| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Luca Barbato wrote: |
| 5 |
| Simon Stelling wrote: |
| 6 |
| |
| 7 |
|> Ciaran McCreesh wrote: |
| 8 |
|> |
| 9 |
|>> On Mon, 12 Sep 2005 22:51:38 -0500 Brian Harring <ferringb@g.o> |
| 10 |
|>> wrote: |
| 11 |
|>> | define exactly how one proves themself, and in what context. |
| 12 |
|>> |
| 13 |
|>> Repeated good contributions. |
| 14 |
|> |
| 15 |
|> |
| 16 |
|> |
| 17 |
|> Just to clarify: We're not going around giving everybody AT-status who |
| 18 |
|> just asked for it. Normally, we note certain users filing many bugs |
| 19 |
|> (=useful contributions) and then we're going toward them to ask them |
| 20 |
|> whether they want to become ATs. Also, they have to pass the current |
| 21 |
|> dev quizzes before they become ATs, so the required knowledge *is* there. |
| 22 |
|> |
| 23 |
|> So, basically, ATs already HAVE proven themselves to be useful. |
| 24 |
|> |
| 25 |
| |
| 26 |
| Basically you are saying that they have the skill to be developers, they |
| 27 |
| prove them, but they don't have enough time to become full developers? |
| 28 |
| |
| 29 |
| lu |
| 30 |
No, you're confusing the different definitions of developers. In the |
| 31 |
gentoo sense of everyone is a developer(ebuild, infra, devrel, even |
| 32 |
forums), then yes, you would have to consider the AT as a "developer." |
| 33 |
If you take a more classical view, or at least acknowledge the fact that |
| 34 |
everyone has the term "developer" in their title and discount this fact, |
| 35 |
then no, they are no more "developers" than infra or docs or devrel. |
| 36 |
|
| 37 |
When I started this project, I had in mind that all ATs would eventually |
| 38 |
become devs, but it's never been a requirement. Being an AT has many |
| 39 |
advantages over being a dev in some peoples eyes. |
| 40 |
|
| 41 |
Pros: |
| 42 |
As it's not official, you don't need to go through devrel(which at the |
| 43 |
time of inception was very slow) |
| 44 |
|
| 45 |
You are sheltered from a lot of the political bullshit that "developers" |
| 46 |
have to deal with. |
| 47 |
|
| 48 |
The commitment isn't nearly as large in terms of time. We mostly |
| 49 |
recruit ATs from those active on IRC. They already spend the time |
| 50 |
testing and filing bugs, helping user, and so on. It doesn't require a |
| 51 |
great change in time to move from helpful user to AT. |
| 52 |
|
| 53 |
It's a great training and recruiting tool. A number of ATs have stated |
| 54 |
that they don't feel they have the skills to be a developer. This is a |
| 55 |
statement that I would dispute in a number of cases. However, after |
| 56 |
being an active AT, you can't help but to learn how things work. ATs |
| 57 |
are encouraged to submit patches and solve problems. The transition |
| 58 |
from AT to dev is much less painful then if it was skipped. ATs come |
| 59 |
out of the program as knowledgeable people with a focus on testing. |
| 60 |
Gentoo /needs/ more of these people. |
| 61 |
|
| 62 |
And, most importantly, they get the feeling of satisfaction that comes |
| 63 |
with learning and the knowledge that they have contributed. |
| 64 |
|
| 65 |
Cons: |
| 66 |
Due to the fact that it hasn't been official, providing them with the |
| 67 |
tools to get their job done has been a challenge. I don't think it's |
| 68 |
right to ask for read-only CVS without them being official for example. |
| 69 |
|
| 70 |
While most developers have accepted them and use them, there are still |
| 71 |
those that look down on them. What can I say, other than a distro like |
| 72 |
gentoo inherently breeds a certain level of 31337ism, however misplaced |
| 73 |
or inappropriate it is. |
| 74 |
|
| 75 |
So, the choice for an AT to not pursue becoming a ebuild/arch dev is |
| 76 |
theirs to make, with a wide variety of reasons. It's not that they lack |
| 77 |
in any one skill that would otherwise make them a developer. |
| 78 |
|
| 79 |
Off topic, AMD64 requires that all new potential devs work as an AT for |
| 80 |
the reasons stated above. When they do make dev, they "hit the ground |
| 81 |
running," and we don't need to invest anywhere near as much time as we |
| 82 |
would without the program, nor are there any misconceptions about how we |
| 83 |
operate. |
| 84 |
|
| 85 |
- -- |
| 86 |
======================================================= |
| 87 |
Mike Doty kingtaco@g.o |
| 88 |
Gentoo/AMD64 Strategic Lead PGP Key: 0xA797C7A7 |
| 89 |
Gentoo Developer Relations |
| 90 |
~ ===GPG Fingerprint=== |
| 91 |
~ 0094 7F06 913E 78D6 F1BB 06BA D0AD D125 A797 C7A7 |
| 92 |
======================================================= |
| 93 |
-----BEGIN PGP SIGNATURE----- |
| 94 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 95 |
|
| 96 |
iD8DBQFDJs9Z0K3RJaeXx6cRAj/XAKDJXKTeb4DsELKqC+EoOeLny1uRtQCfYx11 |
| 97 |
9a1/mby281fO6/0E6iTQAu0= |
| 98 |
=/S6n |
| 99 |
-----END PGP SIGNATURE----- |
| 100 |
-- |
| 101 |
gentoo-dev@g.o mailing list |
Archives