Re: [GSOC] Re: [PHP-DEV] About GSoC 2009

>
>  all students work inside php cvs. Be it in core,
> a pecl module, a pear module or some documentation related project.


+1


>
> So maybe we can finally agree on these points. And then we'll see
> for ways to kick mentors to respect them and not do their own thing.
> That said, what are we going to do about non direct PHP projects
> this year? With what was brought up in this thread I don't think
> we should do any of those. Other opinions?


One of the things I have personally found very productive in running PEAR's
bug triage days is documenting things in the wiki constantly, and doing a
summary blog post.

An example:
http://wiki.php.net/pear/qa/bug_triage/2009-02-07

and
http://clockwerx.blogspot.com/2009/02/pear-bug-day-roundup-feb-7th-2009.html

This lets me and others participating document what we're doing, and it
provides good visibility to people who are interested.

What you don't see is that I'm also talking to people on #pear and by
mailing list posts; but *all of the tasks and status changes end up in the
wiki*.


To that end I would suggest strongly documenting plans & todo lists in the
wiki and updating them each week at a set time.
That's a responsibility for the mentor to enforce; and allows for others to
step in if that mentor 'gets busy'.

Encourage students into irc for discussion; but documenting outcomes of
meetings / discussions is something constantly hammered home.


The role of specific mailing lists? To receive emails like "Oh hi guys, this
week's gsoc summary is.... (link) "