Hi Matthew,
On Thu, Feb 13, 2020 at 4:30 pm, Matthew Miller
<mattdm(a)fedoraproject.org> wrote:
Background: we want to notify spin maintainers when their particular
compose fails. Specifically, tag them in the ticket so they get
notified.
(We could also possibly do email notifications or something else,
but that
gets into the general problem of "sending automated email sucks",
so for
first pass, tagging people in the pagure repo seems good.)
Related ticket: <
https://pagure.io/releng/compose-tracker/issue/4>
Problem: there's no consistent machine-readable source of truth for
who to
tag. Maintainer information is found in comments in the various
kickstarts
in <
https://pagure.io/fedora-kickstarts/tree/master>, but it's not
in a
consistent format, and is sometimes a group mailing list rather
than a FAS
ID.
Two competing proposals
Proposal A: make that header information consistent and required,
with a
format like:
# SPIN-Maintainer-IDs: mattdm, mboddu
# SPIN-Maintainer-Names: Matthew Miller, Mohan Bodhu
# SPIN-Mailing-List: fedora-imaginaryimage(a)fedoraproject.org
<mailto:fedora-imaginaryimage@fedoraproject.org>
or something like that.
Proposal B: remove maintainer info from unstructured comments,
introduce
new "maintainers.toml" file. (Because Of Course It Does,
compose-tracker
uses both Toml and Yaml. I've been playing with Rust lately, so I
arbitrarily pick Toml.
[spins]
[spins.imaginary]
fas = [ "mattdm", "mboddu" ]
maintainers = [ "Matthew Miller", "Mohan Bodhu" ]
or something like that. I'm just making this up as I type.
Thoghts?
Whatever implementation happens would be great. In the Ubuntu world, we
have something similar where if a particular "flavor" fails to spin,
then the development groups for those flavors are notified via email. I
was noticing there was no such notification when taking over Jam, so I
didn't even know where to look to fix the kickstart at first. So, I
think any sort of notification to this effect would be invaluable.
Additionally, I believe something like this would prevent spins from
being outright abandoned as it would make it difficult to ignore a
daily email that a spin is failing. At least then the maintainer would
be more likely to want to hand it off as opposed to simply abandoning
it.
Just my 2c.
Erich
---
Erich Eickmeyer
Fedora Jam Maintainer