| 1 |
Ian Stakenvicius schrieb: |
| 2 |
> On 23/11/12 09:32 AM, Thomas Sachau wrote: |
| 3 |
>> Ian Stakenvicius schrieb: |
| 4 |
>>> On 22/11/12 11:22 PM, Robin H. Johnson wrote: |
| 5 |
>>>> On Thu, Nov 22, 2012 at 08:22:10PM -0600, Donnie Berkholz |
| 6 |
>>>> wrote: |
| 7 |
>>>>> On 11:11 Sun 18 Nov , Robin H. Johnson wrote: |
| 8 |
>>>>>> Here's a list of every package where I'm a maintainer and |
| 9 |
>>>>>> there is no herd listed (but their might be other |
| 10 |
>>>>>> maintainers): |
| 11 |
>>>> I didn't say I was dropping any of the packages, merely making |
| 12 |
>>>> an explicit list of packages I maintain, that other developers |
| 13 |
>>>> are welcome to touch - if they want to take them over |
| 14 |
>>>> explicitly, that would be great too. |
| 15 |
>>> |
| 16 |
>>> |
| 17 |
>>> .. For certain things, I think it would be very beneficial for |
| 18 |
>>> this to be true (other dev's welcome to touch) across the tree. |
| 19 |
>>> Maybe if there is enough general support for it, we should change |
| 20 |
>>> our default of "never touch a maintainer's package without |
| 21 |
>>> permission of the maintainer/herd", to "OK to touch unless |
| 22 |
>>> package metadata explicitly requests not to" ...? And we can put |
| 23 |
>>> a tag in the metadata to indicate this (or even to indicate what |
| 24 |
>>> other dev's can and can't touch -- ie, can touch *DEPEND, can |
| 25 |
>>> bump EAPI, cannot add features, cannot bump)? |
| 26 |
>>> |
| 27 |
>>> Thoughts? |
| 28 |
>>> |
| 29 |
>>> |
| 30 |
>>> |
| 31 |
> |
| 32 |
>> What certain things do you have in mind? In wich situation do you |
| 33 |
>> see a simple "May i touch the package?/ok for this patch?" as too |
| 34 |
>> much to do before touching a package? |
| 35 |
> |
| 36 |
> |
| 37 |
> This works, and when, say, myself and the other dev are on irc it's |
| 38 |
> very quick, but then if I don't write it down or communicate it to my |
| 39 |
> other couterparts in the herd this permission gets lost in the |
| 40 |
> shuffle. I'm just suggesting that if we put it in the metadata then |
| 41 |
> it'll be easier to track. |
| 42 |
|
| 43 |
You can already add a comment in the ebuild or metadata.xml to |
| 44 |
explicitly allow everyone to touch it, so there is nothing needed to |
| 45 |
allow you or anyone else interested in it doing this now. |
| 46 |
|
| 47 |
Just reverting this default probably wont happen, since it just means |
| 48 |
additional work and issues without any real benefit (like mass commits |
| 49 |
to add the notes, missed additions and others touched the package and |
| 50 |
other problems). |
| 51 |
|
| 52 |
-- |
| 53 |
|
| 54 |
Thomas Sachau |
| 55 |
Gentoo Linux Developer |
Archives