3
On Mon, Nov 5, 2012 at 10:37 AM, Jeroen van der Wal <[email protected]> wrote: > 3 > > -- > Jeroen van der Wal > +31 655 874050 > > On Mon, Nov 5, 2012 at 8:26 AM, Dan Haywood > <[email protected]>wrote: > >> yup, couchdb use git for their codebase, and svn as the backing store for >> their site (using Apache's CMS). I suggest we follow the same path. >> >> When I IRC'ed with <danielsh> on infra yesterday, it was kinda like, "we >> just need to know if you are on svn or git..". There are further docs here >> [1]. >> >> [1] https://git-wip-us.apache.org/ >> >> >> On 4 November 2012 23:35, Henry Saputra <[email protected]> wrote: >> >> > Hi Dan, >> > >> > I did not know that option number 3 now exists for Apache projects. If >> its >> > true then +1 for option 3 (non-binding) >> > >> > - Henry >> > >> > >> > On Sun, Nov 4, 2012 at 3:29 PM, Dan Haywood < >> [email protected] >> > >wrote: >> > >> > > The idea of using git rather than svn for the Isis codebase has been >> > > discussed several times in the past. Now that we have graduated, it >> > seems >> > > a good time to formally vote on whether we want to make this change. >> > > >> > > There are three options available: >> > > >> > > 1. carry on using svn. (In this case, I will carry on maintaining an >> > > informal read-only copy on github as a convenience to contributors who >> > > prefer to create patches using git) >> > > 2. use git.apache.org as a read-only clone, with svn remaining as the >> > > master. (This is similar to 1, though git.apache.org is a more formal >> > > copy >> > > way of doing this) >> > > 3. use git.apache.org as a read/write master, and retire use of svn >> for >> > > the >> > > Isis codebase. >> > > >> > > As usual, this vote will be open for at least 72 hours. Please >> indicate >> > > your preference as (1), (2) or (3). I have cc'ed to >> > > [email protected] order to elicit the widest number of views. >> > > >> > > Thanks >> > > Dan >> > > Isis PMC Chair >> > > >> > >>
