| 1 |
On 11/23/12 22:32, Thomas Sachau wrote: |
| 2 |
> Ian Stakenvicius schrieb: |
| 3 |
>> On 22/11/12 11:22 PM, Robin H. Johnson wrote: |
| 4 |
>>> On Thu, Nov 22, 2012 at 08:22:10PM -0600, Donnie Berkholz wrote: |
| 5 |
>>>> On 11:11 Sun 18 Nov , Robin H. Johnson wrote: |
| 6 |
>>>>> Here's a list of every package where I'm a maintainer and there |
| 7 |
>>>>> is no herd listed (but their might be other maintainers): |
| 8 |
>>> I didn't say I was dropping any of the packages, merely making an |
| 9 |
>>> explicit list of packages I maintain, that other developers are |
| 10 |
>>> welcome to touch - if they want to take them over explicitly, that |
| 11 |
>>> would be great too. |
| 12 |
>> |
| 13 |
>> |
| 14 |
>> .. For certain things, I think it would be very beneficial for this |
| 15 |
>> to be true (other dev's welcome to touch) across the tree. Maybe if |
| 16 |
>> there is enough general support for it, we should change our default |
| 17 |
>> of "never touch a maintainer's package without permission of the |
| 18 |
>> maintainer/herd", to "OK to touch unless package metadata explicitly |
| 19 |
>> requests not to" ...? And we can put a tag in the metadata to |
| 20 |
>> indicate this (or even to indicate what other dev's can and can't |
| 21 |
>> touch -- ie, can touch *DEPEND, can bump EAPI, cannot add features, |
| 22 |
>> cannot bump)? |
| 23 |
>> |
| 24 |
>> Thoughts? |
| 25 |
>> |
| 26 |
>> |
| 27 |
>> |
| 28 |
> |
| 29 |
> What certain things do you have in mind? In wich situation do you see a |
| 30 |
> simple "May i touch the package?/ok for this patch?" as too much to do |
| 31 |
> before touching a package? |
| 32 |
> |
| 33 |
To me it's random noise, if I'm in the package metadata just do it. No |
| 34 |
need to distract me :) |
| 35 |
|
| 36 |
And there's tons of packages that have a "maintainer" in metadata and |
| 37 |
bugs just go into nirvana (like apache)... |
Archives