* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/userrel/soc: applying.xml mentoring.xml
@ 2008-03-02 10:17 Alec Warner (antarus)
0 siblings, 0 replies; only message in thread
From: Alec Warner (antarus) @ 2008-03-02 10:17 UTC (permalink / raw
To: gentoo-commits
antarus 08/03/02 10:17:54
Added: applying.xml mentoring.xml
Log:
Get some drafts up in anticipation for application
Revision Changes Path
1.1 xml/htdocs/proj/en/userrel/soc/applying.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/applying.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/applying.xml?rev=1.1&content-type=text/plain
Index: applying.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide>
<title>Summer of code application guide</title>
<author>antarus</author>
<abstract>This guide is intended to be read by anyone who is interested
in applying to Gentoo in the Google Summer of Code event. Interested students
need not be Gentoo Developer, anyone who meets the Eligibility requirements of
Google is encouraged to apply.
</abstract>
<version>1.0</version>
<date>March 1, 2008</date>
<chapter>
<title>Applying as a student</title>
<section>
<title>Communication</title>
<body>
<p>Students interested in applying to do a project for Gentoo should join
#gentoo-soc on irc.freenode.net and/or join the gentoo-soc mailing list.
Announcements related to Gentoo's summer of code effort will be relayed to both
places</p>
</body>
</section>
</chapter>
<chapter>
<title>What interested students need to do</title>
<section>
<title>Get feedback on your idea</title>
<body>
<p>Students interested in applying to do a project for Gentoo should review
the projects <uri link="index.xml">listed</uri>. You are free to apply for a
project that is not on our list. In either case once you have an idea of what
you want to work on you should find someone to discuss it with it. The
gentoo-soc mailing list, #gentoo-soc on irc.freenode.net or any of the
listed <uri link="index.xml">mentors</uri> should be able to provide feedback.
</p>
</body>
</section>
<section>
<title>Write a proposal</title>
<body>
<p>Students should author a proposal that attempts to convince Gentoo why
their project should be chosen over other competing proposals. A few sentences
is not sufficient in most cases to sway anyone.
</p>
<ol>
<li>Objective - What problem does the project solve. This does not need to
be a long section. Generally software tries to help make people more
efficient, or foster communication, or entertain folks. Any proposed
software should have a purpose and applicants should define that purpose
here.</li>
<li>Abstract - What does the project do; try to keep this section to one
paragraph. It should not be an in depth analysis but is helpful when
someone desires an overview of the project.</li>
<li>Deliverables - What will the project consist of when it is finished?
Source code, documentation, a build system, libraries, binaries; these should
all be enumerated in your proposal. Without a concrete set of deliverables
it is difficult to judge if a student finished their proposal. If it is
difficult to judge if the proposal was finished, it is difficult to pay for
the work as well.</li>
<li>Timeline - When will the deliverables be done? This is <b>very</b>
important for the mid-term evaluation as the mentor has to determine if a
given student has made enough progress to award them money. A student should
strive to make this as easy for the mentor as possible by providing a bar
to be measured by and then meeting that bar. A student should be careful to
make good judgements in time costs and if the student slips behind he/she
should alert their mentor to this fact and explain why the estimates were
wrong.</li>
<li>Biography - The student should talk about themselves: where they are from
what they like to study, what they do in their free time, etc. Part of this
contest is to make new friends and learn about each other and this is an
important part of that goal.</li>
</ol>
</body>
</section>
</chapter>
</guide>
1.1 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.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/mentoring.xml?rev=1.1&content-type=text/plain
Index: mentoring.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide>
<title>Summer of code mentoring guide</title>
<author>antarus</author>
<abstract>This guide is intended to be read by anyone who is interested
in mentoring students for Gentoo in the Google Summer of Code event.
Interested mentors need not be Gentoo Developers; anyone interested in
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>
<chapter>
<title>What it is to be a Mentor</title>
<section>
<title>Attributes</title>
<body>
<ul>
<li>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 for
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 this
opportunity should not be squandered. Of course mentoring also offers a
great opportunity for friendship.</li>
<li>Informed - A mentor should know what they are signing up for; generally
by reading this document. A mentor should be aware of the time requirements
and any mentor who knows they cannot devote the time required should probably
take a back-seat role; perhaps as a secondary or backup mentor.</li>
<li>Capable - A mentor should be capable of mentoring for the given task.
Knowledge of the language the student is using is important as is knowledge
of the problem domain. The student will (hopefully) be asking questions
about the project and their implementation (and as a mentor you should
arguably be questioning their implementation as you review it.)</li>
<li>Sociable - A mentor should try to foster a relationship with 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 lead
and/or the Google Summer of Code staff.</li>
</ul>
</body>
</section>
<section>
<title>Process</title>
<body>
<p>Being a mentor is about getting to know the student, helping the student,
critiquing the student and insuring the student is making progress. These are
roles generally performed by a 'Tech Lead' or 'Project Manager'. A person
interested in mentoring should be prepared to do these tasks.</p>
<p>Helping the Student:
The mentor should assist the student with common questions about the domain
area, implementation and language specifics. As a mentor you should not write
the code for the student; however using unrelated examples that can communicate
your point to the student are a good tool.</p>
<p>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 can the
student should discuss meeting times, number of meetings, and meeting duration.
It is important that you as a mentor ensure the student is staying on track and
and is meeting the deadlines set forth in their application. If there are road
blocks that are hindering the student's progress you should aid the student in
overcoming them.
</p>
</body>
</section>
</chapter>
</guide>
--
gentoo-commits@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-03-02 10:17 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-03-02 10:17 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/userrel/soc: applying.xml mentoring.xml Alec Warner (antarus)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox