2026-01-27T17:10:52  <cboltz> admin-auto has two mails from quiz-update.service sent nearly at the same time (0:30 UTC, with ~30 seconds difference) which both show a failure to start the main instance
2026-01-27T17:11:26  <cboltz> any idea why quiz-update did run twice at nearly the same time?
2026-01-27T17:48:18  <acidsys> cboltz: according to systemd, they run one after each other (about 1 minute apart), not at the same time
2026-01-27T17:56:16  <acidsys> both were triggered by the timer. the first one (started 00:26:57) probably through OnStartupSec=10, as the machine was just about finishing to reboot at the time (think it's expected to not be precise as other things are stil starting too). the second one (started 00:30:00) exactly lines up with OnCalendar=*:0/30
2026-01-27T18:36:31  <cboltz> ah, reboot-triggered - that explains it, thanks!
2026-01-27T18:41:33  <cboltz> completely different question - https://build.opensuse.org/project/monitor/openSUSE:infrastructure:mailman3 looks quite broken (literally - several packages are in "broken" state because the diff to the linked package can no longer be applied)
2026-01-27T18:42:31  <cboltz> do we still need these packages in their patched version, or could we use unpatched or even Tumbleweed packages?
2026-01-27T18:44:03  <cboltz> (basically our version enforces python312 instead of default python)
2026-01-27T18:46:52  <acidsys> it needs to be tested, at the time, the factor version built against default python and that broke most functionality when default python in tw was switched to 3.13
2026-01-27T18:47:04  <acidsys> I did not track if it was repaired in the meanwhile
2026-01-27T18:47:41  <acidsys> (whether by pinning to an older version or shipping the required packages which backport ex-stdlib stuff to 3.13)
2026-01-27T18:49:03  <acidsys> before that incident, the only package which we needed in the custom version is python-mailman-web, because we have services there which officially are shipped in a different package
2026-01-27T18:50:04  <acidsys> (that was yet another big todo, to migrate those to the ones shypper in python-HyperKitty)
2026-01-27T18:50:35  <cboltz> well, we'll probably never run out of todos ;-)
2026-01-27T18:57:53  <cboltz> I'm afraid the diff for python-mailman-web is a bit bigger than just some services (including a version update in o:i)
2026-01-27T18:59:58  <cboltz> anyway, the most interesting question is if it works with 3.13 now
2026-01-27T22:57:16  <matrix-o-o> <jeff_mahoney> Hi everyone - as promised during oSC in June, I've (mostly) put together a document to serve as a starting point for a discussion about governance. One thing I want to add is recognition and representation for the Heroes. The question I have is: how do _you_ want that to look? In other areas, we have committees with chairs - where the committees are elected by the members and the chairs elected by the committee...
2026-01-27T22:57:22  <matrix-o-o> ... members. Heroes are entirely voluntary and I don't want to change the model under which you already operate. What I _would_ like is to invite a representative from the Heroes to Board meetings to give an update on status, goals, and frustrations and to raise any issues that the board could help with either directly or with publicity.
2026-01-27T23:27:33  <acidsys> Hi jeff_mahoney, not speaking for others, and I hope others chime in too - but I did join the board meetings occasionally in the past (albeit it not fitting well during working hours). I personally feel the board is lacking an escalation path for issues - typically when I bring something up, it is because I already exhausted the conventional methods (like opening tickets and asking people
2026-01-27T23:27:35  <acidsys> internally) - yet the board was so far only able to attempt the same methods and not achieve results. Worse, the issues I collected over the years were all eventually "forgotten" about when I stopped nagging - I thought being present and inquiring in the meetings would help over repeatedly sending emails, but I got the same I got outside the meetings over the years: mostly empty promises.
2026-01-27T23:27:37  <acidsys> That being said, I am happy to work with you if you think it would be useful to try again - just think you should know about my past experience prior. :)
2026-01-27T23:31:41  <matrix-o-o> <knurpht - Gertjan> acidsys: Sorry to say so, but I can confirm this from a mod perspective.
2026-01-27T23:38:46  <matrix-o-o> <jeff_mahoney> Understood. The lack of any real structure is a frustration for both sides there. One of the goals of this project is to establish the structure so it isn’t a train of one-offs that need to be handled specially.