Moving from harrah/xsbt to sbt/sbt on GitHub

[Mark Harrah]

sbt will be moving from its current location (github.com/harrah/xsbt) to the sbt organization (github.com/sbt/sbt). I believe this can be done in a way that preserves existing links to the code, wiki, and issues at the old harrah/xsbt location, which will be a fork of sbt/sbt. It looks like repository followers also move to the new repository and I don't think forks will be affected (except for which repository to send the pull request to). The wiki at the new sbt/sbt location will be used only for developer documentation, proposals, and other project management/development topics.

I'd like to do this in the next week or so after trying it out on a test repository. I'll send another message after the move. Concerns, questions, comments, and advice are welcome.

Thanks,
Mark

[Doug Tangren]

On Thu, Jan 3, 2013 at 10:19 AM, Mark Harrah <dmha...@gmail.com> wrote:

sbt will be moving from its current location (github.com/harrah/xsbt) to the sbt organization (github.com/sbt/sbt).  I believe this can be done in a way that preserves existing links to the code, wiki, and issues at the old harrah/xsbt location, which will be a fork of sbt/sbt.  It looks like repository followers also move to the new repository and I don't think forks will be affected (except for which repository to send the pull request to).  The wiki at the new sbt/sbt location will be used only for developer documentation, proposals, and other project management/development topics.

I'd like to do this in the next week or so after trying it out on a test repository.  I'll send another message after the move.  Concerns, questions, comments, and advice are welcome.

Sbt is definitely a project that deserves its own gh organization. sbt.github.com also makes a lot more sense as the goto place for user docs.

 

Thanks,
Mark

--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To post to this group, send email to simple-b...@googlegroups.com.
To unsubscribe from this group, send email to simple-build-t...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.

[Josh Suereth]

Sbt.github.com is the same as scala-sbt.org :-)

[Grzegorz Kossakowski]

On 3 January 2013 07:19, Mark Harrah <dmha...@gmail.com> wrote:

sbt will be moving from its current location (github.com/harrah/xsbt) to the sbt organization (github.com/sbt/sbt).  I believe this can be done in a way that preserves existing links to the code, wiki, and issues at the old harrah/xsbt location, which will be a fork of sbt/sbt.  It looks like repository followers also move to the new repository and I don't think forks will be affected (except for which repository to send the pull request to).  The wiki at the new sbt/sbt location will be used only for developer documentation, proposals, and other project management/development topics.

I'd like to do this in the next week or so after trying it out on a test repository.  I'll send another message after the move.  Concerns, questions, comments, and advice are welcome.

+1

Makes perfect sense. I've done this a while ago (1,5hours) with scalagwt project and the transition was pain free.

--
Grzegorz Kossakowski

[Mark Harrah]

Care to elaborate? Were you able to keep the issues in both places, could you make the issues in the old location read-only, did you have to reimport the wiki to the old location, etc...?

-Mark

>
> --
> Grzegorz Kossakowski

[Grzegorz Kossakowski]

On 3 January 2013 13:29, Mark Harrah <dmha...@gmail.com> wrote:

>
> +1
>
> Makes perfect sense. I've done this a while ago (1,5hours) with scalagwt
> project and the transition was pain free.

Care to elaborate?  Were you able to keep the issues in both places, could you make the issues in the old location read-only, did you have to reimport the wiki to the old location, etc...?

Sorry, my e-mail was really sloppy (I think I was missing morning coffee). I meant that I did the migration 1,5 years ago.

However, I checked details and what I did was migrate from user called 'scalagwt' to organization called 'scalagwt'. Therefore I didn't have problem with links, and having two different locations. I somehow thought I migrated from my personal account to scalagwt but that wasn't the case. Sorry for the confusion.

--
Grzegorz Kossakowski

[Mark Harrah]

This is completed. The official project home for sbt is now https://github.com/sbt/sbt. Some links in the documentation still need to be updated. If you cloned the harrah/xsbt repository, please update your remote URLs in your .git/config to sbt/sbt instead of harrah/xsbt.

The major problem was with GitHub Issues. The GitHub API does not provide for importing Issues or Pull Requests in a way that preserves the original content, especially comments. Links directly to comments at harrah/xsbt are no longer valid, although you can replace harrah/xsbt with sbt/sbt and they should still work. To get even the limited re-import that you'll find at https://github.com/harrah/xsbt/issues was sadly a large amount of work.

To anyone following me on GitHub, sorry for the noise from reimporting every issue. I could not find a better way. Social coding and issue tracker maintenance do not go together well.

As a side note, if your project is getting larger (more than 20 issues, perhaps) and you have a preferred issue tracker but think that the integration with GitHub is enough of an advantage, I would suggest using the alternative issue tracker. In particular, if you might move your project from your user account to an organization at some point in the future (or any transfer, really), you should expect that links to your issues and pull requests will be broken unless GitHub implements a proper import feature. The same holds for renaming a repository.

Please let me know about any issues related to this move. (Again, the scala-sbt.org site has not been updated yet, so give me a few days there.)

-Mark