Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
dberkholz 10/04/21 01:43:25
Modified: mentoring.xml
Log:
Add a bunch of text on proposal evaluations and the role of the admin.
Revision Changes Path
1.12 xml/htdocs/proj/en/userrel/soc/mentoring.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/mentoring.xml?rev=1.12&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/mentoring.xml?rev=1.12&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/mentoring.xml?r1=1.11&r2=1.12
Index: mentoring.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/userrel/soc/mentoring.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- mentoring.xml 24 Mar 2010 21:49:58 -0000 1.11
+++ mentoring.xml 21 Apr 2010 01:43:25 -0000 1.12
@@ -79,5 +79,69 @@
</p>
</body>
</section>
+<section>
+<title>Evaluating student proposals</title>
+<body>
+<p>
+Please read and score all proposals so that we don't bias our scores
+toward ones that have more "experts" but may be less important. If you
+are an expert on specific topics, please be sure to review your
+proposals as quickly as possible so the rest of us can better judge the
+student's understanding of his project and his likelihood of success
+with it.
+</p>
+
+<p>
+If you haven't participated before, note that there are both public and
+private comments. Public comments are seen by the student, and we expect
+the student to respond. Poorly communicating students will be
+down-ranked accordingly. Private comments are for use to discuss the
+student with the other mentors.
+</p>
+
+<p>
+Please spend at least 5-15 minutes on each proposal for which you are
+not the expert (varying based on your experience level in evaluation and
+your reading speed).
+</p>
+
+<p>
+The primary goal of our participation in GSoC is to get new developers
+— when you are reading proposals, consider the quality of the student
+your #1 priority. Of course an awesome student tends to be highly
+correlated with an awesome proposal, but also consider their likelihood
+of them sticking around once the summer ends. We would rather have a new
+developer than one summer's effort.
+</p>
+
+<p>
+Once all mentors have had a chance to evaluate the proposals, the
+organization adminstrator will take their rankings into account, as well
+as their own expertise and the selection criteria mentioned above, in
+creating the final list of students.
+</p>
+
+</body>
+</section>
+<section>
+<title>The role of the organization administrator</title>
+<body>
+
+<p>
+The organization administrator is ultimately responsible for the success
+of the program. In Google's eyes, this means both <uri
+link="http://socghop.appspot.com/document/show/program/google/gsoc2009/studentallocations">passing
+students and new developers</uri> — this is one reason for
+our focus on potential developers over a summer's work from someone who
+will never return. Administrators are expected to have experience with
+GSoC and will be knowledgeable about all aspects of the program,
+including the high standards expected of students and proposals, the
+culture of the Google Summer of Code program, and what it takes for
+projects to be successful. The administrator has the final word on all
+aspects of the program, from mentor selection to student ranking.
+</p>
+
+</body>
+</section>
</chapter>
</guide>
|
|
