| 1 |
On Tue, Mar 24, 2015 at 08:41:52AM +0100, Alexis Ballier wrote: |
| 2 |
> On Mon, 23 Mar 2015 13:22:25 -0400 |
| 3 |
> Tim Harder <radhermit@g.o> wrote: |
| 4 |
> |
| 5 |
> > Hey all, |
| 6 |
> > |
| 7 |
> > Having been around for a few years I've inherited or added quite a few |
| 8 |
> > pkgs to the tree that I wouldn't mind other people fixing/bumping/etc |
| 9 |
> > that don't fall into any current herds. |
| 10 |
> > |
| 11 |
> > With that in mind, I think it would be an interesting experiment if we |
| 12 |
> > had a collaborative herd (probably named "collab") that signals the |
| 13 |
> > status that anyone is generally free to fix, bump, or do sane things |
| 14 |
> > to the pkgs with the caveat that you fix what you break. |
| 15 |
> > |
| 16 |
> > Anyone else interested in such a setup? |
| 17 |
> sounds like nmu is what you want: |
| 18 |
> https://archives.gentoo.org/gentoo-dev/message/604102ed1392afd3bfe35bfb33da8796 |
| 19 |
Here's a quick stab at a <nmu> element for metadata.xml; based on vapier's |
| 20 |
comments. I'm not set on the name of '<nmu>', something like |
| 21 |
'<change-policy>' might be a cleaner choice. |
| 22 |
|
| 23 |
<nmu> element, which has machine-readable attributes: |
| 24 |
- who: |
| 25 |
- ANYONE - anybody can touch (implicit default) |
| 26 |
- REQUIRES_TEAM - you must be a team member of a team listed |
| 27 |
- REQUIRES_MAINTAINER - you must be an explicitly listed maintainer |
| 28 |
specific herds or devs can be explicitly listed if you want to direct |
| 29 |
people to ask somebody about your packages (but that person should |
| 30 |
probably be listed as a maintainer then). |
| 31 |
- timeout: |
| 32 |
this is how long you we suggest you wait for the maintainer/team to |
| 33 |
comment on your change. |
| 34 |
Format should be a short duration specifier per ISO8601 |
| 35 |
I'd like to default it to 1 week: 'P1W'. |
| 36 |
- scope: |
| 37 |
How big of changes are ok? |
| 38 |
- NONE - (included for completeness) |
| 39 |
- STABLE - you can mark it stable after the normal 30 days |
| 40 |
- VERBUMP-MINOR - strictly a minor version bump, no other changes |
| 41 |
- TRIVIAL - simple, strict bugfixes (implicit default) |
| 42 |
- VERBUMP-MAJOR - a major version bump |
| 43 |
- MAJOR - rewrites, large functionality changes |
| 44 |
|
| 45 |
<nmu> element may also have human-readable content, to help clarify your |
| 46 |
intent if you think you cannot make it sufficiently clear with the |
| 47 |
machine attributes. |
| 48 |
|
| 49 |
Under this proposal, I'll be tagging most of my packages with: |
| 50 |
<nmu who='ANYONE' timeout='P0' scope='TRIVIAL' /> |
| 51 |
|
| 52 |
Fragile things might be tagged with: |
| 53 |
<nmu who='REQUIRES_MAINTAINER' timeout='P2Y' /> |
| 54 |
|
| 55 |
It should be valid to have multiple elements; something fragile to patches |
| 56 |
(eg qmail), but ok for bumping minor versions, because upstream is very |
| 57 |
good about API breakage: |
| 58 |
<nmu who='ANYONE' timeout='P2W' scope='VERBUMP-MINOR,!STABLE' /> |
| 59 |
<nmu who='REQUIRE_TEAM' timeout='P1W' scope='VERBUMP-MAJOR' /> |
| 60 |
<nmu who='REQUIRE_MAINTAINER' timeout='P0' scope='MAJOR' /> |
| 61 |
|
| 62 |
Overall, I suggest that these two elements become the implicit default: |
| 63 |
<nmu who='ANYONE' timeout='P1W' scope='TRIVIAL' /> |
| 64 |
<nmu who='REQUIRE_TEAM' timeout='P1W' scope='MAJOR' /> |
| 65 |
|
| 66 |
-- |
| 67 |
Robin Hugh Johnson |
| 68 |
Gentoo Linux: Developer, Infrastructure Lead |
| 69 |
E-Mail : robbat2@g.o |
| 70 |
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 |
Archives