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