Gentoo Archives: gentoo-dev

From: Daniel Robbins <drobbins.daniel@×××××.com>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Summer of Code - worth repeating?
Date: Mon, 19 Feb 2007 22:03:01
Message-Id: 226689f10702191359h35ae33adsea9e44fb32424a7b@mail.gmail.com
In Reply to: [gentoo-dev] Summer of Code - worth repeating? by Christel Dahlskjaer
1 I agree that we should do it. Looking a the list for 2006, I think we
2 should steer clear of projects that might require significant
3 knowledge of Gentoo Linux internals or that may have a lot of
4 difficult interdependencies and/or coordination. For example, moving
5 to a different revision control system does not, at least on the
6 surface, seem like a project that a single SoC student could pull off,
7 considering the significant amount of coordination required.
8
9 I think I good way to start 2007 would be to put together an informal
10 guide for how to choose appropriate SoC projects. These guidelines
11 should be geared towards helping to ensure a greater likelihood of
12 rapid progress and successful completion. My list:
13
14 1) Should be a specific, focused problem or challenge
15
16 2) Should not have a large number of technical inter-dependencies
17
18 3) Should not require significant cross-team coordination/project
19 management work
20
21 4) Anything that touches core gentoo functionality should be done as a
22 proof of concept, not as an official replacement (changing official
23 core stuff has distro-wide implications which is not suitable for SoC
24 efforts and makes the design stage overly complex - "officialness" can
25 be considered afterwards if the SoC effort is successful)
26
27 5) An emphasis on training and mentoring future Gentoo developers to
28 bring lasting benefits to the project. This means: interesting, fun
29 projects, good experiences are more important than solving incredibly
30 thorny problems.
31
32 6) The challenges need not be hard - this is not our money so we need
33 not set artificially high expectations. We should not expect a student
34 with relatively little Gentoo experience to solve challenges that we
35 have struggled to find solutions for.
36
37 7) Projects should be achievable by a single person working part-time
38 over 3 months (this *is* summer, after all) and have clearly defined
39 goals for completion.
40
41 -Daniel
42
43 On 2/20/07, Christel Dahlskjaer <christel@g.o> wrote:
44 > Hiya all,
45 >
46 > Let's do a quick re-cap of Summer of Code '06:
47 >
48 > Gentoo had 14 project slots, out of these fourteen two were on Gentoo
49 > external Gentoo project which I will leave out of the re-cap.
50 >
51 > That leaves us with twelve projects, four of which were being worked on
52 > by at the time current Gentoo developers. Leaving us eight "newcomers,"
53 > out of these eight four has been recruited and I belicve an additional
54 > one is in the recruitment queue.
55 >
56 > Some of the projects have been picked up and are being worked on daily,
57 > some we've had problems getting acceptance for from the projects where
58 > they would be most suited (Beacon - GDP), and some may have fizzled off
59 > and died when SoC ended (be that because the student were no longer
60 > involved and didn't feel that they were welcomed into the community
61 > post-soc, or be that because it just didn't end up being a small idea
62 > turned explosion).
63 >
64 > Summer of Code 2006 was thrown together practically overnight, we jumped
65 > onboard after the deadline, by pure luck, and due to lack of planning
66 > ended up with whatever projects people could think up in no time and
67 > what mentors felt comfortable mentoring at said time.
68 >
69 > Based on the timeframe and having to jump into the deep end I'd say SoC
70 > was a tremendous success for us, not least as a recruitment tool. And of
71 > course, it feels great to put something back into the community.
72 >
73 > Summer of Code '07 is about to kick off, those of us who participated in
74 > one form or another last year are pretty geared up to do it again. This
75 > time around we've got a chance to plan better, apply in time..
76 >
77 > Should we SoC? Of course we should! Can we think up projects? Do we have
78 > willing mentors? Will Google have us once more? (with feeling)
79 >
80 > Summer of Code itself should be a lot more organised this year, OSPO has
81 > put a fair chunk of work into getting things up to speed and has
82 > listened to the feedback of both students and mentoring organisations
83 > from last year.
84 >
85 > -- Christel
86 >
87 >
88 >
89 > --
90 > gentoo-dev@g.o mailing list
91 >
92 >
93 --
94 gentoo-dev@g.o mailing list