I think that this is what stopped us originally. How will we know if a project violates the requirements and that we should delete it? Will we (CPE team) police it? If not then who will?

I would suggest adding to the end something like "Note that this list is not exhaustive, there may be other reasons we disable or delete your application, but we will make every effort to communicate with you about any such actions"

I think that this is what stopped us originally. How will we know if a project violates the requirements and that we should delete it? Will we (CPE team) police it? If not then who will?

Well, I think it's like anything else in fedora (packages, git repos, wiki pages). We ask people to say they will not violate the requirements and then if someone tells us they do or we notice it, we take action.

I added the note that @kevin mentioned. The template in fedora-infrastructure repo is now available as well, as I didn't noticed that this should be pushed directly to tickets repo. Thanks @kevin for pointing that out.

@patrikp As @kevin said, if somebody reports that the service hosted in communishift is doing something they shouldn't we will delete it. Otherwise we need to have a job or mention this in release documentation that all the projects will need to be deleted after new Fedora release. I'm not sure where the post release check list is documented right now, but it should be part of it.

Maybe having a ansible playbook that will do that with the list of whitelisted projects that should stay is a good idea as well.