1 |
On 12/16/2012 01:27 PM, Duncan wrote: |
2 |
> Michael Orlitzky posted on Sun, 16 Dec 2012 12:20:10 -0500 as excerpted: |
3 |
> |
4 |
>> On 12/16/2012 12:02 PM, Fabian Groffen wrote: |
5 |
>>> On 16-12-2012 11:57:35 -0500, Michael Orlitzky wrote: |
6 |
>>>> 3. Get off CVS for Christ's sake. Nobody wants to work with that. |
7 |
>>>> I don't know how this fits into my bullet list, but it's important. |
8 |
>>> |
9 |
>>> It doesn't, and it's not. |
10 |
>>> |
11 |
>> I'm not going to put together a powerpoint presentation for you, but |
12 |
>> think about it this way. |
13 |
>> |
14 |
>> Many new developers who want to contribute to to some project will learn |
15 |
>> git, because a large number of important projects use git. No (new) |
16 |
>> developers are going to learn CVS. Ever. |
17 |
>> |
18 |
>> Therefore, we can rule out "using CVS is helping us attract new |
19 |
>> developers." |
20 |
> |
21 |
> I agree getting off of CVS is important in that it's likely triggering a |
22 |
> writeoff of gentoo from the list of potential volunteers before they even |
23 |
> get to where we see them, but AFAIK, the switch to git /is/ making (slow) |
24 |
> progress. One of the big blockers was apparently taken care of via |
25 |
> bounty (relatively) recently, and I don't think they'd have spent the |
26 |
> money on that if they believed it to be pouring that money down a rathole. |
27 |
> |
28 |
> Before finding out about that, I too had despaired of the git transition |
29 |
> being anything but "bluesky", but that's concrete indication that |
30 |
> /somebody/ is still working on it, and that it's considered important |
31 |
> enough for the gentoo foundation to spend money on. |
32 |
> |
33 |
|
34 |
Thanks. I know progress has been made and I didn't mean to belittle that |
35 |
effort. But I know I'm not alone in thinking CVS deters new people. |
36 |
|
37 |
|
38 |
> |
39 |
> Meanwhile, I'm not sure how practical your bounty for recruiting spruceup |
40 |
> is, since much of that work's likely to require intimate knowledge of |
41 |
> gentoo and recruiting to approve, if not to actually do, and that level |
42 |
> of knowledge is apparently in short supply, or recruiting wouldn't be the |
43 |
> bottleneck it seems to be. |
44 |
> |
45 |
|
46 |
True. I've observed that the sunrise and proxy-maint projects already do |
47 |
a lot of this work. The quality of ebuilds that get past review in |
48 |
either situation is on average higher than that of those which don't. |
49 |
|
50 |
I hate to criticize without offering a suggestion, so here's a wild one: |
51 |
pay someone from the recruiters, sunrise, and/or proxy-maint teams to |
52 |
recruit and train new developers. Pay them a reasonable wage, say, |
53 |
$15-20/hr. out of the foundation to actively recruit new people. |
54 |
|
55 |
We fix the recruitment docs, and make the homepage attractive. Then we |
56 |
put out press releases on Slashdot, Reddit, etc. and announce to |
57 |
gentoo-users@g.o that we're looking to train new developers. Send them |
58 |
to the new docs, which will in turn tell them to, |
59 |
|
60 |
* Be familiar with gentoo system administration |
61 |
|
62 |
* Know the devmanual forwards and backwards |
63 |
|
64 |
* Practice committing ebuilds to an overlay |
65 |
|
66 |
* Submit ebuilds for review in #gentoo-sunrise and #gentoo-dev-help |
67 |
|
68 |
* Learn CVS (ugh) |
69 |
|
70 |
... |
71 |
|
72 |
* Contact the guy we're paying to mentor people, who will then train, |
73 |
test, and recruit him. |
74 |
|
75 |
You'll get tons of new developers. In the long-term, that's a highly |
76 |
effective use of the money. |
77 |
|
78 |
Most of the day-to-day work that needs done is not life-threatening. If |
79 |
we can get people wrangling bugs, bumping packages, and communicating |
80 |
with upstream, it will make a big difference. |
81 |
|
82 |
|
83 |
> I don't know how important a general gentoo web page redesign might be (I |
84 |
> think what's there is perfectly functional and great), but you're |
85 |
> certainly correct on the content itself; anything still mentioning |
86 |
> looking for openings in the weekly newsletter is... anachronistic I think |
87 |
> is the term. Have you checked for and filed if necessary, a bug on that? |
88 |
> |
89 |
|
90 |
I have some specific suggestions for the homepage, but in general I |
91 |
think it just needs to look like it wasn't made in 2001. We need to look |
92 |
attractive to attract things. I hope that's not controversial too! |
93 |
|
94 |
And yeah, yeah, I'll go file bugs =) |