Proposal for machine-readable contact info for spins maintainers
by Matthew Miller
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
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?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
4 years, 1 month
[fedora-kickstarts] branch master updated (0929a3f -> d3042d4)
by pagure＠pagure.io
This is an automated email from the git hooks/post-receive script.
kevin pushed a change to branch master
in repository fedora-kickstarts.
from 0929a3f Comment out paraview
add d3042d4 Add pipewire to disk
No new revisions were added by this update.
Summary of changes:
fedora-live-jam_kde.ks | 3 +++
1 file changed, 3 insertions(+)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
4 years, 1 month
Revamping the Release Readiness meeting
by Ben Cotton
(Posting to many mailing lists for visibility. I apologize if you see
this more times than you'd like.)
You may have already seen my Community Blog post[1] about changing the
Release Readiness meeting process. The meeting has questionable value
in the current state, so I want to make it more useful. We'll do this
by having teams self-report readiness issues on a dedicated wiki
page[2] beginning now. This gives the community time to chip in and
help with areas that need help without waiting until days before the
release.
I invite teams to identify a representative to keep the wiki page up
to date. Update it as your status changes and I'll post help requests
in my weekly CommBlog posts[3] and the FPgM office hours[4] IRC
meeting. The Release Readiness meeting will be shortened to one hour
and will review open concerns instead of polling for teams that may or
may not be there. We will use the logistics mailing list[5] to discuss
issues and make announcements, so I encourage representatives to join
this list.
[1] https://communityblog.fedoraproject.org/fedora-program-update-2020-08/
[2] https://fedoraproject.org/wiki/Release_Readiness
[3] https://communityblog.fedoraproject.org/category/program-management/
[4] https://apps.fedoraproject.org/calendar/council/#m9570
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
4 years, 1 month
