From 05dcdd1f1089b3cdfcf9fef71b0bb7b79425ac24 Mon Sep 17 00:00:00 2001 From: Christian Ehrhardt Date: Wed, 6 Mar 2024 07:52:45 +0100 Subject: [PATCH] Ask to confirm ownership if a team was suggested We had this to some extend, but it was shown that it isn't clear enough yet so we decided we want to spell it out and require a comment by a representative of the owning team. Fixes: #52 Signed-off-by: Christian Ehrhardt --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index d98fb9af90..c89976577e 100644 --- a/README.md +++ b/README.md @@ -511,6 +511,10 @@ RULE: but then, as a first step, needs to get a team agreeing to own RULE: it before the case can be processed further. RULE: If unsure which teams to consider have a look at the current mapping RULE: http://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.html +RULE: In that case (you are not a representative of the team who will +RULE: gain the long term committment to this) please ask a representative +RULE: of that team to comment on the bug confirming that they are ok to +RULE: own it. RULE: - The package needs a bug subscriber before it can be promoted to main. RULE: Strictly speaking that subscription can therefore wait until the RULE: moment of the actual promotion by an archive admin. But it is @@ -718,6 +722,11 @@ TODO: There is no other package in main providing the same functionality. RULE: No matter how useful a rationale is and how unique a package might be RULE: it will need an owning team that is willing and able to spend the time RULE: to maintain it well for the benefit of all Ubuntu users and use cases. +RULE: If someone submitted an MIR on behalf of another team and suggested them +RULE: to own it, we expect someone representing that to be owning team to +RULE: comment on the bug and confirm that they are ok to own that package +RULE: (to avoid review and process effort being spent only to then +RULE: immediately be cancelled by a lack of ownership). TODO: A team is committed to own long term maintenance of this package. RULE: In the template to submit cases we ask the reporter to state a rationale RULE: why this should be considered. But a MIR team member needs to