Difference between revisions of "Google Summer of Code 2012 Improvements"
Jump to navigation
Jump to search
(init, add idea) |
m (sign) |
||
| Line 3: | Line 3: | ||
* See also [[Google Summer of Code 2011 Improvements|suggestions from last year]] | * See also [[Google Summer of Code 2011 Improvements|suggestions from last year]] | ||
| − | * '''Automated blog grind-o-matic''': An idea from umbrella Python.org: They have the | + | * '''Automated blog grind-o-matic''': An idea from umbrella Python.org: They have the http://soc.python.org site which acts as a central aggregator (''Planet'') for each of the student blogs. That way mentors and students can keep track of their fellow coders, making the summer a bit less lonely, and making common expectations a bit more obvious. On top of that, Arc has it set up so that if the week ends without a blog post from any particular student, then an automated email is sent out to the student, their mentor, and the org admins. (run by a little cron job to parse the RSS feed, which I'm sure they'd share the code for) --HB |
* '''Add your idea here''': Explain it here. | * '''Add your idea here''': Explain it here. | ||
Revision as of 01:31, 11 February 2012
This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code.
- See also suggestions from last year
- Automated blog grind-o-matic: An idea from umbrella Python.org: They have the http://soc.python.org site which acts as a central aggregator (Planet) for each of the student blogs. That way mentors and students can keep track of their fellow coders, making the summer a bit less lonely, and making common expectations a bit more obvious. On top of that, Arc has it set up so that if the week ends without a blog post from any particular student, then an automated email is sent out to the student, their mentor, and the org admins. (run by a little cron job to parse the RSS feed, which I'm sure they'd share the code for) --HB
- Add your idea here: Explain it here.