| 1 |
antarus 08/03/02 10:17:54 |
| 2 |
|
| 3 |
Added: applying.xml mentoring.xml |
| 4 |
Log: |
| 5 |
Get some drafts up in anticipation for application |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.1 xml/htdocs/proj/en/userrel/soc/applying.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/applying.xml?rev=1.1&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/applying.xml?rev=1.1&content-type=text/plain |
| 12 |
|
| 13 |
Index: applying.xml |
| 14 |
=================================================================== |
| 15 |
<?xml version="1.0" encoding="UTF-8"?> |
| 16 |
<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?> |
| 17 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 18 |
|
| 19 |
<guide> |
| 20 |
<title>Summer of code application guide</title> |
| 21 |
<author>antarus</author> |
| 22 |
<abstract>This guide is intended to be read by anyone who is interested |
| 23 |
in applying to Gentoo in the Google Summer of Code event. Interested students |
| 24 |
need not be Gentoo Developer, anyone who meets the Eligibility requirements of |
| 25 |
Google is encouraged to apply. |
| 26 |
</abstract> |
| 27 |
<version>1.0</version> |
| 28 |
<date>March 1, 2008</date> |
| 29 |
<chapter> |
| 30 |
<title>Applying as a student</title> |
| 31 |
<section> |
| 32 |
<title>Communication</title> |
| 33 |
<body> |
| 34 |
<p>Students interested in applying to do a project for Gentoo should join |
| 35 |
#gentoo-soc on irc.freenode.net and/or join the gentoo-soc mailing list. |
| 36 |
Announcements related to Gentoo's summer of code effort will be relayed to both |
| 37 |
places</p> |
| 38 |
</body> |
| 39 |
</section> |
| 40 |
</chapter> |
| 41 |
<chapter> |
| 42 |
<title>What interested students need to do</title> |
| 43 |
<section> |
| 44 |
<title>Get feedback on your idea</title> |
| 45 |
<body> |
| 46 |
<p>Students interested in applying to do a project for Gentoo should review |
| 47 |
the projects <uri link="index.xml">listed</uri>. You are free to apply for a |
| 48 |
project that is not on our list. In either case once you have an idea of what |
| 49 |
you want to work on you should find someone to discuss it with it. The |
| 50 |
gentoo-soc mailing list, #gentoo-soc on irc.freenode.net or any of the |
| 51 |
listed <uri link="index.xml">mentors</uri> should be able to provide feedback. |
| 52 |
</p> |
| 53 |
</body> |
| 54 |
</section> |
| 55 |
<section> |
| 56 |
<title>Write a proposal</title> |
| 57 |
<body> |
| 58 |
<p>Students should author a proposal that attempts to convince Gentoo why |
| 59 |
their project should be chosen over other competing proposals. A few sentences |
| 60 |
is not sufficient in most cases to sway anyone. |
| 61 |
</p> |
| 62 |
<ol> |
| 63 |
<li>Objective - What problem does the project solve. This does not need to |
| 64 |
be a long section. Generally software tries to help make people more |
| 65 |
efficient, or foster communication, or entertain folks. Any proposed |
| 66 |
software should have a purpose and applicants should define that purpose |
| 67 |
here.</li> |
| 68 |
<li>Abstract - What does the project do; try to keep this section to one |
| 69 |
paragraph. It should not be an in depth analysis but is helpful when |
| 70 |
someone desires an overview of the project.</li> |
| 71 |
<li>Deliverables - What will the project consist of when it is finished? |
| 72 |
Source code, documentation, a build system, libraries, binaries; these should |
| 73 |
all be enumerated in your proposal. Without a concrete set of deliverables |
| 74 |
it is difficult to judge if a student finished their proposal. If it is |
| 75 |
difficult to judge if the proposal was finished, it is difficult to pay for |
| 76 |
the work as well.</li> |
| 77 |
<li>Timeline - When will the deliverables be done? This is <b>very</b> |
| 78 |
important for the mid-term evaluation as the mentor has to determine if a |
| 79 |
given student has made enough progress to award them money. A student should |
| 80 |
strive to make this as easy for the mentor as possible by providing a bar |
| 81 |
to be measured by and then meeting that bar. A student should be careful to |
| 82 |
make good judgements in time costs and if the student slips behind he/she |
| 83 |
should alert their mentor to this fact and explain why the estimates were |
| 84 |
wrong.</li> |
| 85 |
<li>Biography - The student should talk about themselves: where they are from |
| 86 |
what they like to study, what they do in their free time, etc. Part of this |
| 87 |
contest is to make new friends and learn about each other and this is an |
| 88 |
important part of that goal.</li> |
| 89 |
</ol> |
| 90 |
</body> |
| 91 |
</section> |
| 92 |
</chapter> |
| 93 |
</guide> |
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
1.1 xml/htdocs/proj/en/userrel/soc/mentoring.xml |
| 98 |
|
| 99 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/mentoring.xml?rev=1.1&view=markup |
| 100 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/mentoring.xml?rev=1.1&content-type=text/plain |
| 101 |
|
| 102 |
Index: mentoring.xml |
| 103 |
=================================================================== |
| 104 |
<?xml version="1.0" encoding="UTF-8"?> |
| 105 |
<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?> |
| 106 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 107 |
|
| 108 |
<guide> |
| 109 |
<title>Summer of code mentoring guide</title> |
| 110 |
<author>antarus</author> |
| 111 |
<abstract>This guide is intended to be read by anyone who is interested |
| 112 |
in mentoring students for Gentoo in the Google Summer of Code event. |
| 113 |
Interested mentors need not be Gentoo Developers; anyone interested in |
| 114 |
mentoring should be able to make a case as to why they want to mentor should |
| 115 |
the SOC team have quetions. |
| 116 |
</abstract> |
| 117 |
<version>1.0</version> |
| 118 |
<date>Feb 29, 2008</date> |
| 119 |
<chapter> |
| 120 |
<title>What it is to be a Mentor</title> |
| 121 |
<section> |
| 122 |
<title>Attributes</title> |
| 123 |
<body> |
| 124 |
<ul> |
| 125 |
<li>Willing - A mentor should be willing to mentor. Mentoring is not a |
| 126 |
forced activity and it is not required. A mentor should not mentor |
| 127 |
half-heartedly. The Summer of Code experience is a great experience for |
| 128 |
students and part of that experience is having some help along the way. It |
| 129 |
is also a great opportunity to recruit new people into a project and this |
| 130 |
opportunity should not be squandered. Of course mentoring also offers a |
| 131 |
great opportunity for friendship.</li> |
| 132 |
<li>Informed - A mentor should know what they are signing up for; generally |
| 133 |
by reading this document. A mentor should be aware of the time requirements |
| 134 |
and any mentor who knows they cannot devote the time required should probably |
| 135 |
take a back-seat role; perhaps as a secondary or backup mentor.</li> |
| 136 |
<li>Capable - A mentor should be capable of mentoring for the given task. |
| 137 |
Knowledge of the language the student is using is important as is knowledge |
| 138 |
of the problem domain. The student will (hopefully) be asking questions |
| 139 |
about the project and their implementation (and as a mentor you should |
| 140 |
arguably be questioning their implementation as you review it.)</li> |
| 141 |
<li>Sociable - A mentor should try to foster a relationship with the student. |
| 142 |
It is important to critique the students work in a professional manner. |
| 143 |
Complaints about rudeness and abuse should be filed to the GSoc team lead |
| 144 |
and/or the Google Summer of Code staff.</li> |
| 145 |
</ul> |
| 146 |
</body> |
| 147 |
</section> |
| 148 |
<section> |
| 149 |
<title>Process</title> |
| 150 |
<body> |
| 151 |
<p>Being a mentor is about getting to know the student, helping the student, |
| 152 |
critiquing the student and insuring the student is making progress. These are |
| 153 |
roles generally performed by a 'Tech Lead' or 'Project Manager'. A person |
| 154 |
interested in mentoring should be prepared to do these tasks.</p> |
| 155 |
<p>Helping the Student: |
| 156 |
The mentor should assist the student with common questions about the domain |
| 157 |
area, implementation and language specifics. As a mentor you should not write |
| 158 |
the code for the student; however using unrelated examples that can communicate |
| 159 |
your point to the student are a good tool.</p> |
| 160 |
<p>Critiquing the student: |
| 161 |
As a mentor you should review the student's work on a regular basis. A |
| 162 |
recommendation that has worked in the past is every week; however you can the |
| 163 |
student should discuss meeting times, number of meetings, and meeting duration. |
| 164 |
It is important that you as a mentor ensure the student is staying on track and |
| 165 |
and is meeting the deadlines set forth in their application. If there are road |
| 166 |
blocks that are hindering the student's progress you should aid the student in |
| 167 |
overcoming them. |
| 168 |
</p> |
| 169 |
</body> |
| 170 |
</section> |
| 171 |
</chapter> |
| 172 |
</guide> |
| 173 |
|
| 174 |
|
| 175 |
|
| 176 |
-- |
| 177 |
gentoo-commits@l.g.o mailing list |
Archives