| 1 |
On 19/12/2012 10:03 p.m., Michał Górny wrote: |
| 2 |
> Doesn't this prove that the recruitment process fails to work? |
| 3 |
> |
| 4 |
> If I were to throw random ideas, I'd think about letting new recruits |
| 5 |
> did all commits through a proxy (mentor?). Of course, it all would be |
| 6 |
> easier if we used git. |
| 7 |
> |
| 8 |
|
| 9 |
I know this side question of "git" migration is one we want to avoid |
| 10 |
discussing, I know its in progress. |
| 11 |
|
| 12 |
But I am literally waiting for it to happen, because for whatever |
| 13 |
reason, the present barriers to contribution are too high for me without it. |
| 14 |
|
| 15 |
I can't put an exact finger on it, but devs seem to think the quiz |
| 16 |
methodology is "easy", but it ( oh, and CVS ) are a high barrier to |
| 17 |
entry for me. |
| 18 |
|
| 19 |
I don't have the time/motivation/focus required to commit to even |
| 20 |
completing the quizzes, and I don't have the time/motivation/focus |
| 21 |
really required to be a "full dev", and I don't even want to be a "Full |
| 22 |
dev" really. |
| 23 |
|
| 24 |
But I basically have found every time I've done the quiz, its eventually |
| 25 |
boiled down to a cycle of |
| 26 |
|
| 27 |
1. Read quiz |
| 28 |
2. Find it hard to find documentation on |
| 29 |
3. Search for |
| 30 |
4. Get lost |
| 31 |
5. Find the resulting information I eventually find is vague and |
| 32 |
confusing with regard to the question. |
| 33 |
6. Eventually get distracted and do something other than the rest of the |
| 34 |
quiz. |
| 35 |
|
| 36 |
I know, it should be easy, and I'm probably making excuses, but it boils |
| 37 |
down to |
| 38 |
|
| 39 |
1. People in Gentoo have asked me to/encouraged me to do the quizzes |
| 40 |
2. I've tried several times |
| 41 |
3. Still not there. |
| 42 |
4. This problem is not so prevalent in the dozens of other projects I've |
| 43 |
contributed to. |
| 44 |
|
| 45 |
As soon as Git migration is done, then I can just |
| 46 |
|
| 47 |
1. Fork |
| 48 |
2. Hack |
| 49 |
3. Somebody can watch/review/cherry-pick commits I make if they like |
| 50 |
them, if not, I'm not worried. |
| 51 |
|
| 52 |
But the git part aside, back to the quiz. |
| 53 |
|
| 54 |
Surely, I'm not the /only/ person to get roadblocked by the quiz. |
| 55 |
|
| 56 |
The only thing really keeping me around as a half-assed dev is the fact |
| 57 |
we have overlays and the fact that the overlays are git based, and I get |
| 58 |
/some/ notion of contributions being of value there. |
| 59 |
|
| 60 |
Can we short cut the whole quiz process and have some "Inbound" |
| 61 |
repository until we're full git, which people can fork/commit/pull and |
| 62 |
trusted people can review submitted branches and apply them to CVS? |
| 63 |
|
| 64 |
Because I feel its quite possible partly that CVS is due to blame ( due |
| 65 |
to requiring of trusted commit, which requires the questions ) that |
| 66 |
there is difficulty getting devs, and the longer we're stuck with it, |
| 67 |
the more it will be a problem. |
| 68 |
|
| 69 |
It could actually be just the Proxy Maintainer workflow is not clear |
| 70 |
enough, or simple enough, and that we need more push towards a more |
| 71 |
heavy proxy-maintainer based system ( I don't know, I'm ignorant to too |
| 72 |
much of proxy-maintainer-ship stuff, to discern /why/ that is might be |
| 73 |
difficult, but I'd imagine my ignorance is part of the problem ) |
Archives