[Epic] move most community eng tasks upstream

[samccann]

Currently in some areas like release (ansible-core and ansible community package) as well as building and publishing documentation, the community can not help or own those area as there is an hard dependency on being in Red Hat VPN to be able to trigger the Jenkins jobs.

The goal of this EPIC is to move all the things the community engineering team does that requires VPN access to a fully upstream only process where any community member could participate if they want, are willing to and trust worthy,

• audit what - in the process of releasing ansible community package - requires VPN, why and how we could bring that completely upstream/public
• audit what - in the process of releasing ansible-core - requires VPN, why and how we could bring that completely upstream / public
• Opening up Ansible Community package release for the community
• [Epic] Migrate Ansible community docs hosting to ReadTheDocs #497
• open up core release build so community can build it.

[samccann]

After talking with the core team, we agreed to move the release pipeline of ansible-core from the internal team + VPN to a Github Action triggered whenever a new tag is created. This will completely make the release process of ansible-core live upstream and proper permission could be given to who we want to allow to create tags.

[samccann]

@anweshadas @oraNod - Is the checklist accurate? If so, I can turn them into subissues so we can track each one separately etc.

also, if any of the checklist items are done, please mark them done here so we know the status...thanks!

[oraNod]

@samccann I think maybe we should break opening up the package docs to community as a separate epic. I think @anweshadas is done with the package build side so if she can tick the other checkboxes then breaking the docs build into a separate thing means we can close this.

[samccann]

@anweshadas - are we at the point where the community package could be built by someone else? ...and if so, do we want to ask for a release manager for Ansible 8 or is that too soon?

[anweshadas]

Proposing it for Ansible 8 will be too soon.

[samccann]

Ok thanks for the clarification!