If you are interested in helping out for GCI, at the very least add your name to the bottom of https://github.com/sympy/sympy/wiki/gci-2012-organization-application (under the "Please tell us about how your organization has prepared for Google Code-in..." question). It would also help out if you edited the application to update it and/or did some work creating/tagging issues for tasks.
So far, no one except for Sean seems to have done anything with this. If no one helps out with this, I will take that to mean that we don't have enough people interested in volunteering to be mentors, and I won't submit the application. Aaron Meurer On Mon, Oct 22, 2012 at 5:40 PM, Aaron Meurer <[email protected]> wrote: > Google has announced the application period for Google Code-In 2012. > As decided earlier > (https://groups.google.com/d/topic/sympy/KrpvxADqAxM/discussion), we > should apply. See > http://www.google-melange.com/gci/homepage/google/gci2012 for more > information about it, as well as > http://code.google.com/p/google-code-in/wiki/GCIMentorInformation2012. > > The application deadline is November 5, two weeks from today. I need > help doing two things: > > - Edit the application. I have started the organization application > based on last year's at > https://github.com/sympy/sympy/wiki/GCI-2012-Organization-Application. > But we need to edit it to talk about our experiences with the program > from last year. > > - We need to create tasks. I have recreated the GCI labels in the > issue tracker. A couple of notes here: > > * There are only five categories this year. They have consolidated > outreach/research and documentation/training into single tasks, and > they have eliminated translation tasks. I haven't yet fixed this in > the issue tracker (but anyone who can add labels can bulk edit issues, > so feel free to do this). > > * They have removed the difficulty ratings. All tasks should now have > the same difficulty. The metric that they are telling us is that a > task should take an experienced project member (that's you guys) > approximately two hours to complete. Anything harder should be broken > into multiple tasks. > > We can also create tasks for SymPy-Bot, which uses the GitHub issue > tracker. See https://github.com/sympy/sympy-bot/issues?state=open. I > don't know how the permissions work with labels on GitHub, so let me > know if you are unable to add labels to issues. SymPy Live and SymPy > Gamma are also good sources for tasks (add these to the Google Code > issue tracker). > > We need to have a good chunk of tasks ready by the 5th to show Google, > but not all of them have to be created at that point. We do need to > have a certain number of each type, though. Additionally, this year, > we can add tasks at any time, so there will not be a hard deadline for > that later on like there was last year. > > - If you are interested in mentoring, please add your name to the > bottom of the application. I guess we should also create a mentors > page like the one we had last year. Also, go to google-melange.com > and create a profile (you have to do it again even if you've mentored > before, as it resets with each program). > > I would greatly appreciate help with this. > > Aaron Meurer -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
