Gentoo Archives: gentoo-commits

From: "Donnie Berkholz (dberkholz)" <dberkholz@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/userrel/soc: applying.xml
Date: Fri, 24 May 2013 14:26:21
Message-Id: 20130524142618.CDC452171D@flycatcher.gentoo.org
1 dberkholz 13/05/24 14:26:18
2
3 Modified: applying.xml
4 Log:
5 More detail on timelines.
6
7 Revision Changes Path
8 1.17 xml/htdocs/proj/en/userrel/soc/applying.xml
9
10 file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/userrel/soc/applying.xml?rev=1.17&view=markup
11 plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/userrel/soc/applying.xml?rev=1.17&content-type=text/plain
12 diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/userrel/soc/applying.xml?r1=1.16&r2=1.17
13
14 Index: applying.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/userrel/soc/applying.xml,v
17 retrieving revision 1.16
18 retrieving revision 1.17
19 diff -u -r1.16 -r1.17
20 --- applying.xml 8 Apr 2013 20:36:20 -0000 1.16
21 +++ applying.xml 24 May 2013 14:26:18 -0000 1.17
22 @@ -73,7 +73,8 @@
23 to be measured by and then meeting that bar. A student should be careful to
24 make good judgements in time costs and if the student slips behind he/she
25 should alert their mentor to this fact and explain why the estimates were
26 - wrong.</li>
27 + wrong. Your timeline should be at a level of detail of one work item
28 + every 1-2 weeks</li>
29 <li><b>Biography</b> - The student should talk about themselves: where they are from
30 what they like to study, what they do in their free time, etc. Part of this
31 contest is to make new friends and learn about each other and this is an
32 @@ -82,6 +83,21 @@
33 section is also intended to promote oneself and convince Gentoo that we should
34 chose a given student over other applicants.</li>
35 </ol>
36 +<p>
37 +For Gentoo, the coding period should not explicitly include time to
38 +learn, research, investigate, etc. Your initial research should be done
39 +before writing the proposal, to convince us that you know enough about
40 +your project to understand it and complete it successfully. If further
41 +dedicated time for research/learning is required, it should happen
42 +during the community-bonding period, which comes before the coding
43 +period.
44 +</p>
45 +<p>
46 +We understand that sometimes implementations cannot match the proposal,
47 +and further experimentation and research may be necessary while
48 +implementing any given week's work, but this falls under the time for
49 +the implementation itself rather than devoting a week to research.
50 +</p>
51 <p>We highly recommend having some initial discussion with one of the mentors about
52 your proposal before you submit it.</p>
53 </body>