Difference between revisions of "Google Summer of Code 2012 Improvements"
Jump to navigation
Jump to search
m (sign) |
|||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | <center> | |
| + | [[Image:Gsoc-2012-logo-color.png|250px]] <font size="+3"> @ </font> [[Image:OSGeo_300_127_pixel.png|200px]] | ||
| + | </center> | ||
| − | * See also [[Google Summer of Code 2011 Improvements|suggestions from last year]] | + | |
| + | == This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code == | ||
| + | |||
| + | * 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 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 | * '''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 | ||
| + | |||
| + | * '''Remove Mentor form registration''' Several mentors didn't register in Melange after filling the OSGeo mentor form. I suppose it looks like the final step, whereas it is only for internal use. Actually, admins could ask for the same information in the Mentor registration on Melange. --AG | ||
* '''Add your idea here''': Explain it here. | * '''Add your idea here''': Explain it here. | ||
| + | |||
| + | |||
| + | [Back to [[Google Summer of Code 2012]] @ OSGeo] | ||
[[Category:Google Summer of Code]] | [[Category:Google Summer of Code]] | ||
Latest revision as of 05:01, 30 March 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
- Remove Mentor form registration Several mentors didn't register in Melange after filling the OSGeo mentor form. I suppose it looks like the final step, whereas it is only for internal use. Actually, admins could ask for the same information in the Mentor registration on Melange. --AG
- Add your idea here: Explain it here.
[Back to Google Summer of Code 2012 @ OSGeo]