On May 24, 2015, at 12:25 PM, Brad Hollister <behol...@soe.ucsc.edu> wrote:
> When developing our code for GSoC, will we get a SVN branch to work out of? > I'd like to version control my local changes. Also, while developing, I'd > like to not worry about integrating the trunk. > > If we don't get a branch of our own, is it best to create a snapshot of the > trunk and make a git repo of our own (and host a public copy on github or > sourceforge)? More on this will come out this week; access is granted on a case-by-case basis. Everyone should make sure to submit at least one functional patch to our Sourceforge tracker (see the Checklist), and ideally two that apply flawlessly. We strongly prefer integrated development and generally do not want most participants working in isolation. Exceptions are rare. Revisit http://brlcad.org/wiki/Google_Summer_of_Code/Expectations#Integrated_development for some details, but the reasoning is even deeper than our docs get into. Basically, we want you to worry about integrating trunk — otherwise you’re making someone else worry, are accruing technical debt, or both. Cheers! Sean ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
