Apertium has moved from SourceForge to GitHub.
If you have any questions, please come and talk to us on #apertium on irc.freenode.net or contact the GitHub migration team.

Task ideas for Google Code-in/Mentor guidelines

From Apertium
< Task ideas for Google Code-in(Difference between revisions)
Jump to: navigation, search
m (Guidelines for mentors)
Line 12: Line 12:
 
* 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.
   
[[Category:Google Code-In]]
+
[[Category:Google Code-in]]

Revision as of 19:30, 3 November 2019

Becoming a mentor

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. There's simply no tasks that you could mentor.

Guidelines for mentors

  • 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.
  • 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.
Personal tools