Would need more information about what is needed here.
The issue is to decommission the old fedoraplanet? On which machine it is running? (people01?)
Since the new fedoraplanet has been moved to ocp [0], can be the blocking issue #10383 considered solved?
How do we stand on the steps outlined by Kevin here? [1]

[0] https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/4J6UJ6J4NXM7C4GR67KBQBYOBIADERY7/
[1] https://pagure.io/fedora-infrastructure/issue/10383#comment-904194

@phsmoura @kevin

fedorapeople.org (also people02.fedoraproject.org ) provides a number of services to contributors. See: https://fedoraproject.org/wiki/Infrastructure/fedorapeople.org

Amoung that list is the fedoraplanet.org setup. It currently runs there and uses ~/.planet files to build the content.
We are moving that to use a blog url in the account system and run in openshift... thats almost ready, but... it's not 100% ready to switch over.
We need to announce to users whats happening, give them time to add their blogs, then set a date to switch over to the new one.
After thats done, we can look at moving the people02 server to rhel9.

I sent an email to fedora-infra and posted in discussion to inform people about new planet and asked them if they find any issue. Now just waiting for feedback before retiring the old one

How does May 21st sound like for a sunset date for the old planet?

Thats 3 weeks from today, hopefully that would be enough time for people to update things.

Next steps as I see them:

• Agree to this date or some other one (I guess you could reply to those threads you started suggesting it)

• Once thats set, we need to do a new post to the devel-announce list to tell people to actually set things.

• Then when the sunset date hits, we take down the old planet, and update things to point to the new planet.

• Also, we need to update the existing planet wiki page.

Then, finally, I think we would be done. ;)