Indeed, though it is quite useful, oddly, for the proposals to not be quite right (hardness etc.), it requires students to investigate and look into the problem first, that usually is a pretty good way in itself of filtering the students wanting an easy life.
Block Pointer Rewrite is a good example, they task itself is too big BUT if we get a good student interested in advanced file systems, they can (with us) probably produce a manageable deliverable and we may just get the next file system hot shot interested in further work post GSOC. Any student who just writes BPR on the form we know they clearly haven't spent even an hour looking into things. Deano -----Original Message----- From: Alan Coopersmith [mailto:[email protected]] Sent: 06 March 2011 20:09 To: OpenIndiana Developer mailing list Subject: Re: [oi-dev] Fwd: [illumos-Developer] Google Summer of Code? On 03/ 6/11 11:59 AM, Deano wrote: > I've added some from easy to hard to hopefully give Google and the students a range of things they might like to get involved with, I've added myself as mentor for most but for a few I'm not the right person or will be useful to have a few people covering it (i.e. ZFS BPR) Google Summer of Code projects are expected to be equivalent to a full-time job for 2-3 months, so things that are too easy won't qualify, but neither will things that a new developer without much experience can't complete in that amount of time. Of course, the project suggestions are just to give students ideas - students will actually have to write up a proposal when they apply and can use something the project suggested or their own idea. -- -Alan Coopersmith- [email protected] Oracle Solaris Platform Engineering: X Window System _______________________________________________ oi-dev mailing list [email protected] http://openindiana.org/mailman/listinfo/oi-dev _______________________________________________ oi-dev mailing list [email protected] http://openindiana.org/mailman/listinfo/oi-dev
