| 1 |
I'm not claiming that this is a new problem or that it will be orders of magnitude worse. Merely that it brings the issue back into the forefront and that we could benefit from official policies and (in some cases renewed) efforts to reduce their impact. An official policy/action is not likely to make an impact than an ad hoc, unofficial one, IMO. |
| 2 |
|
| 3 |
On January 19, 2016 5:51:27 PM EST, "Michał Górny" <mgorny@g.o> wrote: |
| 4 |
>On Tue, 19 Jan 2016 00:44:49 -0500 |
| 5 |
>NP-Hardass <NP-Hardass@g.o> wrote: |
| 6 |
> |
| 7 |
>> With all of the unclaimed herds and unclaimed packages within them, I |
| 8 |
>> started to wonder what will happen after the GLEP 67 transition |
| 9 |
>> finally comes to fruition. This left me with some concerns and I was |
| 10 |
>> wondering what the community thinks about them, and some possible |
| 11 |
>> solutions. |
| 12 |
>> |
| 13 |
>> There is a large number of packages from unclaimed herds that, at |
| 14 |
>this |
| 15 |
>> time, look like they will not be claimed by developers. This will |
| 16 |
>> likely result in a huge increase in maintainer-needed packages (and |
| 17 |
>> subsequent package rot). This isn't to say that some of these |
| 18 |
>> packages weren't previously in a "maintainer-needed" like state, but |
| 19 |
>> now, they will explicitly be there. |
| 20 |
> |
| 21 |
>Oh, and just to be clear, this isn't going to be some kind of huge |
| 22 |
>growth. Right now I can count 380 new maintainer-needed packages, from |
| 23 |
>which some will most likely be mapped. I would estimate the final |
| 24 |
>outcome to around 300 packages, maybe less. |
| 25 |
> |
| 26 |
>Now compare that to the current 1212 maintainer-needed packages. |
| 27 |
> |
| 28 |
>-- |
| 29 |
>Best regards, |
| 30 |
>Michał Górny |
| 31 |
><http://dev.gentoo.org/~mgorny/> |
| 32 |
|
| 33 |
-- |
| 34 |
NP-Hardass |
Archives