> > Moving to gitbox means you will get full write access on GitHub as well, > and be able to close/merge pull requests and much more. >
I think this statement is interesting in regards to Gerrit and the merge script. We will need to make sure no committer merges a pull request or backports a change via github, otherwise Gerrit will get out of sync. Perhaps at some point shortly after the migration we should consider using github as the main point for contributions and reviews. Many successful open source communities already do this, Spark and Kafka are Apache examples and I find more people know how to send pull requests via Github, then have had experience with Gerrit. We also wouldn't need to run push_to_asf.py script anymore. Now that we have a lot more control/power this seams like the way most Apache projects would go. On Thu, Jan 3, 2019 at 10:10 AM Attila Bukor <[email protected]> wrote: > I'm 99% sure we don't. Gerrit uses it's own internal repo and doesn't > have a notiion of remotes without plugins (which we don't use as we > push merged commits to ASF manually using the push_to_asf.py script). > > Jenkins uses Gerrit's internal repo as well, as evidenced by the console > output of the console output of the latest builds of both kudu-gerrit > and kudu-tidy-bot: > > 06:05:34 > git config remote.origin.url http://gerrit.cloudera.org/kudu > # timeout=10 > > On Thu, Jan 03, 2019 at 07:51:54AM -0800, Adar Lieber-Dembo wrote: > > Do we need to update any configuration in gerrit.cloudera.org or > > jenkins.kudu.apache.org? > > > > On Thu, Jan 3, 2019 at 6:18 AM Attila Bukor <[email protected]> wrote: > > > > > Hi, > > > > > > I submitted 2 patches to Gerrit to change our tooling to use the gitbox > > > URLs: > > > > > > - https://gerrit.cloudera.org/c/12150/ > > > - https://gerrit.cloudera.org/c/12151/ > > > > > > I'm not aware of any other changes we need to do, so if these patches > > > get +2s and there are no objections on this thread by Wednesday, I > think > > > we can proceed with the migration. > > > > > > Please let me know if you have any concerns about this. > > > > > > Thanks, > > > Attila > > > > > > On Thu, Jan 03, 2019 at 01:19:14PM -0000, Apache Infrastructure Team > wrote: > > > > Hello, kudu folks. > > > > As stated earlier in 2018, all git repositories must be migrated from > > > > the git-wip-us.apache.org URL to gitbox.apache.org, as the old > service > > > > is being decommissioned. Your project is receiving this email because > > > > you still have repositories on git-wip-us that needs to be migrated. > > > > > > > > The following repositories on git-wip-us belong to your project: > > > > - kudu.git > > > > - kudu-site.git > > > > > > > > > > > > We are now entering the mandated (coordinated) move stage of the > roadmap, > > > > and you are asked to please coordinate migration with the Apache > > > > Infrastructure Team before February 7th. All repositories not > migrated > > > > on February 7th will be mass migrated without warning, and we'd > > > appreciate > > > > it if we could work together to avoid a big mess that day :-). > > > > > > > > Moving to gitbox means you will get full write access on GitHub as > well, > > > > and be able to close/merge pull requests and much more. > > > > > > > > To have your repositories moved, please follow these steps: > > > > > > > > - Ensure consensus on the move (a link to a lists.apache.org thread > will > > > > suffice for us as evidence). > > > > - Create a JIRA ticket at > https://issues.apache.org/jira/browse/INFRA > > > > > > > > Your migration should only take a few minutes. If you wish to migrate > > > > at a specific time of day or date, please do let us know in the > ticket. > > > > > > > > As always, we appreciate your understanding and patience as we move > > > > things around and work to provide better services and features for > > > > the Apache Family. > > > > > > > > Should you wish to contact us with feedback or questions, please do > so > > > > at: [email protected]. > > > > > > > > > > > > With regards, > > > > Apache Infrastructure > > > > > > > > -- Grant Henke Software Engineer | Cloudera [email protected] | twitter.com/gchenke | linkedin.com/in/granthenke
