2026-10-31T14:43:29  <matrix-o-o> <SFaulken> acidsys so I know code.o.o is a problem, and it's probably easier to migrate away from it, I'm just not sure _where_ to migrate to, for instance, for things like the mod-team and board issue trackers, where we need the ability to have private issues/tickets, and I don't think we've currently got anything else that can do it
2026-10-31T14:45:56  <matrix-o-o> <malcolmlewis> SFaulken: Maybe we could implement something on the Forum?
2026-10-31T14:46:11  <matrix-o-o> <malcolmlewis> hendersj: ^^
2026-10-31T14:46:26  <matrix-o-o> <SFaulken> I'm not completely opposed to that idea, in theory. I mostly despise discourse, but it might not be the worst option.
2026-10-31T14:51:50  <matrix-o-o> <SFaulken> I mostly don't want to get back to where the only long-term traceability of board decisions are whatever mailing list archives people are keeping on their local machines of the board-ML, that's been a recurring problem since I've been on the board, for certain issues, from before we started using the pagure issue tracker.
2026-10-31T14:56:52  <matrix-o-o> <knurpht - Gertjan> There are also more teams that (used to) use code.o.o, f.e, membership-officials. Just saying.
2026-10-31T14:57:43  <matrix-o-o> <SFaulken> yeah, there are, we kind of need to come up with something, if keeping code.o.o around is just going to continue being a problem for the heroes, with the maintenance burden.
2026-10-31T16:23:59  <matrix-o-o> <hendersj> I don't know that Discourse is the right place - it's not really a ticketing system.  But we do clearly need someplace for these things to be housed, and if it's not code.o.o, we need a solution sooner rather than later for some of these things (like mod-team, board issue trackers, membership-officials, etc.)
2026-10-31T16:25:13  <SFaulken> forge issues aren't a great option, to the best of my knowledge gitea/forgejo don't do private tickets.  gitlab does, but it's sort of janky
2026-10-31T16:28:31  <matrix-o-o> <hendersj> We also need to consider how we migrate the existing data, because there are important records that need to be preserved.
2026-10-31T16:28:51  <matrix-o-o> <hendersj> So at the very least, the existing issue needs to be fixed well enough to be able to get at the current data.
2026-10-31T16:42:50  <cboltz> for tickets (including private tickets), progress.o.o should work
2026-10-31T16:43:26  <cboltz> forgejo has an open feature request for private tickets (in an otherwise public tracker), but I don't know when someone will implement that feature
2026-10-31T16:43:31  <SFaulken> sure, if that's the direction we want to go, and if it's not adding a bunch of work to the heroes to do.
2026-10-31T16:44:44  <cboltz> the solution we have today is progress.o.o - adding another project there is done in some minutes, and we maintain progress.o.o anyway
2026-10-31T16:46:06  <cboltz> oh, and for backing up the tickets on code.o.o - IIRC pagure manages the issues as a git repo which you can clone (please ask a search engine for details)
2026-10-31T16:47:41  <cboltz> actually I have it at hand:   git clone ssh://git@code.opensuse.org/tickets/project/irc.git   (that would be for the project/irc tickets)
2026-10-31T18:23:55  <matrix-o-o> <hendersj> So I guess we'd just need to look at if there's a way to import that into progress, or figure out some way of securely storing that historical data so the teams that need access to it can get it.
2026-10-31T20:31:34  <acidsys> yes already wanted to send email about shutdown of code.o.o
2026-10-31T21:56:09  <matrix-o-o> <hendersj> I did run a git clone per cboltz's suggestion, but noted that a ticket I opened while it's having issues wasn't included in the clone I pulled (this from mod-team).  So it seems that clone perhaps isn't comprehensive.
2026-10-31T21:56:42  <matrix-o-o> <hendersj> Or maybe I'm not authenticated to pull private tickets (which my ticket is).  I hadn't thought about that until just now, so I'll have to check that later today.