Page MenuHomePhabricator

Lessons learned from GSoC 2015 and Outreachy 10
Closed, ResolvedPublic

Description

https://www.mediawiki.org/wiki/Outreach_programs/Lessons_learned needs to be updated with the lessons learned during Google-Summer-of-Code (2015) / Outreachy-Round-10. This is an important document, we point candidates, mentors, and org admins to it as soon as they get ready for a new round. This is how we try to avoid repeating the same mistakes.

Event Timeline

Qgil raised the priority of this task from to Medium.
Qgil updated the task description. (Show Details)

The documentation at https://www.mediawiki.org/wiki/Outreach_programs/Lessons_learned looks almost complete to me though. Of course, it can be enhanced. Few points from my experience would be:

  1. Weekly meetings properly scheduled using one of the programs out there ( Google Calendar is great ) would make sure that the team communicates regularly, and stays focused.
  2. Regular updates to Wikitech-l makes sure that people are informed, and of course there will be people coming in between telling you never gave them notice - but you should have some threads in some mailing list to answer with
  3. A minimum viable product with all basic functionalities up in labs before mid term worked very well for @Qgil, @Tinaj1234 and me with the MediaWiki-extensions-Newsletter extension.

I hope most of them are already mentioned in the link above though

@01tonythomas:

  1. Weekly meetings properly scheduled using one of the programs out there ( Google Calendar is great ) would make sure that the team communicates regularly, and stays focused.

There is the line "Recurrent weekly calls are useful, as long as they don't substitute the regular communication in public channels." Shall we change that to "Recurrent and properly scheduled weekly meetings are useful to make sure the team stays focused and aligned, as long as these meetings don't substitute the regular communication in public channels." ?

  1. Regular updates to Wikitech-l makes sure that people are informed, and of course there will be people coming in between telling you never gave them notice - but you should have some threads in some mailing list to answer with

Three sentences which sound related: "Interns must send a summary of their project at wikitech-l at the end of the program.", "Weekly reports must be required and plugged to Wikimedia's pyramid of reports", and "Proposals must go through public community review."
What about asking people to not only inform wikitech-l at the end (and potentially when proposing), but also at the beginning of the three months and at mid-term? It could be a simple email with project summary/short desc and a link to wherever the weekly reporting takes place.

  1. A minimum viable product with all basic functionalities up in labs before mid term worked very well for @Qgil, @Tinaj1234 and me with the MediaWiki-extensions-Newsletter extension.

Already covered by the line "Define a minimum viable product and focus in getting it deployed as soon as possible."?

Feel free to revert if it looks too descriptive !

Thanks. It looks good and I've edited it a bit further: https://www.mediawiki.org/w/index.php?title=Outreach_programs%2FLessons_learned&type=revision&diff=1913460&oldid=1910776 for your+my changes combined.

So from my point of view we are done here. :)

Assigning this task to Tony because it is in the DevRel-October-2015 sprint and he is the main org admin. Feel free to assign it to someone else if this is not correct.

The page https://www.mediawiki.org/wiki/Outreach_programs/Lessons_learned looks great as of now though - thanks to @Aklapper but sure - there is no upper limit :)

@01tonythomas: Are there more lessons learned / do you have more in mind? Or are you waiting for more input from some specific people (who?) on this task? If "no" is the answer to both questions then I propose you close this task as resolved.

This one looks resolved. Closing.