I've just created https://issues.apache.org/jira/browse/INFRA-17745 for this task, referencing this thread as lazy consensus.
Thx On Thu, 3 Jan 2019 at 19:53, Kevin Meyer <[email protected]> wrote: > Hi Dan, > > I agree with the assumption of lazy consensus, but I give my formal > consent anyway. > > I agree with the move. > > I agree that you can go ahead and create the JIRA ticket, as/when you wish. > > Thanks, > Kevin > > -- > Kevin Meyer > Vice President Apache Isis (https://isis.apache.org) > The Apache Software Foundation > > > On Thu, January 3, 2019 14:59, Dan Haywood wrote: > > As per Infra's email below, let's use this email thread to ensure > > consensus that it is okay for this repo to be migrated to gitbox. > > > > To explain what's going on here... > > > > > > we have two git repos, the main one (isis.git) on github, and the one for > > our site (isis-site.git) that is still on git-wip-us.apache.org. > > > > The isis-site.git repo actually just holds the generated website. When I > > build the site locally, I copy over the generated HTML and PDFs into > > this isis-site, and push; that causes the site to be published to > > isis.apache.org . > > > > > > Infra's mention of gitbox.apache.org is basically the bit of magic that > > (I > > think) sets up some sort of trust relationship so that the github-hosted > > repo is the canonical repo for our project rather than a repo hosted on > > an apache.org server. We already did this for isis.git, but haven't yet > > done so for isis-git.org. > > > > I'm going to assume lazy consensus on this .... unless I hear otherwise > > I'll assume that everyone is okay for us to ask infra to migrate > > isis-site.git over to github. The only impact is for anyone who builds > > and publishes the isis website, which so far, has only ever been me, I > > think. > > > > But, if you do have issues, then do raise them here. > > > > > > Thanks > > Dan > > > > > > > > > > > > > > ---------- Forwarded message --------- > > From: Apache Infrastructure Team <[email protected]> > > Date: Thu, 3 Jan 2019 at 13:19 > > Subject: [NOTICE] Mandatory migration of git repositories to > > gitbox.apache.org To: <[email protected]> > > > > > > > > Hello, isis 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: > > - isis-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 > > > > > > >
