1 |
On Tue January 06 2004 4:33 am, Paul de Vrieze wrote: |
2 |
<snip> |
3 |
> > dev says "ok, that sounds fun." I mean, I got passed back and forth |
4 |
> > from hardened to general and back a few times and it was all because |
5 |
> > the devs reviewing my bug(s) didn't understand the packages. |
6 |
> |
7 |
> I'm sorry for that. It however can be a sign that the tree is not ready |
8 |
> for those ebuilds, or that they are in very low demand. |
9 |
|
10 |
If someone has gone their entire life using a rock to hammer nails and has |
11 |
never heard of a hammer before and thus doesn't have the demand for it does |
12 |
that mean that if they are told about the hammer they won't use it or have a |
13 |
demand for always having it? |
14 |
|
15 |
Sometimes you create demand where one doesn't currently exist by simply |
16 |
telling people about the hammer. |
17 |
|
18 |
> > Basically, I just find that the entire ebuild submission process could |
19 |
> > definitely be streamlined as to take less dev time and be more |
20 |
> > rewarding for the users actually doing the submissions. Including |
21 |
> > having user response saying, "hey, so and so just bumped package-x.y.y |
22 |
> > to package-x.y.z and it builds fine with a renamed and digested |
23 |
> > ebuild." |
24 |
> |
25 |
> I would agree with that. However I don't know how to do it in a good way |
26 |
> that preserves quality. |
27 |
|
28 |
There is but it will take effort and time to setup. Sometimes if not always |
29 |
time is required to save time in the long run. Kind of like it takes money to |
30 |
make money. It takes time to save it. Fine grain controls on cvs are required |
31 |
now. If you want until they are fully needed then there will be a ton of |
32 |
pressure to get it done yesterday. Lets not REact let's be proactive. |
33 |
|
34 |
If there is a way to make cvs ownership based that would be the easiest |
35 |
administration wise. As in the ebuild(s) I submit I have access to and |
36 |
nothing else. |
37 |
|
38 |
Robert |
39 |
|
40 |
-- |
41 |
gentoo-dev@g.o mailing list |