Hi Luc,<div>At this point I'd say (b) looks most useful.</div><div>Ralf<br><br><div class="gmail_quote">On Sun, Apr 22, 2012 at 4:44 AM, Luc Bourhis <span dir="ltr"><<a href="mailto:luc_j_bourhis@mac.com">luc_j_bourhis@mac.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div class="im"><blockquote type="cite"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<blockquote type="cite">it would be easy to put a crontab on the CCI machine phenix-online, that would periodically update from sourceforge and then push to GitHub.</blockquote></blockquote></div></div></blockquote><br></div>
<div class="im"><blockquote type="cite"><div>Or maybe we could setup a mail account that receives the commit messages which then triggers the git sync?</div><div>Ralf</div></blockquote><br></div></div><div>We first need to clarify what we want the GitHub repo to be for. Two choices here as I see it:</div>
<div>(a) a repo that would fit in the git culture: git afficionados would fork it, do their own development and then send pull notification to us, never using "git svn";</div><div>(b) a repo whose sole purpose would be to spare the long time necessary to run "git svn clone" in the first place: users of that repo would share their development with us solely through "git svn dcommit".</div>
<div><br></div><div>I had obviously (b) in mind, hence my not being concerned with a slight lag between sourceforge and GitHub. If option (a) is our goal, then not only the lag shall be minimised but the "master" branch of the GitHub repository should be "dcommited" periodically to sourceforge. And of course, we need a clear policy to deal with those pull requests. That option (b) would be an alternative to give commit rights to sourceforge to "casual" cctbx developers. Thanks to git, it would be easy to checkout and then evaluate their proposed pull, then giving the green light at the press of a button. As usual with git, it's another world entirely��</div>
<span class="HOEnZb"><font color="#888888"><div><br></div><div>Luc</div><div><br></div><div></div></font></span></div><br>_______________________________________________<br>
cctbxbb mailing list<br>
<a href="mailto:cctbxbb@phenix-online.org">cctbxbb@phenix-online.org</a><br>
<a href="http://phenix-online.org/mailman/listinfo/cctbxbb" target="_blank">http://phenix-online.org/mailman/listinfo/cctbxbb</a><br>
<br></blockquote></div><br></div>