Thanks for pulling this together Ross! I agree sharing successes / lessons learned is a very important part of GSoC.
I'm having trouble editing the page with Apache CMS. (This is my first time using CMS so this could easily be user error somewhere...). I installed the CMS bookmarklet, navigated to http://community.apache.org/mentoring/experiences.html, and then clicked it (the bookmarklet), but that redirects me to this URL: https://cms.apache.org/community/wc/browse/mikemccand-voFLne/trunk (The top-level page for "community" ... and I can't find any "mentoring" subdir there). If instead I go to http://lucene.apache.org/core/features.html and click the bookmarklet, it looks like it's working correctly ... Not sure what's up but any help would be appreciated! Mike McCandless http://blog.mikemccandless.com On Wed, Aug 22, 2012 at 6:01 AM, Ross Gardler <rgard...@opendirective.com> wrote: > In the past we've done a really poor job of highlighting the successes > of GSoC for the ASF and for the students. One reason for this is that > it takes quite a bit of work to collate all the information and admins > are most busy during the periods when mentors are reaching out (during > proposal phase) and wrapping up (during evaluation phase). > > It would be great if mentors, and their students, could help us out by > recording any useful information about successes (and failures if it > can be constructive) on the page at [1] (all committed should have > write access via the CMS). > > What we are looking for is things like: > > * blog posts > * updates on students engagement beyond GSoC > * identification of ASF success stories (e.g. students that have > become key to the ASF as a whole) > * the benefits of GSoC + TAC support > * statistics that paint a picture > * anything else > > Note, this page is not currently prominently linked as it is quite > sparse right now (it is linked from the upcoming board reprot though). > It is only semi-private so keep the information factual and > constructive. > > Ross > > -- > Ross Gardler (@rgardler) > Programme Leader (Open Development) > OpenDirective http://opendirective.com
