Difference between revisions of "Google Summer of Code/Review process"

From Apertium
Jump to navigation Jump to search
(Created page with "How the review process works in Apertium: * Students submit proposals until the deadline * Students and mentors match up * Proposals that have students are put into a spreads...")
 
 
Line 3: Line 3:
* Students submit proposals until the deadline
* Students submit proposals until the deadline
* Students and mentors match up
* Students and mentors match up
* Proposals that have students are put into a spreadsheet
* Proposals that have mentors are put into a spreadsheet
* Each proposal is ranked by all of the mentors, mentors submit their ranking at any point during the review period
* Each proposal is ranked by all of the mentors, mentors submit their ranking at any point during the review period
* The ranking period / review process closes some time before Google slot requests are due
* The ranks are averaged and the result is sent to the [[PMC]] for review
* The mentors' ranks are averaged and the result is sent to the [[PMC]] for review
⚫
* The PMC may make changes and then the top <math>N</math> are accepted, where <math>N</math> is the number of slots we get from Google
* The PMC may make changes, and a number of slots is requested from Google
⚫
* The top <math>N</math> students are accepted, where <math>N</math> is the number of slots we get from Google


What this means for students:
What this means for students:
Line 12: Line 14:
* You must submit your proposal to Google before the deadline
* You must submit your proposal to Google before the deadline
* You should actively try and find a mentor among Apertium contributors
* You should actively try and find a mentor among Apertium contributors
* You can submit a proposal with an incomplete coding challenge, and you have the length of the review process to finish it, but the longer it remains incomplete, the more mentors will have reviewed your proposal.
* You can submit a proposal with an incomplete coding challenge, and you have the length of the review process (see above) to finish it, but the longer it remains incomplete, the more mentors will have reviewed your proposal.




Latest revision as of 05:02, 7 April 2019

How the review process works in Apertium:

  • Students submit proposals until the deadline
  • Students and mentors match up
  • Proposals that have mentors are put into a spreadsheet
  • Each proposal is ranked by all of the mentors, mentors submit their ranking at any point during the review period
  • The ranking period / review process closes some time before Google slot requests are due
  • The mentors' ranks are averaged and the result is sent to the PMC for review
  • The PMC may make changes, and a number of slots is requested from Google
  • The top students are accepted, where is the number of slots we get from Google

What this means for students:

  • You must submit your proposal to Google before the deadline
  • You should actively try and find a mentor among Apertium contributors
  • You can submit a proposal with an incomplete coding challenge, and you have the length of the review process (see above) to finish it, but the longer it remains incomplete, the more mentors will have reviewed your proposal.
Retrieved from "https://wiki.apertium.org/w/index.php?title=Google_Summer_of_Code/Review_process&oldid=69421"