Surprised? Me too!
Please read / watch / discuss https://www.mediawiki.org/wiki/Summer_of_Code_2013
*Nothing* about GSOC 2013 is confirmed at this point, but there is no harm in starting collecting ideas and recruiting participants.
Your feedback is welcome at the wiki page - or here if you are really really lazy. Reason: potential participants visiting that page in the near future will have an easier time following background discussions if they are take place there.
Thank you!
hi,
Can you explain the roles of mentors and admins? Also what is requirement for participants? I suppose it's for students?
On Thu, Jan 17, 2013 at 8:32 PM, Quim Gil qgil@wikimedia.org wrote:
Surprised? Me too!
Please read / watch / discuss https://www.mediawiki.org/**wiki/Summer_of_Code_2013https://www.mediawiki.org/wiki/Summer_of_Code_2013
*Nothing* about GSOC 2013 is confirmed at this point, but there is no harm in starting collecting ideas and recruiting participants.
Your feedback is welcome at the wiki page - or here if you are really really lazy. Reason: potential participants visiting that page in the near future will have an easier time following background discussions if they are take place there.
Thank you!
-- Quim Gil Technical Contributor Coordinator @ Wikimedia Foundation http://www.mediawiki.org/wiki/**User:Qgilhttp://www.mediawiki.org/wiki/User:Qgil
______________________________**_________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/**mailman/listinfo/wikitech-lhttps://lists.wikimedia.org/mailman/listinfo/wikitech-l
One thing I would like to see is code from projects being merged into core at a regular basis instead of just at the end. Obviously that might not be possible for all projects depending on what your project is, but many that modify core can be done in incremental steps. I don't know about last year specificly but in other years there have been gsoc projects coded away happily in branches, getting code review but not held to the same standard as core was. When they tried to merge it the student gets a rather rude awekening with all sorts of objections to their code they didnt expect.
Tl; dr: good in depth feedback early and often is critical for success. If we make people merge their projects in small steps as they complete independant features (like once every 2 weeks) gsocers get better feedback and no giant painful merge at the end.
-bawolff On 2013-01-17 3:47 PM, "Petr Bena" benapetr@gmail.com wrote:
hi,
Can you explain the roles of mentors and admins? Also what is requirement for participants? I suppose it's for students?
On Thu, Jan 17, 2013 at 8:32 PM, Quim Gil qgil@wikimedia.org wrote:
Surprised? Me too!
Please read / watch / discuss https://www.mediawiki.org/**wiki/Summer_of_Code_2013<
https://www.mediawiki.org/wiki/Summer_of_Code_2013%3E
*Nothing* about GSOC 2013 is confirmed at this point, but there is no
harm
in starting collecting ideas and recruiting participants.
Your feedback is welcome at the wiki page - or here if you are really really lazy. Reason: potential participants visiting that page in the
near
future will have an easier time following background discussions if they are take place there.
Thank you!
-- Quim Gil Technical Contributor Coordinator @ Wikimedia Foundation http://www.mediawiki.org/wiki/**User:Qgil<
http://www.mediawiki.org/wiki/User:Qgil%3E
______________________________**_________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/**mailman/listinfo/wikitech-l<
https://lists.wikimedia.org/mailman/listinfo/wikitech-l%3E
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hello,
On Thu, Jan 17, 2013 at 9:08 PM, Bawolff Bawolff bawolff@gmail.com wrote:
One thing I would like to see is code from projects being merged into core at a regular basis instead of just at the end. Obviously that might not be possible for all projects depending on what your project is, but many that modify core can be done in incremental steps. I don't know about last year specificly but in other years there have been gsoc projects coded away happily in branches, getting code review but not held to the same standard as core was. When they tried to merge it the student gets a rather rude awekening with all sorts of objections to their code they didnt expect.
Tl; dr: good in depth feedback early and often is critical for success. If we make people merge their projects in small steps as they complete independant features (like once every 2 weeks) gsocers get better feedback and no giant painful merge at the end.
I concur and offer to document that. Something like this text could be used in this purpose.
== Tips == === Push to Gerrit to show your code. In code review we trust. ===
MediaWiki uses a continuous integration model. Code is first peer-reviewed: other developers provide feedback about your code, approve it or recommend improvements. Jenkins tests run too, to ensure your code doesn't break anything. When your change is ready, it's merged in the master branch of our code repository.
Follow this workflow. Push your code to Gerrit when you want to show it. Add your mentor as reviewer. Others will join the conversation on a regular basis. You'll learn a lot from the others reviewers' feedback.
And the greatest bonus? Your code will be merged on a continuous basis. You will directly be able to see your code live and in production. This is what we're calling the continuous integration.
On Mon, Jan 21, 2013 at 12:28 AM, Sébastien Santoro dereckson@espace-win.org wrote:
I concur and offer to document that. Something like this text could be used in this purpose.
== Tips == === Push to Gerrit to show your code. In code review we trust. ===
MediaWiki uses a continuous integration model. Code is first peer-reviewed: other developers provide feedback about your code, approve it or recommend improvements. Jenkins tests run too, to ensure your code doesn't break anything. When your change is ready, it's merged in the master branch of our code repository.
Follow this workflow. Push your code to Gerrit when you want to show it. Add your mentor as reviewer. Others will join the conversation on a regular basis. You'll learn a lot from the others reviewers' feedback.
And the greatest bonus? Your code will be merged on a continuous basis. You will directly be able to see your code live and in production. This is what we're calling the continuous integration.
A few GSoC admins (including me) wrote these some time ago: * http://google-opensource.blogspot.de/2011/03/dos-and-donts-of-google-summer-... * http://google-opensource.blogspot.de/2011/04/dos-and-donts-of-google-summer-... * http://google-opensource.blogspot.de/2011/04/dos-and-donts-of-google-summer-...
Cheers Lydia
-- Lydia Pintscher - http://about.me/lydia.pintscher Community Communications for Wikidata
Wikimedia Deutschland e.V. Obentrautstr. 72 10963 Berlin www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
wikitech-l@lists.wikimedia.org