@Gilles - thanks for chipping in on the move. With [numbers]. [rng], [statistics], and [math] out, that leaves us with the following 18 repos (broken up for readability sake):
commons-build-plugin.git 11 weeks ago commons-cli.git 30 weeks ago commons-collections.git 15 days ago commons-compress.git 19 days ago commons-crypto.git 9 weeks ago commons-csv.git 7 weeks ago commons-dbcp.git 24 days ago commons-dbutils.git 30 weeks ago commons-fileupload.git 29 weeks ago commons-imaging.git 6 weeks ago commons-io.git 18 days ago commons-lang.git 6 days ago commons-pool.git 16 days ago commons-rdf.git 25 weeks ago commons-release-plugin.git 25 days ago commons-scxml.git 7 weeks ago commons-testing.git 30 weeks ago commons-text.git 14 days ago I’ll take the rest over December. Pardon the two email chains here…..but infra said they wanted documented consensus so alas we have two. -Rob > On Dec 8, 2018, at 10:38 AM, sebb <seb...@gmail.com> wrote: > > The inventory is here: > > https://git1-us-west.apache.org/repos/asf > > These are the Commons ones: > > commons-build-plugin.git 11 weeks ago > commons-cli.git 30 weeks ago > commons-collections.git 15 days ago > commons-compress.git 19 days ago > commons-crypto.git 9 weeks ago > commons-csv.git 7 weeks ago > commons-dbcp.git 24 days ago > commons-dbutils.git 30 weeks ago > commons-fileupload.git 29 weeks ago > commons-imaging.git 6 weeks ago > commons-io.git 18 days ago > commons-lang.git 6 days ago > commons-math.git 15 weeks ago > commons-numbers.git 8 days ago > commons-pool.git 16 days ago > commons-rdf.git 25 weeks ago > commons-release-plugin.git 25 days ago > commons-rng.git < 2 days ago > commons-scxml.git 7 weeks ago > commons-statistics.git 30 weeks ago > commons-testing.git 30 weeks ago > commons-text.git 14 days ago > > S. > > > On Sat, 8 Dec 2018 at 14:40, Rob Tompkins <chtom...@gmail.com> wrote: >> >> Seems like we should put together an inventory, and pull the divide and >> conquer strategy?? Who’s willing to lend hands here? >> >> -Rob >> >>> On Dec 8, 2018, at 8:38 AM, Gary Gregory <garydgreg...@gmail.com> wrote: >>> >>> Sounds good. >>> >>> Gary >>> >>> On Fri, Dec 7, 2018, 17:33 Gilles <gil...@harfang.homelinux.org wrote: >>> >>>> Hi. >>>> >>>> [See message quoted below.] >>>> >>>> Any objection to my filing an INFRA request for each of the >>>> following components: >>>> [Numbers] >>>> [RNG] >>>> [Statistics] >>>> [Math] >>>> ? >>>> >>>> Gilles >>>> >>>> -------- Original Message -------- >>>> Subject: [NOTICE] Mandatory relocation of Apache git repositories on >>>> git-wip-us.apache.org >>>> Date: Fri, 7 Dec 2018 17:52:36 +0100 >>>> From: Daniel Gruno <humbed...@apache.org> >>>> To: "us...@infra.apache.org" <us...@infra.apache.org> >>>> Reply-To: "us...@infra.apache.org" <us...@infra.apache.org> >>>> >>>> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE >>>> DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] >>>> >>>> Hello Apache projects, >>>> >>>> I am writing to you because you may have git repositories on the >>>> git-wip-us server, which is slated to be decommissioned in the coming >>>> months. All repositories will be moved to the new gitbox service which >>>> includes direct write access on github as well as the standard ASF >>>> commit access via gitbox.apache.org. >>>> >>>> ## Why this move? ## >>>> The move comes as a result of retiring the git-wip service, as the >>>> hardware it runs on is longing for retirement. In lieu of this, we >>>> have decided to consolidate the two services (git-wip and gitbox), to >>>> ease the management of our repository systems and future-proof the >>>> underlying hardware. The move is fully automated, and ideally, nothing >>>> will change in your workflow other than added features and access to >>>> GitHub. >>>> >>>> ## Timeframe for relocation ## >>>> Initially, we are asking that projects voluntarily request to move >>>> their repositories to gitbox, hence this email. The voluntary >>>> timeframe is between now and January 9th 2019, during which projects >>>> are free to either move over to gitbox or stay put on git-wip. After >>>> this phase, we will be requiring the remaining projects to move within >>>> one month, after which we will move the remaining projects over. >>>> >>>> To have your project moved in this initial phase, you will need: >>>> >>>> - Consensus in the project (documented via the mailing list) >>>> - File a JIRA ticket with INFRA to voluntarily move your project repos >>>> over to gitbox (as stated, this is highly automated and will take >>>> between a minute and an hour, depending on the size and number of >>>> your repositories) >>>> >>>> To sum up the preliminary timeline; >>>> >>>> - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) >>>> relocation >>>> - January 9th -> February 6th: Mandated (coordinated) relocation >>>> - February 7th: All remaining repositories are mass migrated. >>>> >>>> This timeline may change to accommodate various scenarios. >>>> >>>> ## Using GitHub with ASF repositories ## >>>> When your project has moved, you are free to use either the ASF >>>> repository system (gitbox.apache.org) OR GitHub for your development >>>> and code pushes. To be able to use GitHub, please follow the primer >>>> at: https://reference.apache.org/committer/github >>>> >>>> >>>> We appreciate your understanding of this issue, and hope that your >>>> project can coordinate voluntarily moving your repositories in a >>>> timely manner. >>>> >>>> All settings, such as commit mail targets, issue linking, PR >>>> notification schemes etc will automatically be migrated to gitbox as >>>> well. >>>> >>>> With regards, Daniel on behalf of ASF Infra. >>>> >>>> PS:For inquiries, please reply to us...@infra.apache.org, not your >>>> project's dev list :-). >>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>> >>>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
