Difference between revisions of "Task ideas for Google Code-in/Mentor guidelines"

From Apertium
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 4: Line 4:
* People who have experience using Apertium tools without having contributed to official Apertium repositories.
* People who have experience using Apertium tools without having contributed to official Apertium repositories.


Apertium makes every effort to be an inclusive community, but if you don't have any experience with Apertium tools or code, please don't bother asking to be a mentor. There's simply no tasks that you could mentor.
Apertium makes every effort to be an inclusive community, but if you don't have any experience with Apertium tools or code, please don't bother asking to be a mentor after it's already been announced that Apertium will participate. There's simply no tasks that you could mentor, and not enough time to learn.

If you are eligible, you are likely on any of several mailing lists to have received an invitation, or have been personally invited by an org admin, or have seen discussion on IRC about it and know who to ask. If you somehow missed it, please inquire on IRC or our "stuff" mailing list, or reach out to any member of the PMC.


== Guidelines for mentors ==
== Guidelines for mentors ==


=== General guidelines ===
=== During the contest ===
* Please '''commit to responding to tasks every day'''. If a task isn't accepted or returned to the student within 36 hours, Google notifies the org admins.
* Please '''commit to responding to tasks every day'''. If a task isn't accepted or returned to the student within 36 hours, Google notifies the org admins.
⚫
** If you haven't been active for 48 hours and the org admin hasn't heard from you, your published unclaimed tasks will be unpublished.
⚫
* Relatedly, please try to find someone willing to be a secondary mentor for all your tasks—ideally someone who can evaluate it in your absence.
⚫
* If you haven't been active for 48 hours and the org admin hasn't heard from you, your published unclaimed tasks will be unpublished.
* You '''must not ask students about themselves''', including where they are from. You may ask them what languages they know if it's relevant for the task.
* You '''must not ask students about themselves''', including where they are from. You may ask them what languages they know if it's relevant for the task.


=== Before GCI starts ===
=== Before GCI starts ===
* Students aren't allowed to work on tasks before GCI starts, so please don't discuss any tasks or task ideas publicly or post information about them anywhere students can find them.
* Students aren't allowed to work on tasks before GCI starts, so please don't discuss any tasks or task ideas publicly or post information about them anywhere students can find them.
⚫
* Please try to find someone willing to be a secondary mentor for all your tasks—ideally someone who can evaluate it in your absence.
* Translation tasks are not allowed. Tasks may benefit from student language knowledge, such as annotating, post-editing, or categorisation, but they must be able to be evaluated as accurate by a mentor!


[[Category:Google Code-in]]
[[Category:Google Code-in]]

Latest revision as of 13:19, 14 November 2019

Becoming a mentor[edit]

Only people who are able to mentor Apertium-related tasks are eligible to be Google Code-In mentors for Apertium. This can include:

  • Pretty much anyone who has contributed to an Apertium repository, be it a core tool, a language pair, or our IRC bot.
  • People who have experience using Apertium tools without having contributed to official Apertium repositories.

Apertium makes every effort to be an inclusive community, but if you don't have any experience with Apertium tools or code, please don't bother asking to be a mentor after it's already been announced that Apertium will participate. There's simply no tasks that you could mentor, and not enough time to learn.

If you are eligible, you are likely on any of several mailing lists to have received an invitation, or have been personally invited by an org admin, or have seen discussion on IRC about it and know who to ask. If you somehow missed it, please inquire on IRC or our "stuff" mailing list, or reach out to any member of the PMC.

Guidelines for mentors[edit]

During the contest[edit]

  • Please commit to responding to tasks every day. If a task isn't accepted or returned to the student within 36 hours, Google notifies the org admins.
    • If you haven't been active for 48 hours and the org admin hasn't heard from you, your published unclaimed tasks will be unpublished.
  • You must not ask students about themselves, including where they are from. You may ask them what languages they know if it's relevant for the task.

Before GCI starts[edit]

  • Students aren't allowed to work on tasks before GCI starts, so please don't discuss any tasks or task ideas publicly or post information about them anywhere students can find them.
  • Please try to find someone willing to be a secondary mentor for all your tasks—ideally someone who can evaluate it in your absence.
  • Translation tasks are not allowed. Tasks may benefit from student language knowledge, such as annotating, post-editing, or categorisation, but they must be able to be evaluated as accurate by a mentor!
Retrieved from "https://wiki.apertium.org/w/index.php?title=Task_ideas_for_Google_Code-in/Mentor_guidelines&oldid=70608"