Google Code In 2017 Lessons Learned - Revision history

Madi: /* Mentors withdrawal */

2018-02-27T10:54:51Z

Mentors withdrawal

Jmckenna: /* Abandoned Tasks */

2017-12-10T14:12:23Z

Abandoned Tasks

Jmckenna: /* Abandoned Tasks */

2017-12-10T14:10:52Z

Abandoned Tasks

Jmckenna: add note on abandoned tasks

2017-12-10T13:55:11Z

add note on abandoned tasks

Madi: /* Student evaluation */

2017-11-30T16:53:19Z

Student evaluation

Madi at 16:53, 30 November 2017

2017-11-30T16:53:01Z

Jmckenna: /* Publishing Tasks */

2017-11-28T13:00:41Z

Publishing Tasks

Jmckenna: add publishing note

2017-11-28T12:58:41Z

add publishing note

Jmckenna at 21:27, 19 November 2017

2017-11-19T21:27:07Z

Cvvergara at 19:31, 16 November 2017

2017-11-16T19:31:51Z

@@ Line 54: / Line 54: @@
 == Mentors withdrawal ==
-Mentors can withdraw at any time, however they should be aware that this does create a problem. In fact, we need to know the mentor capacity '''before''' applying for GCI. Giving the availability and then withdrawing after we have been accepted as a mentor organization, or worse, disappearing in the middle of the contest, '''is not OK''', as the team will have to cope with more requests than expected and will have to dedicate extra time to fulfill the gaps. We prefer not to apply to GCI if we don't have enough mentor capacity rather than stressing ourselves beyond our limits. So please, try to avoid to give your availability if you are undecided, and limit withdrawals to very urgent / important cases.
+Mentors can withdraw at any time, however they should be aware that this does create a problem. In fact, '''we need to know the mentor capacity before applying for GCI'''. Giving the availability and then withdrawing after we have been accepted as a mentor organization, or worse, disappearing in the middle of the contest, '''is not OK''', as the team will have to cope with more requests than expected and will have to dedicate extra time to fulfill the gaps. We prefer not to apply to GCI if we don't have enough mentor capacity rather than stressing ourselves beyond our limits. So please, try to avoid to give your availability if you are undecided, and limit withdrawals to very urgent / important cases.
 == Student evaluation ==

@@ Line 39: / Line 39: @@
 * mentors should respond in the task to ask "Can I help you with what you are stuck on?", as most times the student will then re-join the task
 * task activity (comments/attachments) remains in a task that was re-joined after abandoning
 == Mentor Signup Form ==

@@ Line 38: / Line 38: @@
 * often kids are shy to ask for help and will just press 'Abandon Task' instead
 * mentors should respond in the task to ask "Can I help you with what you are stuck on?", as most times the student will then re-join the task
 == Mentor Signup Form ==

@@ Line 33: / Line 33: @@
 * tasks should be published (minimum of 75) at least the day before the contest starts
 ** published tasks won't actually be seen publicly until contest kickoff
 == Mentor Signup Form ==

@@ Line 51: / Line 51: @@
 == Student evaluation ==
-* Try not to discuss in a public channel
+Try not to discuss in a public channel
 == Submissions evaluation ==

← Older revision		Revision as of 16:53, 30 November 2017
Line 52:		Line 52:

	* Try not to discuss in a public channel		* Try not to discuss in a public channel
		+
		+	== Submissions evaluation ==
		+
		+	Mentors should evaluate submissions within 24 hours, but 12 hours is recommended. After 36 hours the dashboard sens a message to admins to take over and evaluate immediately. This must not happen. It takes years for an organization to build trustability and only 36 hours for a mentor to destroy all the work done. So mentors if you plan to be offline, organize shifts and leave notes about your evaluations so that other can evaluate the same task with the same criteria that you used. E.g. create a private document and share it to your co-mentors and admins, on which keep track of the tasks that you review and the criteria that you use, so that, if needed, others can help sort out the queue using the same criteria that you have used.
		+
		+	== Prevent cheating ==
		+
		+	Always ask students original material such as for example screenshots with their own computer with their name written in it, to prove that they actually performed the tasks ad didn't just rephrase and reuse material taken online.

	[[Category:Google Code In]]		[[Category:Google Code In]]

@@ Line 27: / Line 27: @@
 *** Deleted the duplicated tab
 *** Changed the project tab name adding a DONE as a reminder that those tasks were uploaded
 == Mentor Signup Form ==

← Older revision		Revision as of 21:27, 19 November 2017
Line 27:		Line 27:
	*** Deleted the duplicated tab		*** Deleted the duplicated tab
	*** Changed the project tab name adding a DONE as a reminder that those tasks were uploaded		*** Changed the project tab name adding a DONE as a reminder that those tasks were uploaded
		+
		+	== Mentor Signup Form ==
		+
		+	* include timezone in the Google form

← Older revision		Revision as of 19:31, 16 November 2017
Line 39:		Line 39:
	Mentors can withdraw at any time, however they should be aware that this does create a problem. In fact, we need to know the mentor capacity '''before''' applying for GCI. Giving the availability and then withdrawing after we have been accepted as a mentor organization, or worse, disappearing in the middle of the contest, '''is not OK''', as the team will have to cope with more requests than expected and will have to dedicate extra time to fulfill the gaps. We prefer not to apply to GCI if we don't have enough mentor capacity rather than stressing ourselves beyond our limits. So please, try to avoid to give your availability if you are undecided, and limit withdrawals to very urgent / important cases.		Mentors can withdraw at any time, however they should be aware that this does create a problem. In fact, we need to know the mentor capacity '''before''' applying for GCI. Giving the availability and then withdrawing after we have been accepted as a mentor organization, or worse, disappearing in the middle of the contest, '''is not OK''', as the team will have to cope with more requests than expected and will have to dedicate extra time to fulfill the gaps. We prefer not to apply to GCI if we don't have enough mentor capacity rather than stressing ourselves beyond our limits. So please, try to avoid to give your availability if you are undecided, and limit withdrawals to very urgent / important cases.

		+	== Student evaluation ==
		+
		+	* Try not to discuss in a public channel

	[[Category:Google Code In]]		[[Category:Google Code In]]