Google Code-in 2016 just started and we need your help!

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Google Code-in 2016 just started and we need your help!

Andre Klapper-2
Google Code-in 2016 just started:
https://www.mediawiki.org/wiki/Google_Code-in_2016

In the next seven weeks, many young people are going to make their
first contributions to Wikimedia. Expect many questions on IRC and
mailing lists by onboarding newcomers who have never used IRC or lists
before. Your help and patience is welcome to provide a helping hand!

Thanks to all mentors who have already registered & provided tasks!

You have not become a mentor yet? Please do consider it.
It is fun and we do need more tasks! :)

* Think of easy tasks in your area that you could mentor.
  Areas are: Code, docs/training, outreach/research, quality
  assurance, and user interface. "Easy" means 2-3h to complete for
  you, or less technical ~30min "beginner tasks" for onboarding).
* OR: provide an easy 'clonable' task (a task that is generic and
  could be repeated many times by different students).
* Note that you commit to answer to students' questions and to
  evaluate their work within 36 hours (but the better your task
  description the less questions. No worries, we're here to help!)

For the full info, please check out
https://www.mediawiki.org/wiki/Google_Code-in_2016/Mentors
and ask if something is unclear!

Thank you again for giving young contributors the opportunity to learn
about and work on all aspects of Free & Open Source Software projects!

Cheers,
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/

_______________________________________________
Wikitech-l mailing list
[hidden email]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Reply | Threaded
Open this post in threaded view
|

Re: Google Code-in 2016 just started and we need your help!

John Mark Vandenberg
What happens if a mentor doesn't respond with 36 hrs?
The weekend is going to be the most problematic stage, especially this
first weekend.

Does this "36 hrs" also apply to reviewing in Gerrit and comments in
Phabricator?

I am seeing students not submit their GCI task for approval once they
have uploaded their patch into Gerrit.  This is actually "good" in one
sense, as they haven't finished the task until it is merged, but if we
are not tracking Gerrit review times of GCI patches, it means the
mentors are not obligated to do code review with 36 hrs and the
participants are surprised at how long the code review phase is
taking. (48 hrs in one case).

Is there any warning when the 36 hour limit is approaching?

Are Wikimedia org admins watching this limit somehow?
Is there some process in place?
e.g. 24 hr "this is getting worrying" status, where we find another
mentor / code reviewer?


On Tue, Nov 29, 2016 at 12:00 AM, Andre Klapper <[hidden email]> wrote:

> Google Code-in 2016 just started:
> https://www.mediawiki.org/wiki/Google_Code-in_2016
>
> In the next seven weeks, many young people are going to make their
> first contributions to Wikimedia. Expect many questions on IRC and
> mailing lists by onboarding newcomers who have never used IRC or lists
> before. Your help and patience is welcome to provide a helping hand!
>
> Thanks to all mentors who have already registered & provided tasks!
>
> You have not become a mentor yet? Please do consider it.
> It is fun and we do need more tasks! :)
>
> * Think of easy tasks in your area that you could mentor.
>   Areas are: Code, docs/training, outreach/research, quality
>   assurance, and user interface. "Easy" means 2-3h to complete for
>   you, or less technical ~30min "beginner tasks" for onboarding).
> * OR: provide an easy 'clonable' task (a task that is generic and
>   could be repeated many times by different students).
> * Note that you commit to answer to students' questions and to
>   evaluate their work within 36 hours (but the better your task
>   description the less questions. No worries, we're here to help!)
>
> For the full info, please check out
> https://www.mediawiki.org/wiki/Google_Code-in_2016/Mentors
> and ask if something is unclear!
>
> Thank you again for giving young contributors the opportunity to learn
> about and work on all aspects of Free & Open Source Software projects!
>
> Cheers,
> andre
> --
> Andre Klapper | Wikimedia Bugwrangler
> http://blogs.gnome.org/aklapper/
>
> _______________________________________________
> Wikitech-l mailing list
> [hidden email]
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



--
John Vandenberg

_______________________________________________
Wikitech-l mailing list
[hidden email]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Reply | Threaded
Open this post in threaded view
|

Re: Google Code-in 2016 just started and we need your help!

Strainu
2016-12-03 13:25 GMT+02:00 John Mark Vandenberg <[hidden email]>:
> Is there any warning when the 36 hour limit is approaching?
>
> Are Wikimedia org admins watching this limit somehow?
> Is there some process in place?
> e.g. 24 hr "this is getting worrying" status, where we find another
> mentor / code reviewer?

John,

There was an email sent to mentors which says:

"Mentors do have 24h of time to review and reply to questions until
Google will send a reminder email, and a maximum of 36h in total.
However, if you plan to be off for a weekend or take holidays, please
either do tell us (admins could also add more co-mentors to a task if
you have somebody in mind), or when creating tasks simply put some
"[DONT PUBLISH BEFORE 20161231]" prefix or such into the task summary."

Strainu

_______________________________________________
Wikitech-l mailing list
[hidden email]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l