1 |
>A. REGISTERED USERS / TESTERS |
2 |
> |
3 |
>Let's say Gentoo creates new posts: registered users and/or registered |
4 |
>testers. Ok, maybe there are few out there wanting to become a developer, but |
5 |
>there are tons of users out there continously installing and testing Gentoo. |
6 |
>Why don't take advantage of that? The developer task may take a lot of time, |
7 |
>and may be not rewarded, but testing new software is something that people |
8 |
>uses to do while they're studying, working, or even playing at home. Let's |
9 |
>make them take a step further: become a registered user or tester that |
10 |
>reports directly to Gentoo their success or failure, instead of just writing |
11 |
>to some list saying they have a problem, or they've been successful while |
12 |
>installing and using an ebuild. |
13 |
> |
14 |
> |
15 |
interesting idea |
16 |
if you follow the track a little bit further -> there are many users of |
17 |
gentoo quite experienced |
18 |
in getting certain packages to run, using them for their work, etc ... |
19 |
such users could take over support and/or ebuild maintenance for these |
20 |
packages; |
21 |
this does not need an access to cvs at all |
22 |
|
23 |
getting an updated ebuild into portage is not about 'cvs commit', it is |
24 |
about writing an ebuild, |
25 |
and about testing it with cooperation of other users |
26 |
|
27 |
i think that this could be automated very nicely; so that when it |
28 |
finally comes to gentoo developer (someone with |
29 |
commit rights) he already sees patch/new ebuild, and list of people who |
30 |
positively confirmed that it is working |
31 |
well on their systems |
32 |
|
33 |
if he trusts the people doing all this work before him, it can be |
34 |
commited quite quickly i'd guess |