On 18. 12. 19 15:53, David Cantrell wrote:
Maybe if a module bundles a package, the module maintainer also becomes a
co-maintainer on the bundled package?
How this appears to work now:
1. If one bundles a package in a module they need to create a stream branch
(unless they bundle form master/f31 etc. which is probably possible, but I
haven't seen that happen much).
2. If they intent to push to the stream branch, they need ACLs.
3. Either they need to become a co-maintainer or they need to be provenpackagers
(for example, sgallagh has commit rights for python-django to be able to
maintain the 1.6 branch*, but mbooth has no commit rights in protobuf but is a
provenpackager).
I think that if somebody wants a stream branch in a package they should become
co-maintainers first. Using the provenpackager rights for this without talking
to the non-modular maintainer(s) is wrong. It goes against:
https://fedoraproject.org/wiki/Who_is_allowed_to_modify_which_packages
But OTOH, I don't like of the modular maintainer just becomes a co-miantainer
automatically, they should talk to the non-modular maintainers first. See also
https://pagure.io/modularity/issue/115
(* Side note: I believe sgallagh is also a provenpackager and yet he explicitly
has the commit rights set - and that is what I think makes sense - it signalizes
explicit consent.)
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
