| 1 |
On 12/16/12 14:04, Markos Chandras wrote: |
| 2 |
> On 16 December 2012 16:57, Michael Orlitzky <michael@××××××××.com> wrote: |
| 3 |
>> Inspired by the number of packages being unmaintained -- why not use |
| 4 |
>> some of that bug bounty money to fix up the recruitment documentation |
| 5 |
> |
| 6 |
> Recruitment documentatiob? What does that mean? |
| 7 |
> |
| 8 |
>> People still think of Gentoo as a ricer distro that's broken all |
| 9 |
>> the time, when in reality, it's one of the most stable. |
| 10 |
> |
| 11 |
> Well that's not entirely true but that's a different issue |
| 12 |
> |
| 13 |
|
| 14 |
The first part is definitely true. The stable part is also true in my |
| 15 |
experience, all things considered. For an example, take the last "what's |
| 16 |
your favorite distro" post on Reddit (not exactly a representative |
| 17 |
sample, I know): |
| 18 |
|
| 19 |
http://www.reddit.com/r/linux/comments/14tpnt/of_all_the_distros_youve_ever_used_what_do_you/ |
| 20 |
|
| 21 |
Top rated comment: |
| 22 |
|
| 23 |
"Tie between Arch and Gentoo. These are my "messing around" distros. |
| 24 |
Fun to install and tweak on older machines, but I don't know enough |
| 25 |
about them to use them full time. Plus, Gentoo breaks. A lot. Arch |
| 26 |
breaks much more often than Debian for me but much less than Gentoo." |
| 27 |
|
| 28 |
Further down: |
| 29 |
|
| 30 |
"Gentoo is not stable. Stop saying that." |
| 31 |
|
| 32 |
My experience mirrors Michael Mol's. Perception is bad. Reality not so much. |
| 33 |
|
| 34 |
|
| 35 |
> Note quite. The activity of a distro is measure but the # of devs, |
| 36 |
> packages in tree, activity on bugzilla and mailing lists etc. The |
| 37 |
> design of a website does not |
| 38 |
> really say much. Many foss projects still have static html pages. This |
| 39 |
> does not mean they are dead. |
| 40 |
|
| 41 |
The actual activity, yes. The perceived activity... eh. And that's what |
| 42 |
gets you new users and developers. |
| 43 |
|
| 44 |
|
| 45 |
> Parts of this docs are outdated but this does not matter. Get |
| 46 |
> involved, fix bugs, help people and someone will ask you to join. Or |
| 47 |
> look for a mentor. |
| 48 |
|
| 49 |
If your recruitment process is "fix bugs for years and maybe someone |
| 50 |
will notice you, maybe not," then nobody is going to bother. There needs |
| 51 |
to be a clear, step-by-step process. This guy posted a graph the other day: |
| 52 |
|
| 53 |
http://hwoarang.silverarrow.org/wp-content/uploads/recruitment_stats.png |
| 54 |
|
| 55 |
People aren't bothering. It's not because of any fundamental problem -- |
| 56 |
it's because the process is obscure and potentially a waste of time. |
| 57 |
|
| 58 |
|
| 59 |
> |
| 60 |
>> |
| 61 |
>> 3. Get off CVS for Christ's sake. Nobody wants to work with that. I |
| 62 |
>> don't know how this fits into my bullet list, but it's important. |
| 63 |
>> |
| 64 |
> I believe this is Irrelevant |
| 65 |
> |
| 66 |
|
| 67 |
It's the least important of the three probably. The (lack of) |
| 68 |
recruitment process is the biggest problem. |
| 69 |
|
| 70 |
|
| 71 |
> |
| 72 |
> I don't like the attitude "pay in order to happen". This is a foss |
| 73 |
> project, so people are supposed to |
| 74 |
> see this as a hobby or a learning experience. It is not a job ;) |
| 75 |
> Things are supposed to happen because they are fun |
| 76 |
> |
| 77 |
|
| 78 |
You would be perfect for training new developers. Feel free to decline |
| 79 |
your salary =) |
Archives
