Mike you should call a vote on this Sent from my iPhone
> On Feb 21, 2014, at 1:22 PM, "Michael Joyce" <[email protected]> wrote: > > Thanks for all the feedback everyone. I'm going to include a move to Git in > my JIRA tickets that I'll be opening today. Keep discussing though! I just > want to make sure INFRA starts on everything sooner rather than later! > > > > > -- Joyce > > > On Thu, Feb 20, 2014 at 3:28 PM, Lee, Kyo (3246-Affiliate) < > [email protected]> wrote: > >> Actually I am ignorant of Git so I quickly googled 'SVN vs GIT' and found >> this. >> >> "SVN is one repo and lots of clients. GIT is a repo with lots of client >> repos, each with a user. It's decentralised to a point where people can >> track their own edits locally without having to push things to an external >> server. >> >> SVN is designed to be more central where GIT is based on each user having >> their own GIT repo and those repos push changes back up into a central one. >> For that reason, GIT gives individuals better local version control." >> >> (http://stackoverflow.com/questions/161541/should-i-use-svn-or-git) >> >> Now I like the idea of moving codes to Git. >> >> Cheers, >> Kyo >> >> On Feb 20, 2014, at 1:44 PM, Michael Joyce wrote: >> >> Hay Alex, >> >> Everyone's opinion is always welcome so never hesitate to throw it around! >> >> To clarify a bit for everyone: >> >> - The ASF repository would be Git not SVN. The ASF repository is always the >> gold standard. All work must be done through it. >> - There would be a Github mirror of the project much like OODT has at [1]. >> The Github mirror would be for users to provide pull requests against and >> for code reviews. We wouldn't be doing any commits directly to Github. Note >> that we could still have a Github mirror without using Git. It's just not >> quite as easy trying to mix the two together in that way. >> - We would still use JIRA over the Github issue tracker (since it's quite >> lacking). >> >> I think a good project to look to for inspiration in this would be Spark. >> They have a very Git(hub) centric workflow that has worked very well for >> their project. In fact, they even have a Jenkins instance that watches for >> pull requests and builds/runs tests, which would be quite nice. [2] and [3] >> for reference. >> >> [1] https://github.com/apache/oodt >> [2] https://github.com/apache/incubator-spark >> [3] >> https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark >> >> >> >> -- Joyce >> >> >> On Thu, Feb 20, 2014 at 1:17 PM, Boustani, Maziyar (398F) < >> [email protected]<mailto:[email protected]>> >> wrote: >> >> Congrats team, I am also interested to have code on Git. >> >> Best regards, >> Mazi >> >> On Feb 20, 2014, at 1:09 PM, Alex Goodman wrote: >> >> Hi all, >> >> I don't know how much weight my opinion holds at this point but I wanted to >> share my 2 cents from my limited experience with git. >> >> From a CLI perspective, I find git to be rather clunky (though very >> powerful) in comparison to svn. However I do think Github itself would >> provide some nice features to this project in one convenient place, in >> particular the ability create issues and review code (via pull requests). >> Also, this last point is not particularly relevant but a lot of other >> active python projects are now hosted on Github, including numpy/scipy and >> matplotlib. I do think having OCW on their too might provide us some nice >> exposure, though this is just conjecture on my part. >> >> So yeah, slightly tl;dr but this definitely has my +1. >> >> Oh, and congrats on graduation. >> >> Alex >> >> >> On Thu, Feb 20, 2014 at 1:44 PM, Chris Mattmann <[email protected] >> <mailto:[email protected]> >> <mailto:[email protected]>> wrote: >> >> Hi Cam: you can work from Github, and so forth, and pull request >> emails, comments, etc. can be mirror'ed to the dev list as all >> communication, and canonical bits for the project must end up >> on the dev list and archived as decisions for the project. >> >> That being said: the Git writeable repo at the ASF is its home. >> At the same time we can mirror at Github, and also issue pull >> requests against those mirrors, and then merge back into the ASF >> writeable Git home for Climate at that point. >> >> So it supports that workflow and even the UI and all convo and >> bits end up on the list here at the ASF, enabling our foundation >> to be able to meet its goals as well. >> >> Cheers, >> Chris >> >> P.S. note these Git services must be explicitly requested >> from infra@ should a JIRA issue be filed should this discussion >> result in consensus to move to Git. >> >> >> >> -----Original Message----- >> From: Cameron Goodale <[email protected]<mailto:[email protected] >>> <mailto:[email protected]>> >> Reply-To: "[email protected]<mailto: >> [email protected]><mailto: >> [email protected]<mailto:[email protected] >>>> " >> <[email protected]<mailto:[email protected] >>> <mailto:[email protected] >> >> Date: Thursday, February 20, 2014 12:38 PM >> To: "[email protected]<mailto: >> [email protected]><mailto: >> [email protected]<mailto:[email protected]>>" >> <[email protected]<mailto:[email protected]> >> <mailto:[email protected]>> >> Subject: Re: Thoughts on moving to Git >> >> +1 from me on moving to Git. >> >> Just one question: Does this also mean we can work from Github to handle >> pull requests and such? I have seen threads about GH mirrors becoming >> stale and not being able to use a lot of the GH features. >> >> Congrats to the entire DEV team on graduation. >> >> -Cam >> >> >> On Thu, Feb 20, 2014 at 11:47 AM, Mattmann, Chris A (3980) < >> [email protected]<mailto:[email protected] >>> <mailto:[email protected]>> >> wrote: >> >> +1 to Git. Woot. >> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Chris Mattmann, Ph.D. >> Chief Architect >> Instrument Software and Science Data Systems Section (398) >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> Office: 171-283, Mailstop: 171-246 >> Email: [email protected]<mailto:[email protected]><mailto: >> [email protected]> >> WWW: http://sunset.usc.edu/~mattmann/ >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Adjunct Associate Professor, Computer Science Department >> University of Southern California, Los Angeles, CA 90089 USA >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> >> >> >> >> >> -----Original Message----- >> From: Michael Joyce <[email protected]<mailto:[email protected]><mailto: >> [email protected]>> >> Reply-To: "[email protected]<mailto: >> [email protected]><mailto: >> [email protected]<mailto:[email protected] >>>> " >> <[email protected]<mailto:[email protected] >>> <mailto:[email protected] >> >> Date: Thursday, February 20, 2014 11:25 AM >> To: dev <[email protected]<mailto: >> [email protected]><mailto: >> [email protected]<mailto:[email protected] >> Subject: Thoughts on moving to Git >> >> Hi guys, >> >> First, Yay we graduated from Incubator!!! >> >> Second, since we have to move over our infrastructure now seems like a >> good >> time to discuss moving to git instead of SVN. I'm all for moving over >> to >> git (which probably doesn't surprise anyone). >> >> What do you guys think? >> >> -- Joyce >> >> >> >> >> -- >> >> Sent from a Tin Can attached to a String >> >> >> >> >> >> -- >> Alex Goodman >> Graduate Research Assistant >> Department of Atmospheric Science >> Colorado State University >> >> >> >>
