GSoC projects: lessons learned

We have quite a lot of experience of GSoC now. It would be valuable collecting what projects worked and what didn't, to inform this year's evaluation.

>From my own memory:


 - things where we have existing community members who happen to be students (eg Timo), working on core stuff (eg p.a.discussion)
 - things that have a limited scope and are easy to learn (building Diazo themes)
 - students who are mature and motivated
 - students who write their own proposals
 - mentors who make time and set a regular (weekly) meeting schedule


I have a feeling a lot of submissions last year were motivated more by money than consideration for the community.


Things that have failed:


 - stuff no one understands (WTF is a "buildout builder")
 - stuff in alien technologies (Laszlo (!), native apps)
 - things that require deep knowledge of core (building p.a.portlets; replacing PAS with PAU)
 - things that require above normal programming talent (designing APIs, addressing really old concerns)
 - things that require hundreds of man hours and are dull (replace all skin templates with views) 


I feel we have more failures than successes, but I may be pessimistic. What else have we had?


Martin
—
Sent from Mailbox for iPad

------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers