Hi all, Our trafodion site repo has been migrated by INFRA to GitBox. It should now offer a write-able mirror on GitHub, allowing committers to be able to merge GitHub pull requests directly via functionalities there.
Can we test this (and report findings) before I submit a request to migrate our code repo? Best regards, Pierre Smits *Apache Trafodion <https://trafodion.apache.org>, Vice President* *Apache Directory <https://directory.apache.org>, PMC Member* Apache Incubator <https://incubator.apache.org>, committer *Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges) since 2008* Apache Steve <https://steve.apache.org>, committer On Sun, Jan 6, 2019 at 10:36 AM Pierre Smits <[email protected]> wrote: > > Hi all the request to migrate the website repo has been submitted. It can > be tracked here: https://issues.apache.org/jira/browse/INFRA-17562 > > Best regards, > > Pierre Smits > > *Apache Trafodion <https://trafodion.apache.org>, Vice President* > *Apache Directory <https://directory.apache.org>, PMC Member* > Apache Incubator <https://incubator.apache.org>, committer > *Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges) > since 2008* > Apache Steve <https://steve.apache.org>, committer > > > On Fri, Jan 4, 2019 at 1:54 AM ming.liu <[email protected]> wrote: > >> Thanks Pierre, >> >> This is a good plan. +1 >> >> Ming >> >> -----Original Message----- >> From: Pierre Smits <[email protected]> >> Sent: Thursday, January 03, 2019 9:58 PM >> To: [email protected] >> Subject: Repo Migration >> >> Hi All, >> >> Happy New Year to all. >> >> As you may have noticed from postings by the INFRA team the mandatory >> migration of our repos >> >> - trafodion.git >> - trafodion-site.git >> >> is intended to happen soon (shortly after Feb 7th, 2019). >> >> In order not to put all our eggs (combined with those of other Apache >> projects) I propose to stagger our migration efforts before the kick-off >> of >> the mandatory process, by >> >> 1. initiating the migration of our website repo first a.s.a.p.; >> 2. initiate the migration of our code base repo second and last. >> >> This way we will build the experience of all our contributors and will - >> most probably - minimise the migration issues. >> >> f you have any questions or concerns please let us know. I will wait >> until >> the beginning of next week before submitting a ticket to infra regarding >> the migration of our website repo ( aspect #1), giving consent for the >> move. Once that move has taken place and the dust has settled again, >> we'll >> initiate the move of the code repo. This will give us a 3-4 week window to >> address any issues raised. >> >> Lazy consensus rules apply, meaning silence implies consent. >> >> Best regards, >> >> Pierre Smits >> >> *Apache Trafodion <https://trafodion.apache.org>, Vice President* >> *Apache Directory <https://directory.apache.org>, PMC Member* >> Apache Incubator <https://incubator.apache.org>, committer >> *Apache OFBiz <https://ofbiz.apache.org>, contributor (without >> privileges) >> since 2008* >> Apache Steve <https://steve.apache.org>, committer >> >>
