| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 06/21/2013 09:42 PM, Robin H. Johnson wrote: |
| 5 |
> On Fri, Jun 21, 2013 at 09:06:30PM -0400, Mike Frysinger wrote: |
| 6 |
>> On Friday 21 June 2013 20:26:03 Robin H. Johnson wrote: |
| 7 |
>>> On Fri, Jun 21, 2013 at 08:17:38PM -0400, Mike Frysinger |
| 8 |
>>> wrote: |
| 9 |
>>>>> I'm not going into review systems here at all, I'm simply |
| 10 |
>>>>> trying to have a policy of what changes are |
| 11 |
>>>>> welcomed/blocked WITHOUT interaction from the listed |
| 12 |
>>>>> maintainer(s) of a given package/herd. |
| 13 |
>>>> |
| 14 |
>>>> add a new field to metadata.xml that declares the state. |
| 15 |
>>>> make it an enum: ANYTHING_GOES (the default) REQUIRES_HERD |
| 16 |
>>>> REQUIRES_MAINTAINER |
| 17 |
>>> |
| 18 |
>>> I wish it was that easy. |
| 19 |
>>> |
| 20 |
>>> Despite being ANYTHING_GOES on most of my packages, I don't |
| 21 |
>>> want people to add giant features like qmail patchbombs; so we |
| 22 |
>>> need to figure out something like the Debian NMU listing of |
| 23 |
>>> what's acceptable. |
| 24 |
>> the maintainers intent has to be machine codable |
| 25 |
> So we have the following facets of NMU permissions: Who What |
| 26 |
> |
| 27 |
>>> Does a version bump count as an acceptable trivial change? |
| 28 |
>> that's up to the maintainer |
| 29 |
> This needs to be in the above data: |
| 30 |
> |
| 31 |
> So we have: Who = {ANYTHING_GOES, REQUIRES_DEV, REQUIRES_HERD, |
| 32 |
> REQUIRES_MAINTAINER} What = {NONE, TRIVIAL, MINOR_FEATURES, |
| 33 |
> VERSION_BUMP, MAJOR_FEATURES} |
| 34 |
> |
| 35 |
> So most of my packages might be coded with: <nmu-policy |
| 36 |
> who="REQUIRES_DEV" what="VERSION_BUMP" /> <nmu-policy |
| 37 |
> who="REQUIRES_HERD" what="MAJOR_FEATURES" /> |
| 38 |
> |
| 39 |
> - If you're a developer, you can do trivial fixes, add minor |
| 40 |
> features, bump the version. - If you're in the herd, you can add |
| 41 |
> major features. |
| 42 |
> |
| 43 |
This is actually pretty sane... I like this idea. |
| 44 |
|
| 45 |
- -Zero |
| 46 |
-----BEGIN PGP SIGNATURE----- |
| 47 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 48 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 49 |
|
| 50 |
iQIcBAEBAgAGBQJRxRn3AAoJEKXdFCfdEflKS5AP/08vkwpc7k5IxEXKShRNUs2b |
| 51 |
1a4WOaFLwWzC3tU1X162qogct/KAUIPCmfe1RlgZs9f8hLDzEUQ9wP50gE46ypP0 |
| 52 |
lLQj0Kg634G/uDbQFMMjiwaT0YJgxaufoLIMNDlxxxKGLKYAevvcmcHtAYLfpHr7 |
| 53 |
lakPlf9SEW002HFN3Yo7cO9eO9X6v0qLnaYxMALdm08G+KkadZ/0wlb/GeQGA6Kl |
| 54 |
RhRDXX8dPSv54O0PTnmEcq3FgOrT1GtxJ590jLB88eRN/MLspdcXJSZ3nPO/Byw2 |
| 55 |
RATTpBTMMiOXTLv374TBQ73ggnYXk/TPw4BAHSdW31eaZMDiKOFA/4BxAybZ9UpA |
| 56 |
CWfGY+XJaJHZqSXoD/Ngz3dphv9U8BkzK0e6PnPl1Y0v70Ayv0XDmSIstYxfRGdl |
| 57 |
6OyUyg8ANvh3vGxJdMGsSAdt2rsMrOas8Yvt4eqb2mOLfJE+oosUiklN7wfAH0+n |
| 58 |
JTIJ0TJ9HTUA6Mu6ezIr5i5JJmey1byBN7OIpD6NgQUcfdJzXrK3ap/p6BEt12hb |
| 59 |
jVPtVGqilz7raGRtb+GnoVXIUtxYmgbIqv1vx0vZTJbAJI0v6JweBU9oQAViaN9I |
| 60 |
mf79M5YciP/ILfFJqc/oWYVabUtvknU3AUzVGf60h6K09IS8JbnIW4rpwaHDFYPE |
| 61 |
zNm2wZEkT2Q49NDo6Hx0 |
| 62 |
=2mTJ |
| 63 |
-----END PGP SIGNATURE----- |
Archives