canonical / ubuntu-mir

Ubuntu Main Inclusion Process - formerly on https://wiki.ubuntu.com/MainInclusionProcess
14 stars 11 forks source link

Owning team requirement is confusing #39

Closed ist199099 closed 1 year ago

ist199099 commented 1 year ago

README.md has the following:

RULE: - All packages must have a designated "owning" team, regardless of
RULE:   complexity, which is set as a package bug contact. This is not a
RULE:   requirement for the MIR team ACK, but for the package to be promoted
RULE:   by an archive admin. Still, it is strongly suggested to subscribe,
RULE:   as the owning team will get a preview of the to-be-expected incoming
RULE:   bugs later on.

It is unclear whether "This" in the sentence beginning with "This is not a requirement for the MIR team ACK" refers to the requirement of having an owning team or to the requirement of the owning team being set as a package bug contact.

The context for this is Ubuntu bug 1986592 (the network-manager-openconnect MIR), namely comments #11 and #12 to that bug.

cpaelzer commented 1 year ago

From MIR meeting as input to the PR

[16:54] <luis220413> cpaelzer: It is a requirement for which stage(s) of the MIR process?
[16:54] <cpaelzer> I'm trying
[16:55] <cpaelzer> luis220413: it is not a requirement to have "the onwing team subscribed" to start the MIR and get the ACK. Oly to get the promotion to main done. But OTOH it is an absolute requitement to "have commitment of a team that will own it" to even enter the process
[16:55] <slyon> luis220413: I guess there are 2 stages: A MIR needs an owning team to be processed AND that team must be subscribed before being promoted by an AA.
github-actions[bot] commented 1 year ago

Thank you so much for creating your first issue and therefore improving the Ubuntu MIR documentation!

Please also attend the next weekly MIR Team meeting (every Tuesday at on the IRC Server irc.libera.chat in the #ubuntu-meeting channel) to discuss your issue with the MIR Team. You can follow these instructions on how to connect to irc.libera.chat.