From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from )
id 1JWS4A-0005eb-5v
for garchives@archives.gentoo.org; Tue, 04 Mar 2008 08:00:02 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 410F5E0455;
Tue, 4 Mar 2008 08:00:01 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
by pigeon.gentoo.org (Postfix) with ESMTP id C57F6E0455
for ; Tue, 4 Mar 2008 08:00:00 +0000 (UTC)
Received: from stork.gentoo.org (stork.gentoo.org [64.127.104.133])
(using TLSv1 with cipher AES256-SHA (256/256 bits))
(No client certificate requested)
by smtp.gentoo.org (Postfix) with ESMTP id 50DCD663A8
for ; Tue, 4 Mar 2008 08:00:00 +0000 (UTC)
Received: from antarus by stork.gentoo.org with local (Exim 4.68)
(envelope-from )
id 1JWS47-0002xx-2f
for gentoo-commits@lists.gentoo.org; Tue, 04 Mar 2008 07:59:59 +0000
From: "Alec Warner (antarus)"
To: gentoo-commits@lists.gentoo.org
Reply-To: gentoo-dev@lists.gentoo.org, antarus@gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/userrel/soc: applying.xml index.xml mentoring.xml
X-VCS-Repository: gentoo
X-VCS-Files: applying.xml index.xml mentoring.xml
X-VCS-Directories: xml/htdocs/proj/en/userrel/soc
X-VCS-Committer: antarus
X-VCS-Committer-Name: Alec Warner
Content-Type: text/plain; charset=utf8
Message-Id:
Sender: Alec Warner
Date: Tue, 04 Mar 2008 07:59:59 +0000
Precedence: bulk
List-Post:
List-Help:
List-Unsubscribe:
List-Subscribe:
List-Id: Gentoo Linux mail
X-BeenThere: gentoo-commits@lists.gentoo.org
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: ec14bdf1-2549-43eb-b30b-d6bb7f20d01e
X-Archives-Hash: 1d6a72abd0759e7ddad4dec23b341851
antarus 08/03/04 07:59:59
Modified: applying.xml index.xml mentoring.xml
Log:
index.xml to 80 chars, remove badly defined projects, other minor chang=
es.
Revision Changes Path
1.2 xml/htdocs/proj/en/userrel/soc/applying.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/use=
rrel/soc/applying.xml?rev=3D1.2&view=3Dmarkup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/use=
rrel/soc/applying.xml?rev=3D1.2&content-type=3Dtext/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/use=
rrel/soc/applying.xml?r1=3D1.1&r2=3D1.2
Index: applying.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/userrel/soc/applying.xml=
,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- applying.xml 2 Mar 2008 10:17:54 -0000 1.1
+++ applying.xml 4 Mar 2008 07:59:58 -0000 1.2
@@ -71,7 +71,10 @@
Biography - The student should talk about themselves: where they a=
re from
what they like to study, what they do in their free time, etc. Part o=
f this
contest is to make new friends and learn about each other and this is =
an
- important part of that goal.
+ important part of that goal. This section should include things like =
previous
+ jobs, internships, and any educational experience an applicant may hav=
e. This
+ section is also intended to promote oneself and convince Gentoo that w=
e should
+ chose a given student over other applicants.
- - Willing - A mentor should be willing to mentor. Mentoring is not =
a
+
- Willing - A mentor should be willing to mentor. Mentoring =
is not a
forced activity and it is not required. A mentor should not mentor
half-heartedly. The Summer of Code experience is a great experience f=
or
students and part of that experience is having some help along the way=
. It
is also a great opportunity to recruit new people into a project and t=
his
opportunity should not be squandered. Of course mentoring also offers=
a
great opportunity for friendship.
- - Informed - A mentor should know what they are signing up for; gene=
rally
+
- Informed - A mentor should know what they are signing up fo=
r; generally
by reading this document. A mentor should be aware of the time requir=
ements
and any mentor who knows they cannot devote the time required should p=
robably
take a back-seat role; perhaps as a secondary or backup mentor.
- - Capable - A mentor should be capable of mentoring for the given ta=
sk.
+
- Capable - A mentor should be capable of mentoring for the g=
iven task.
Knowledge of the language the student is using is important as is know=
ledge
of the problem domain. The student will (hopefully) be asking questio=
ns
about the project and their implementation (and as a mentor you should
arguably be questioning their implementation as you review it.)
- - Sociable - A mentor should try to foster a relationship with the s=
tudent.
+
- Sociable - A mentor should try to foster a relationship wit=
h the student.
It is important to critique the students work in a professional manner=
.
Complaints about rudeness and abuse should be filed to the GSoc team l=
ead
and/or the Google Summer of Code staff.
@@ -49,12 +49,12 @@
critiquing the student and insuring the student is making progress. The=
se are
roles generally performed by a 'Tech Lead' or 'Project Manager'. A pers=
on
interested in mentoring should be prepared to do these tasks.
-Helping the Student:
+
Helping the Student:
The mentor should assist the student with common questions about the dom=
ain
area, implementation and language specifics. As a mentor you should not=
write
the code for the student; however using unrelated examples that can comm=
unicate
your point to the student are a good tool.
-Critiquing the student:
+
Critiquing the student:
As a mentor you should review the student's work on a regular basis. A
recommendation that has worked in the past is every week; however you ca=
n the
student should discuss meeting times, number of meetings, and meeting du=
ration.
--=20
gentoo-commits@lists.gentoo.org mailing list