[Members] GSoC

bear bear42 at gmail.com
Fri Feb 26 14:44:13 CST 2010


unless someone with more XSF experience steps forward I may consider this.

I'm starting a new job at Mozilla next week and they grok open source
so I would be able to work on this during $dayjob hours, but I would
for sure need a lot of help from the team members and mentors as I've
never participated in GSoC

This will definitely fill up my XSF project time, heck probably my
XMPP project time, completely

So if the others don't throw large bulky objects at my head...


On Fri, Feb 26, 2010 at 15:02, Peter Saint-Andre <stpeter at stpeter.im> wrote:
> Yes, I have always been the org admin -- and I've always been too busy
> to make that trip to Mountain View...
>
> On 2/26/10 12:36 PM, Arc Riley wrote:
>> The org admin role cannot be split, though there may be a backup.
>>
>> The org admin is a thankless job that should only be taken on by a
>> really dedicated volunteer, messing up would hurt the XSF's future
>> ability to participate in the program.
>>
>> As a small award, however, the org admin gets a free all-expense paid
>> trip to Mountain View, CA for the GSoC mentors summit in the Fall - so
>> maybe not all thankless.
>>
>> The org admin should be the one to write the XSF's application and most
>> of the other tasks Peter listed.
>>
>> On Thu, Feb 25, 2010 at 6:49 PM, Fabio Forno <fabio at bluendo.com
>> <mailto:fabio at bluendo.com>> wrote:
>>
>>     On Fri, Feb 26, 2010 at 12:39 AM, Peter Saint-Andre
>>     <stpeter at stpeter.im <mailto:stpeter at stpeter.im>> wrote:
>>     > Well, we seem to have consensus. Now who is going to do the work?
>>     And I
>>     > assure you that it is a lot of work! Here are the "Top 20" tasks
>>     you can
>>     > look forward to:
>>     >
>>     > 1. Writing the XSF's application to be an official GSoC organization
>>     > 2. Finding and interviewing potential mentors
>>     > 3. Defining potentially interesting projects
>>     > 4. Reading dozens and dozens of applications on very short notice
>>     > 5. Exhorting the mentors to read those applications, too
>>     > 6. Collating the votes and making the final decisions
>>     > 7. Handling the transition from selection to actual work
>>     > 8. For mentors, babysitting the students
>>     > 9. For the org admin, babysitting the mentors :)
>>     > 10. Getting everyone to report on their progress regularly
>>     > 11. Holding weekly / fortnightly groupchat meetings
>>     > 12. Making sure that everyone is on track at all times
>>     > 13. Completing the first-half progress check / report
>>     > 14. Dropping students who aren't making sufficient progress
>>     > 15. Finding replacement mentors if necessary
>>     > 16. Pushing through the second half of GSoC to project completion
>>     > 17. Frantically taking care of last-minute disasters
>>     > 18. Writing and submitting a final report to Google
>>     > 19. Keeping after Google for payment
>>     > 20. Disbursing funds to our mentors
>>     >
>>     > I can assure you that I simply don't have time for all those tasks, or
>>     > even for any of them. So who is going to step forward?
>>     >
>>
>>     split responsibilities:
>>     - administration stuff and relations with google by the board
>>     - project selection by the council and the board
>>     - project running/monitoring by a special team formed by mentors which
>>     are also members and with one of council as lead
>>
>>     --
>>     Fabio Forno,
>>     Bluendo srl http://www.bluendo.com
>>     jabber id: ff at jabber.bluendo.com <mailto:ff at jabber.bluendo.com>
>>
>
>



-- 
Bear

bear42 at gmail.com (xmpp, email)
bear at code-bear.com (xmpp, email)
http://code-bear.com/bearlog (weblog)

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29


More information about the Members mailing list