Yup, sorry. We tried.

It's real. Three of our email accounts didn't get owned.

Just what somebody whose email account was owned would say!

Your twitter was probably password-reset using your owned email account!

Yes. Use the migrator approval flow for each of your emails. And if you can't do one of them, email us details and we'll hardcode it.

Mercurial has served us well, but it's time to move on. The world today is quite different from the world then. Most members of the Go community use Git and host their work on GitHub, and we should join them.

Who's heading up the Wiki migration? Besides the MoinMoin-ish to Markdown switch, I imagine each page will need to be checked over to ensure links are updated and everything works. I'd be happy to help whomever is taking this on.

For the Issue migration, I'm surprised that it's not possible to get permission to just public repositories. I trust the Go Team, but whether or not my workplace wants too is another question. I guess "gopherbot" is an option for anyone with reservations.

> "Applications can request access for either public or private repositories on a user-wide level."

Go contributors,

When Go became an open source project 5 years ago, Mercurial was the best choice for us for a number of reasons, most important being the ability to support our choice of code review system.

Mercurial has served us well, but it's time to move on. The world today is quite different from the world then. Most members of the Go community use Git and host their work on GitHub, and we should join them. Thanks to the efforts of open source projects like Android, we now have access to a Git-based code review system that fits our workflow.

We are therefore pleased to announce that we plan to migrate the Go project and its subrepositories to GitHub. The issue tracker and the wiki will also be moved; all data will be preserved. We will use a Google-hosted instance of Gerrit for code reviews.

The transition will happen soon after the 1.4 release in early December. All development for 1.5 will happen in GitHub; the Mercurial tree will be closed to changes after the 1.4 release.

We are still developing the plan and will explain more about the transition in the coming weeks.

There is one thing we need to do beforehand, which is to gather the permissions necessary to migrate the issues on the issue tracker. If you have added issues or comments to the Go issue tracker, please visit go-issue-migrator.appspot.com and click on the "Yes, let's do this" button and authorize our migrator application on GitHub. This gives us access to your GitHub account to enable us to re-create your issues and comments as you, so that you will be notified of changes to issues you've contributed to. (It's OK to not give us this permission; if you don't, your issues and comments will be owned by a "gopherbot" account but will still be attributed to you.) We only need your credentials for the transition; once it's done we'll throw them away and—to be sure—you may revoke the token yourself.

As always, our thanks to the community for all the work you do to make Go succeed.

Rob

P.S. For those keeping score, this will be Go version control system number four. Go development started in Subversion, moved to Perforce, then Mercurial, and soon to Git.

Because they didn't let us request finer grained privileges for the calls we needed.

I did ask them questions but have not heard back anything yet.

Super cool!

Hein :)

Good things come in Gs.

On 14 Nov 2014 18:01, "David du Colombier" <0in...@gmail.com> wrote:

> Will the builders be required to run Git? Is there any
> plan to modify the builder program to propose alternative
> retrieving methods, like downloading the changeset archives
> through HTTP?

GitHub serves repositories over HTTP, but we will probably try to make native Git work since it is much more efficient.

On Fri, Nov 14, 2014 at 8:01 AM, David du Colombier <0in...@gmail.com> wrote:
> Will the builders be required to run Git? Is there any
> plan to modify the builder program to propose alternative
> retrieving methods, like downloading the changeset archives
> through HTTP?

On Fri, Nov 14, 2014 at 1:45 AM, Rob Pike <r...@golang.org> wrote:
> We are therefore pleased to announce that we plan to migrate the Go project
> and its subrepositories to GitHub.

On 14 November 2014 18:43, Jan Mercl <0xj...@gmail.com> wrote:

> The move from mercurial to git is welcome. However, code.google.com
> supports git for a long time, so why not just switch the repository
> format?

On Fri, Nov 14, 2014 at 8:51 AM, David Symonds <dsym...@golang.org> wrote:
>> The move from mercurial to git is welcome. However, code.google.com
>> supports git for a long time, so why not just switch the repository
>> format?
>
> Rob answered that in the paragraph immediately preceding the one you quoted.

Wow! That's great! Excellent

Wow! That's great! Excellent

Wow ! That's great! Excellent

Is it possible to use lower/more finely-grained permissions?
Presumably the issue migrator only needs to create issues and comments
on the behalf of users.

Will there be a pull request based workflow available?

That would lower the barriers even more, since that's what most people are used to. But I am not sure how comfortable you guys with github pull requests these days.

Carl <carl...@gmail.com> once said:
> Git. Go. Gerrit. Google. Gmail. Github.
>
> Good things come in Gs.

That's superb news. It will finally put an end on my hg-inside-git convolution, done so working on multiple issues at once was more comfortable.

Thanks for going through all the migration bureaucracy.

On Friday, 14 November 2014 00:46:10 UTC, Rob Pike wrote:

Go contributors,

When Go became an open source project 5 years ago, Mercurial was the best choice for us for a number of reasons, most important being the ability to support our choice of code review system.

Mercurial has served us well, but it's time to move on. The world today is quite different from the world then. Most members of the Go community use Git and host their work on GitHub, and we should join them. Thanks to the efforts of open source projects like Android, we now have access to a Git-based code review system that fits our workflow.

We are therefore pleased to announce that we plan to migrate the Go project and its subrepositories to GitHub. The issue tracker and the wiki will also be moved; all data will be preserved. We will use a Google-hosted instance of Gerrit for code reviews.

