I forgot to mention one thing. Since there is substantial interest from a number of people that do not have commit access established, I suggest going through at least one GCI task to be familiar with the work, ideally two that are different types. The list of open and completed tasks from last year is here:
http://www.google-melange.com/gci/org/google/gci2012/brlcad Getting familiar could be as simple as reviewing/testing one of the *completed* GCI programming tasks that hasn't yet been committed. Submit it as a patch to Sourceforge after confirming that it applies and works, or improve their patch. Or you could just pick up one of the GCI tasks that is still open, complete it, and submit your results (to Sourceforge). Everyone should be familiar with one or two task types in order to be effective mentors. Most of the coding tasks really shouldn't take more than an hour, but the importance is being familiar with the process and familiar with how to review their work. Please ask questions if you have them. Cheers! Sean On Oct 23, 2013, at 12:13 AM, Christopher Sean Morrison wrote: > > We have a lot to do to get ready for GCI, and outstandingly a lot of mentor > interest. In preparation, we need those of you that are interested in > mentoring to help get everything ready. Here's a list of some things we need > to do in advance, please tackle any or all of them: > > 01) Post+announce release 7.24.2 (I got this) > 02) Fix style anomalies, update style (I got this) > 03) Add style checker to debug build > 04) Create a GCI branch > 05) Document the program (briefly) on our wiki, similar to the GSoC pages > - See http://brlcad.org/wiki/Google_Code_In > 06) Create a w > 07) Update the VM image with the GCI branch > - See http://www.google-melange.com/gci/task/view/google/gci2012/8013221 > 08) Sync our Deuces page with Melange > 09) Write a wiki scraper so we can export Deuces entries as CSV and > auto-import into Melange > 10) Create+populate GCI 2013 wiki page with basic overview / instruction > - Put here: http://brlcad.org/wiki/Google_Code_In/2013 > 11) Write a brief article (2 paragraphs) about our 2012 GCI participation > - Put here: http://brlcad.org/wiki/Community_Publication_Portal > 12) Upload all the completed 2012 GCI tasks to Sourceforge (probably a way to > automate this) > 13) Review+apply+close patches for any code contributions (there are dozens > still pending) > 14) Create new GCI tasks on our Deuces page, see the template > - Every mentor should add at least 10 tasks, but discuss so we maintain > consistency > 15) Submit our application (I got this) > > I will be writing up our application based on last year's submission. I've > put this list up into the wiki here: > http://brlcad.org/wiki/Google_Code_In/2013/TODO > > Feel free to claim any of the tasks (put your name) or strike them out when > you complete one. Each mentor should create at least 10 fully annotated > tasks with at least one of each type represented. Priority is on getting > last year's patches all integrated and new tasks defined on our Deuces page. > > Cheers! > Sean > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > BRL-CAD Developer mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/brlcad-devel ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
