Skip to content

Commit

Permalink
Remove references to the mailing-list
Browse files Browse the repository at this point in the history
We don't use it anymore.
  • Loading branch information
smarter committed Nov 16, 2017
1 parent 5e325b0 commit a49ee2c
Show file tree
Hide file tree
Showing 2 changed files with 0 additions and 2 deletions.
1 change: 0 additions & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,6 @@ This is the process for committing code to the Scala project. There are of cours
1. Make sure you have signed the [Scala CLA](http://typesafe.com/contribute/cla/scala), if not, sign it.
2. Before starting to work on a feature or a fix, it's good practice to ensure that:
1. There is a ticket for your work in the project's [issue tracker](https://github.com/lampepfl/dotty/issues);
2. If not, create it first (perhaps given a thumbs up from the dotty-internals mailing list first);
2. The ticket has been discussed and prioritized by the team.
3. You should always perform your work in its own Git branch. The branch should be given a descriptive name that explains its intent. Some teams also like adding the ticket number and/or the [GitHub](http://github.com) user ID to the branch name, these details is up to each of the individual teams. (See below for more details on branch naming.)
4. When the feature or fix is completed you should open a [Pull Request](https://help.github.com/articles/using-pull-requests) on GitHub.
Expand Down
1 change: 0 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,6 @@ Community build: [![Community Build Status](https://travis-ci.org/lampepfl/dotty

* [Homepage](http://dotty.epfl.ch)
* [Documentation](http://dotty.epfl.ch/docs)
* [Mailing list](https://groups.google.com/forum/#!forum/dotty-internals)

Try it out
==========
Expand Down

0 comments on commit a49ee2c

Please sign in to comment.