| 1 |
2013/2/1 Rich Freeman <rich0@g.o>: |
| 2 |
> On Fri, Feb 1, 2013 at 8:53 AM, Tomáš Chvátal <tomas.chvatal@×××××.com> wrote: |
| 3 |
>> If you as developers and users find some package useful you can retake |
| 4 |
>> the maintainership (or became proxy-maint) which also expects you to |
| 5 |
>> take care of the bugs (QA can prune it even if you take the |
| 6 |
>> maintainership but ignore failures [even if your personal feeling is |
| 7 |
>> that it is corner case, it is for QA to deicde]). |
| 8 |
> |
| 9 |
> Citation? I don't see any GLEPs or other Council-approved policies to |
| 10 |
> that effect. |
| 11 |
|
| 12 |
You my friend are slowly pissing me of as I read through all the |
| 13 |
flames you cause on -dev. |
| 14 |
There is no council vote required as it is already defined within qa |
| 15 |
team specs (and glep too when i think of it, so yep there is glep for |
| 16 |
you). |
| 17 |
|
| 18 |
> |
| 19 |
> And this is of course why nobody actually wants to maintain these |
| 20 |
> packages - everybody is going to be looking over your shoulder because |
| 21 |
> they've already decided that the existence of the package bothers |
| 22 |
> them. |
| 23 |
|
| 24 |
No, they won't get anyone looking over their shoulder unless they |
| 25 |
decide to neglect the bugs as few maintainers did. |
| 26 |
I didn't see a lot forced removals caused by qa, did you? |
| 27 |
|
| 28 |
The existence of the package usually does not bother anyone, |
| 29 |
maintainer just decided that its burden so it will be removed, he |
| 30 |
could've put it to m-n but its up to every maintainer to decide what |
| 31 |
to do if the package has bugs he deem serious. If anyone else decide |
| 32 |
to pick up where they left, it is his job to ensure the package gets |
| 33 |
fixed and up-par to work nicely. |
| 34 |
|
| 35 |
Bit ago we had this discussion about keeping broken shit in tree |
| 36 |
masked or just prune it, and obvious solution was to remove it as |
| 37 |
there is just few of us and if anyone wants to start where we left he |
| 38 |
can pick out the ebuild from attic and put into his own overlay where |
| 39 |
it might work for him or even put it back to tree fixed. |
| 40 |
|
| 41 |
> |
| 42 |
> Honestly, threads like this bug me so much that I'm half-tempted to |
| 43 |
> take over maintainership of one of these packages just to be a test |
| 44 |
> case... Ugh - time for an email break... |
| 45 |
> |
| 46 |
Go for it, i wrote exactly what to do, create vcs/tracker/homepage and |
| 47 |
it can stay. |
Archives