Scala SVN -> Github Migration

excellent!

excellent!

What should happen to the links in ScalaDoc pointing to the Trac/SVN stuff?

Any chance being able to link methods to line numbers with the code being on GitHub now?

What should happen to the links in ScalaDoc pointing to the Trac/SVN stuff?

Any chance being able to link methods to line numbers with the code being on GitHub now?

What should happen to the links in ScalaDoc pointing to the Trac/SVN stuff?

Any chance being able to link methods to line numbers with the code being on GitHub

now?

What should happen to the links in ScalaDoc pointing to the Trac/SVN stuff?

Any chance being able to link methods to line numbers with the code being on GitHub

now?

Good question.  I know you can make URL links in github to code.  That'll probably be one of things we tackle immediately after the switch.

On Wed, Nov 30, 2011 at 9:34 AM, Simon Ochsenreither <simon [dot] ochsenreither [at] googlemail [dot] com> wrote:

What should happen to the links in ScalaDoc pointing to the Trac/SVN stuff?

Any chance being able to link methods to line numbers with the code being on GitHub now?

What should happen to the links in ScalaDoc pointing to the Trac/SVN stuff?

Any chance being able to link methods to line numbers with the code being on GitHub now?

Hello Scala Community!
We're migrating the Scala SVN repository to github.   This means that in a few short hours, the *official* scala repository will be http://github.com/scala/scala.
A few quick notes:

• The unofficial repository currently located at  http://github.com/scala/scala will be moved to  http://github.com/scala/legacy-svn-scala.  It's history will no longer be supported.   We've rewritten the SVN history to make it faster for users to fork, read commits and make changes.  Those who have pull-requests against the *unofficial* repository can expect support from yours truly in migrating their pull-requests to the official repo.  Send me an email if you need help migrating your commits.
• You will *STILL* be required to sign the CLA before any patches/pull requests can be accepted into the main repository.  Patches should *still* be accompanied by appropriate tests and will have to be reviewed by a core commiter for merging.  The unofficial repository didn't have any official set of rules on the github site.  See here for some good information from the scaladoc maintainers on what contribution requirements are: https://wiki.scala-lang.org/display/SW/Contributing  (Pay note to the CLA and copyright ownership clauses).
• Things will be in a state of flux for a period of time, until we get a handle on the new development workflow.  While we have a lot of things we'd like to get in place (e.g. an automated bot that will run tests on pull requests and comment directly on your open pull requests, alleviating some of the burden of verification of patches), this first venture will be a bit more fluid.  Please bear with us as we migrate all of our ecosystem to git and github.
• The official Scala wiki will *still be* http://wiki.scala-lang.org, and is not migrating to Github.
• The old SVN repository is now READ ONLY.

We hope this venture will improve the Scala development process and, most importantly, allow more community involvement and a more rapid response from the core team to contributions.   We thank you all for your patience and understanding in the move.
- Josh Suereth

Hello Scala Community!
We're migrating the Scala SVN repository to github.   This means that in a few short hours, the *official* scala repository will be http://github.com/scala/scala.
A few quick notes:

• The unofficial repository currently located at  http://github.com/scala/scala will be moved to  http://github.com/scala/legacy-svn-scala.  It's history will no longer be supported.   We've rewritten the SVN history to make it faster for users to fork, read commits and make changes.  Those who have pull-requests against the *unofficial* repository can expect support from yours truly in migrating their pull-requests to the official repo.  Send me an email if you need help migrating your commits.
• You will *STILL* be required to sign the CLA before any patches/pull requests can be accepted into the main repository.  Patches should *still* be accompanied by appropriate tests and will have to be reviewed by a core commiter for merging.  The unofficial repository didn't have any official set of rules on the github site.  See here for some good information from the scaladoc maintainers on what contribution requirements are: https://wiki.scala-lang.org/display/SW/Contributing  (Pay note to the CLA and copyright ownership clauses).
• Things will be in a state of flux for a period of time, until we get a handle on the new development workflow.  While we have a lot of things we'd like to get in place (e.g. an automated bot that will run tests on pull requests and comment directly on your open pull requests, alleviating some of the burden of verification of patches), this first venture will be a bit more fluid.  Please bear with us as we migrate all of our ecosystem to git and github.
• The official Scala wiki will *still be* http://wiki.scala-lang.org, and is not migrating to Github.
• The old SVN repository is now READ ONLY.

