One thought before we start moving this through the process:

• I'd like to see "retirement of the pagure.io/fedora-websites repo" as an explicit outcome (even if it's a stretch goal). Having separate repos (fedora-web/websites is getfedora and fedora-websites is….everything else) makes it more difficult to maintain and it also results in a lot of mis-filed tickets from the community. In theory, a lot of the work has been done already, although it has surely drifted a lot since then. If you don't want to take on the whole site, let's at least add "and Labs" to mentions of "Spins". That way the main release-delivering websites are in the same place (although alt and arm should also be in that category, probably…)

I'm very excited abut this objective proposal because I hope it leads to taking away my commit access to the websites because there's a healthy team that can handle it. :-)

[Edited to clarify context about the repo retirement point]

@ramyaparimi The Council had no significant issues, so we want to run this through the Policy Change process. Can you draft a short Community Blog post so we can start that? See the Community Outreach Revamp proposal post for an example.

@bcotton thank you for the update . Will be working on the CommBlog.

Community Blog article published.

The community comment period has passed. Council members, please vote by 9 June.

+1

+1

+1

+1

+1

+1

After a week, the vote is (+6,0,-0). The proposal is approved.

Thank you everyone!!