The transition will happen soon after the 1.4 release in early December. All development for 1.5 will happen in GitHub; the Mercurial tree will be closed to changes after the 1.4 release.

We are still developing the plan and will explain more about the transition in the coming weeks.

There is one thing we need to do beforehand, which is to gather the permissions necessary to migrate the issues on the issue tracker. If you have added issues or comments to the Go issue tracker, please visit go-issue-migrator.appspot.com and click on the "Yes, let's do this" button and authorize our migrator application on GitHub. This gives us access to your GitHub account to enable us to re-create your issues and comments as you, so that you will be notified of changes to issues you've contributed to. (It's OK to not give us this permission; if you don't, your issues and comments will be owned by a "gopherbot" account but will still be attributed to you.) We only need your credentials for the transition; once it's done we'll throw them away and—to be sure—you may revoke the token yourself.

As always, our thanks to the community for all the work you do to make Go succeed.

Rob

P.S. For those keeping score, this will be Go version control system number four. Go development started in Subversion, moved to Perforce, then Mercurial, and soon to Git.

On Fri, Nov 14, 2014 at 2:16 PM, Aram Hăvărneanu <ara...@mgk.ro> wrote:
> Will it be possible to create and comment on issues without a GitHub account?

On 14 November 2014 10:23, Steven Hartland <steven....@multiplay.co.uk> wrote:
>
> This is great news but unless you can restrict it to public repos only we won't be able to authorise this :(

While I think moving to Git and Gerrit is a very good
thing, I feel a bit concerned about the builders.

Will the builders be required to run Git? Is there any
plan to modify the builder program to propose alternative
retrieving methods, like downloading the changeset archives
through HTTP?

Thanks.

--
David du Colombier

> FYI the builders already run git, for gccgo builds, at least.  I wanted to
> download the changeset archives through HTTP originally, but it seems
> mercurial is the only VCS out of bzr, svn, and git that doesn't have that
> command natively.

On Fri, Nov 14, 2014 at 10:13 AM, 'Peter Collingbourne' via golang-dev
<golan...@googlegroups.com> wrote:
> Will the gofrontend repository also be moving to GitHub?

On Sunday, 16 November 2014 14:59:39 UTC-7, Andrew Gerrand wrote:

We've now switched to using the "public_repo" scope and re-deployed the go-issue-migrator app. Try it now.

On Sun, Nov 16, 2014 at 9:13 PM,  <jeff....@gmail.com> wrote:
>>> My concern was about the Plan 9 builders. Git doesn't run on Plan 9 yet.
>>>
>>> We'll have to port Git (as Felipe Bichued, Steven Stallion and Jeff
>>> Sickel
>>> ported Python and Mercurial previously), but it will take more than two
>>> weeks.

> It doesn't look like getting a Plan 9 build of Git will be that difficult,
> though we'll have to throw away bits from git/t tree if you don't run lnfs.
> Decoding the git/Makefile is... painful, but possibly less so than updating
> Plan 9's Python + hg to support hggit.

On Mon, Nov 17, 2014 at 4:20 AM, 'Han-Wen Nienhuys' via golang-dev
<golan...@googlegroups.com> wrote:
> You may want to consider looking at porting libgit2 instead, and
> writing a command-line client on top of that that implements just what
> you need. The libgit2 code is much cleaner and better structured than
> cgit.

On Thursday, November 13, 2014 7:46:10 PM UTC-5, Rob Pike wrote:

Go contributors,

When Go became an open source project 5 years ago, Mercurial was the best choice for us for a number of reasons, most important being the ability to support our choice of code review system.

Mercurial has served us well, but it's time to move on. The world today is quite different from the world then. Most members of the Go community use Git and host their work on GitHub, and we should join them. Thanks to the efforts of open source projects like Android, we now have access to a Git-based code review system that fits our workflow.

We are therefore pleased to announce that we plan to migrate the Go project and its subrepositories to GitHub. The issue tracker and the wiki will also be moved; all data will be preserved. We will use a Google-hosted instance of Gerrit for code reviews.

The transition will happen soon after the 1.4 release in early December. All development for 1.5 will happen in GitHub; the Mercurial tree will be closed to changes after the 1.4 release.

We are still developing the plan and will explain more about the transition in the coming weeks.

There is one thing we need to do beforehand, which is to gather the permissions necessary to migrate the issues on the issue tracker. If you have added issues or comments to the Go issue tracker, please visit go-issue-migrator.appspot.com and click on the "Yes, let's do this" button and authorize our migrator application on GitHub. This gives us access to your GitHub account to enable us to re-create your issues and comments as you, so that you will be notified of changes to issues you've contributed to. (It's OK to not give us this permission; if you don't, your issues and comments will be owned by a "gopherbot" account but will still be attributed to you.) We only need your credentials for the transition; once it's done we'll throw them away and—to be sure—you may revoke the token yourself.

As always, our thanks to the community for all the work you do to make Go succeed.

Rob

P.S. For those keeping score, this will be Go version control system number four. Go development started in Subversion, moved to Perforce, then Mercurial, and soon to Git.

On Mon, Dec 8, 2014 at 9:45 PM, Jimmy Zelinskie
<jimmyze...@gmail.com> wrote:
> It appears as though the move to GitHub has taken (is taking) place. How
> long until the Gerrit instance is online or is it already?

I'd like to try using milestones. If it works out for 1.5, I'm happy to do the grunt work to relabel the older issues and milestones.