The schedule could use some polishing. Some things that are not there should be there, some that are there should not, individual events/actions do not link to relevant SOPs, capitalization is not consistent. I believe it would be beneficial to have it streamlined. That way it will be clear what is happening when and what specifically needs to be done.

I have thought about what the best way to do this would be and came to the conclusion that a hackmd doc with the proposed new structure would be the best way forward as it will make it easy to leave comments and make changes which is considerably more difficult with issue tickets.

Once we have the hackmd document in its final form (i.e. all Release Engineers agree on it) we can send it to the FPgM to make the changes (or open an individual issue for each step that needs to be changed, to be decided).

URL of the schedule:
https://fedorapeople.org/groups/schedule/f-43/f-43-releng-tasks.html

The Pagure repository says:
The schedule content is exported from a tool called Smartsheet. If you try to edit the schedule files directly, your changes will get lost. To make changes, open an issue. The FPgM will make the changes in Smartsheet and export them as appropriate.

URL of the repository:
https://pagure.io/fedora-pgm/schedule