Re: GSoC idea: TogetherJS

I also think it works better when the project doesn't require the student
to understand all of Plone at once. Otherwise, they spend the whole summer
getting a dev environment and figuring out how to write a test. :)


On 13 February 2014 06:06, Matthew Wilkes <matthew.wilkes-z4DKO/[email protected]> wrote:

> On 2014-02-13 05:57, Dylan Jay wrote:
>
>>  From those with experience perhaps outlining what qualities do make for
>> a good project would be helpful?
>>
>
> Honestly, the best ones are always the ones students suggest themselves.
> In general, though, something that at least some active members of the
> Plone community need. Development tools tend not to work out in the long
> run as people don't adopt them. Big pluggable features tend to bit-rot as
> they're left unsupported at PLIP phase. The right student could make either
> one work, though.
>
> I think what works best are maintenance tasks, where we have something
> that works or used to work, and we want to make better. The problem there
> is that it doesn't leave much scope for the student to leave their own
> stamp on it, so they rarely get applicants.
>
> Remember, too, the ideas list is just a list of ideas. We're not obliged
> to accept projects just because they're on that list, they're a jumping off
> board so students can get an idea of the right direction to go in when
> applying.
>
> Matt
>

------------------------------------------------------------------------------
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