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: Mon, 09 Mar 2009 19:42:57 +0000 [thread overview]
Message-ID: <E1LglNJ-0004Xk-6y@stork.gentoo.org> (raw)
dberkholz 09/03/09 19:42:57
Modified: mentoring.xml
Log:
Update for 2009.
Revision Changes Path
1.6 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.6&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/mentoring.xml?rev=1.6&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/mentoring.xml?r1=1.5&r2=1.6
Index: mentoring.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/userrel/soc/mentoring.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- mentoring.xml 19 Mar 2008 02:33:59 -0000 1.5
+++ mentoring.xml 9 Mar 2009 19:42:57 -0000 1.6
@@ -11,8 +11,8 @@
mentoring should be able to make a case as to why they want to mentor should
the SOC team have quetions.
</abstract>
-<version>1.0</version>
-<date>Feb 29, 2008</date>
+<version>1.1</version>
+<date>March 9, 2009</date>
<chapter>
<title>What it is to be a Mentor</title>
<section>
@@ -66,17 +66,14 @@
</body>
</section>
<section>
-<title>Applying to be a Mentor for GSOC 2008</title>
+<title>Applying to be a Mentor for GSOC 2009</title>
<body>
-<p>If you are interested in being a mentor for Gentoo during GSOC 2008 you may
-apply <uri link="http://code.google.com/soc/2008/mentor_step1.html">here</uri>.
-Once you apply you will be contacted by the program administrators (antarus or
-tsunam) to answer some questions about mentoring and why you have elected to be
+<p>Applications for mentorship are not yet open.
+Once you apply you will be contacted by the program administrators (dberkholz or
+antarus) to answer some questions about mentoring and why you have elected to be
a Mentor. Mentor selection is currently decided at the sole descretion of the
program administrators. All mentors should have sufficient involvement within
the Gentoo community to support their application.
-<uri link="http://code.google.com/soc/2008/mentor_step1.html">Apply to be a
-mentor here</uri>
</p>
</body>
</section>
next reply other threads:[~2009-03-09 19:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 19:42 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:52 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)
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=E1LglNJ-0004Xk-6y@stork.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