1 |
On Sat, 2007-08-04 at 01:23 +0300, Petteri Räty wrote: |
2 |
> Chris Gianelloni kirjoitti: |
3 |
> > More and more, I am finding developers who are afraid to touch packages |
4 |
> > for even minor things if they're not the maintainer. This is a sad |
5 |
> > state of affairs and not the reason we have maintainers. We have |
6 |
> > maintainers to assure that a package is being taken care of, not to |
7 |
> > establish some kind of "territory" over that package. Because of this |
8 |
> > misconception, I would like to come up with and document a listing of |
9 |
> > things that any ebuild developer can feel free to do to any package |
10 |
> > *without* maintainer consent. These are generally all minor things, but |
11 |
> > things that I think are important. I'm going to list off the things |
12 |
> > that I can think of, and encourage everyone else to speak up if I've |
13 |
> > missed something. |
14 |
> > |
15 |
> |
16 |
> I don't find anything wrong with doing the changes after you find that |
17 |
> the maintainer is not responsive. If the maintainer is responsive, he |
18 |
> will a) do the changes b) give you the permission to do it c) give |
19 |
> reasoning on why the proposed changes should not be done. |
20 |
|
21 |
Why should someone have to go through all of that just to make these |
22 |
minor fixes? Is it really necessary for someone to be required to try |
23 |
to track down and contact the maintainer to tell them that they put |
24 |
"ebiuld" instead of "ebuild" into an ebuild? This is my entire point. |
25 |
Why are we forcing a process that only fosters inefficiency? It is much |
26 |
simpler to say "if you see one of these, fix it" than to force every |
27 |
single action to go through the maintainer. |
28 |
|
29 |
-- |
30 |
Chris Gianelloni |
31 |
Release Engineering Strategic Lead |
32 |
Alpha/AMD64/x86 Architecture Teams |
33 |
Games Developer/Council Member/Foundation Trustee |
34 |
Gentoo Foundation |