We hope this venture will improve the Scala development process and, most importantly, allow more community involvement and a more rapid response from the core team to contributions.   We thank you all for your patience and understanding in the move.
- Josh Suereth

Hello Scala Community!
We're migrating the Scala SVN repository to github.   This means that in a few short hours, the *official* scala repository will be http://github.com/scala/scala.
A few quick notes:

• The unofficial repository currently located at  http://github.com/scala/scala will be moved to  http://github.com/scala/legacy-svn-scala.  It's history will no longer be supported.   We've rewritten the SVN history to make it faster for users to fork, read commits and make changes.  Those who have pull-requests against the *unofficial* repository can expect support from yours truly in migrating their pull-requests to the official repo.  Send me an email if you need help migrating your commits.
• You will *STILL* be required to sign the CLA before any patches/pull requests can be accepted into the main repository.  Patches should *still* be accompanied by appropriate tests and will have to be reviewed by a core commiter for merging.  The unofficial repository didn't have any official set of rules on the github site.  See here for some good information from the scaladoc maintainers on what contribution requirements are: https://wiki.scala-lang.org/display/SW/Contributing  (Pay note to the CLA and copyright ownership clauses).
• Things will be in a state of flux for a period of time, until we get a handle on the new development workflow.  While we have a lot of things we'd like to get in place (e.g. an automated bot that will run tests on pull requests and comment directly on your open pull requests, alleviating some of the burden of verification of patches), this first venture will be a bit more fluid.  Please bear with us as we migrate all of our ecosystem to git and github.
• The official Scala wiki will *still be* http://wiki.scala-lang.org, and is not migrating to Github.
• The old SVN repository is now READ ONLY.

We hope this venture will improve the Scala development process and, most importantly, allow more community involvement and a more rapid response from the core team to contributions.   We thank you all for your patience and understanding in the move.
- Josh Suereth

Hello Scala Community!
We're migrating the Scala SVN repository to github.   This means that in a few short hours, the *official* scala repository will be http://github.com/scala/scala.
A few quick notes:

• The unofficial repository currently located at  http://github.com/scala/scala will be moved to  http://github.com/scala/legacy-svn-scala.  It's history will no longer be supported.   We've rewritten the SVN history to make it faster for users to fork, read commits and make changes.  Those who have pull-requests against the *unofficial* repository can expect support from yours truly in migrating their pull-requests to the official repo.  Send me an email if you need help migrating your commits.
• You will *STILL* be required to sign the CLA before any patches/pull requests can be accepted into the main repository.  Patches should *still* be accompanied by appropriate tests and will have to be reviewed by a core commiter for merging.  The unofficial repository didn't have any official set of rules on the github site.  See here for some good information from the scaladoc maintainers on what contribution requirements are: https://wiki.scala-lang.org/display/SW/Contributing  (Pay note to the CLA and copyright ownership clauses).
• Things will be in a state of flux for a period of time, until we get a handle on the new development workflow.  While we have a lot of things we'd like to get in place (e.g. an automated bot that will run tests on pull requests and comment directly on your open pull requests, alleviating some of the burden of verification of patches), this first venture will be a bit more fluid.  Please bear with us as we migrate all of our ecosystem to git and github.
• The official Scala wiki will *still be* http://wiki.scala-lang.org, and is not migrating to Github.
• The old SVN repository is now READ ONLY.

We hope this venture will improve the Scala development process and, most importantly, allow more community involvement and a more rapid response from the core team to contributions.   We thank you all for your patience and understanding in the move.
- Josh Suereth

On Wed, Nov 30, 2011 at 09:13:20AM -0500, Josh Suereth wrote:
> We're migrating the Scala SVN repository to github. This means that in a
> few short hours, the *official* scala repository will be
> http://github.com/scala/scala.

Awesome! Thanks so much to everyone who worked on this effort. This
will be a huge boon for the community.

Simon Ochsenreither writes:

> What should happen to the links in ScalaDoc pointing to the Trac/SVN stuff?
>
> Any chance being able to link methods to line numbers with the code being on GitHub now?

Not sure I understand what you mean, but does this answer the question:

https://github.com/scala/scala/blob/master/src/library/scala/collection/...

(click one line number to start, then shift-click to get the end of the
range, and you get the URL)