From: "Donnie Berkholz (dberkholz)" <dberkholz@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/userrel/soc: mentoring.xml
Date: Wed, 21 Apr 2010 01:52:57 +0000 (UTC) [thread overview]
Message-ID: <20100421015258.0D5CF2C04B@corvid.gentoo.org> (raw)
dberkholz 10/04/21 01:52:57
Modified: mentoring.xml
Log:
More text on what admins do.
Revision Changes Path
1.13 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.13&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/mentoring.xml?rev=1.13&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/mentoring.xml?r1=1.12&r2=1.13
Index: mentoring.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/userrel/soc/mentoring.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- mentoring.xml 21 Apr 2010 01:43:25 -0000 1.12
+++ mentoring.xml 21 Apr 2010 01:52:57 -0000 1.13
@@ -128,17 +128,29 @@
<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.
+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. Admins should have good relationships with the Google
+employees running GSoC, to <uri
+link="http://socghop.appspot.com/document/show/program/google/gsoc2009/orgcriteria">maximize
+our chances</uri> of being selected for GSoC in the future.
+</p>
+
+<p>
+Administrators ensure that a good list of project ideas is submitted,
+write the organization application, select mentors, make final student
+selections, ensure mentoring is going well, resolve any conflicts, and
+are generally responsible for anything outside of mentoring individual
+students. The administrator has the final word on all aspects of the
+program, from mentor selection to student ranking.
</p>
</body>
next reply other threads:[~2010-04-21 1:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 1:52 Donnie Berkholz (dberkholz) [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-13 19:29 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/userrel/soc: mentoring.xml Donnie Berkholz (dberkholz)
2010-04-24 17:24 Donnie Berkholz (dberkholz)
2010-04-21 2:01 Donnie Berkholz (dberkholz)
2010-04-21 1:55 Donnie Berkholz (dberkholz)
2010-04-21 1:54 Donnie Berkholz (dberkholz)
2010-04-21 1:43 Donnie Berkholz (dberkholz)
2009-03-09 19:43 Donnie Berkholz (dberkholz)
2009-03-09 19:43 Donnie Berkholz (dberkholz)
2009-03-09 19:42 Donnie Berkholz (dberkholz)
2008-03-19 2:34 Alec Warner (antarus)
2008-03-09 12:05 Alec Warner (antarus)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100421015258.0D5CF2C04B@corvid.gentoo.org \
--to=dberkholz@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox