| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 11/25/2012 02:01 AM, Patrick Lauer wrote: |
| 5 |
> On 11/23/12 22:32, Thomas Sachau wrote: |
| 6 |
>> Ian Stakenvicius schrieb: |
| 7 |
>>> On 22/11/12 11:22 PM, Robin H. Johnson wrote: |
| 8 |
>>>> On Thu, Nov 22, 2012 at 08:22:10PM -0600, Donnie Berkholz wrote: |
| 9 |
>>>>> On 11:11 Sun 18 Nov , Robin H. Johnson wrote: |
| 10 |
>>>>>> Here's a list of every package where I'm a maintainer and there |
| 11 |
>>>>>> is no herd listed (but their might be other maintainers): |
| 12 |
>>>> I didn't say I was dropping any of the packages, merely making an |
| 13 |
>>>> explicit list of packages I maintain, that other developers are |
| 14 |
>>>> welcome to touch - if they want to take them over explicitly, that |
| 15 |
>>>> would be great too. |
| 16 |
>>> |
| 17 |
>>> |
| 18 |
>>> .. For certain things, I think it would be very beneficial for this |
| 19 |
>>> to be true (other dev's welcome to touch) across the tree. Maybe if |
| 20 |
>>> there is enough general support for it, we should change our default |
| 21 |
>>> of "never touch a maintainer's package without permission of the |
| 22 |
>>> maintainer/herd", to "OK to touch unless package metadata explicitly |
| 23 |
>>> requests not to" ...? And we can put a tag in the metadata to |
| 24 |
>>> indicate this (or even to indicate what other dev's can and can't |
| 25 |
>>> touch -- ie, can touch *DEPEND, can bump EAPI, cannot add features, |
| 26 |
>>> cannot bump)? |
| 27 |
>>> |
| 28 |
>>> Thoughts? |
| 29 |
>>> |
| 30 |
>>> |
| 31 |
>>> |
| 32 |
>> |
| 33 |
>> What certain things do you have in mind? In wich situation do you see a |
| 34 |
>> simple "May i touch the package?/ok for this patch?" as too much to do |
| 35 |
>> before touching a package? |
| 36 |
>> |
| 37 |
> To me it's random noise, if I'm in the package metadata just do it. No |
| 38 |
> need to distract me :) |
| 39 |
|
| 40 |
I completely agree. There is a lot of territorialism that is |
| 41 |
*completely* unwarranted. If you see an issue with one of my packages |
| 42 |
and want to fix it, please, be my guest. Especially if it had a bug on |
| 43 |
bugzie and you close that bug. I get an email when my packages are |
| 44 |
touched, if I don't like your change I'll tell you why and then fix it. |
| 45 |
If you horribly break my package, you may hear about it, but you |
| 46 |
certainly won't get yelled at for fixing my bugs or bumping a package. |
| 47 |
|
| 48 |
Thanks, |
| 49 |
Zero |
| 50 |
> |
| 51 |
> And there's tons of packages that have a "maintainer" in metadata and |
| 52 |
> bugs just go into nirvana (like apache)... |
| 53 |
> |
| 54 |
> |
| 55 |
|
| 56 |
-----BEGIN PGP SIGNATURE----- |
| 57 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 58 |
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ |
| 59 |
|
| 60 |
iQIcBAEBAgAGBQJQsjykAAoJEKXdFCfdEflK0kUQAIB42lvd+oBP9xC9n9krkyzA |
| 61 |
pIdQw/npCZtfQ4ZRXjkrhWf8uP9RkwB04qmFRO/DrxFlMu5QJ+wGPeu8zqRCJBri |
| 62 |
GWqMATtZdvxHGeyKoAc/jJjp9+OHQ+izR7sGGo26uttj5QcA51e8e+568rw1xXk4 |
| 63 |
FQqQEOP9WXL8z8NOOo8ybv3SBqSg/+yHl05aInLhutKQAAtdOPy60nblGPMEyVIJ |
| 64 |
deoMFUU5PsJRaAsHL30iBlclFpgn6UK8bdxTfMiXvEECUrAj+Hx6vSIh8cMPCdLq |
| 65 |
SHT6Dcs8JkhKGEMX0v3CBzZ4yU/y36cSwNMah9eSFVnfW/R+7Mpt9Q3lfElwOSkl |
| 66 |
OAtDqwEiyTgTG/ucOkFb+UBaAOpdlRsC0vbck5RDQaF3AWERpBx9AZ/qVjRg39jt |
| 67 |
Yn7iads9FUAtrQ5bgMxHPkDlzNF50R99Ud41rJ1vZwl0JdrAgem5Pt2cO6TPEeZ8 |
| 68 |
6SeyVYQdRpqO3fMi6ijYTZEPiIX+EUJ8RkunUwgMHAhcn2IeAtkbbY5a3+1V2wpm |
| 69 |
lIP5di6TujmlX7x9zy6UI2ItSnvlwX/rq2XkPOyo4j+wyyQJN4VD2QT4wERuDADK |
| 70 |
ICJA/yke8tmsVo3Uxjtv8Yqbuug/AvD9blxlLpEPcuY5XKZOsxzzQFeRG7u5S+aZ |
| 71 |
16yQHoOjDNFN9882Ggy5 |
| 72 |
=D8vW |
| 73 |
-----END PGP SIGNATURE----- |
Archives