I am pretty sure there is no sync anymore.

A while back we made all the components owned by @pbokoc so he could sort out existing bugs and see what we needed here.

If there's a sync needed we can look at one, perhaps @pbokoc could chime in here?

@pfrields, what exactly do you mean by syncing owners? I'm the default assignee on any BZ bug that anyone opens under the Fedora Documentation product, anything anyone opens there goes into my inbox.

Bugzilla is considered deprecated for Fedora docs, and people generally respect that - since the beginning of 2020, only 5 BZs have been opened against the whole product (one of them was about the recent docs outage), I always catch them since I get notified, copy the report into an issue in a relevant repo, close the bug and provide a link to the reporter so they can follow up on pagure/github/wherever.

The BZ product for Fedora Docs still has some old bugs open that I haven't cleaned up yet, I need to close them all and move the still relevant ones to Pagure/GitHub/wherever and then just ask to have the whole Fedora Documentation project removed, but I haven't had time to do it yet. Given the fairly low volume of bug reports being opened in Bugzilla I haven't been treating it as a high priority, but I really should get to it already, it's been a long time.

So it's unclear to me what needs doing here... should we just close this? Can you update the doc @pbokoc?

@pbokoc I think that I still get cc'd on all these bugs from my "olden days" membership in the Fedora Docs team, back when we used CVS. If there's not an automated way to fix that, I can just email the BZ maintainers about it -- just let me know please, Petr.

If thats the goal, I can remove you from all the fedora-docs components... just let me know if you would like that done.

@pfrields that's the simplest way to do that. I'll mass remove you from CC on every currently existing bug (you might get a wave of spam from that, but it'll be one time only), and @kevin can make sure you're not automatically added to any new ones in the future.

@kevin Yeah, I think we can close this after we're done - the docs don't need updating (maybe except for the contact info on top?), any scripts should still work the same, they're just not being used often.

Done.

@pbokoc You don't even have to worry about the current bugs, that's on me to handle.

If you guys get me off the "future bugs" list, it'd be much appreciated. It's not urgent of course; I just know I won't have any cycles to spend on docs in the foreseeable future.