community.network VS overview

Updates from Ansible networking team. * We have enabled periodic jobs through GHA for network collections. * We are working on community.ioscm collection which works for iosxe on controller mode, when the appliance is in sd-wan infrastructure! * IRC Meeting changes. * We want someone who will look into ansible-lint fixes for community.network collection.

The community.network collection versions 3.3.1 (Final EOL release, changelog) and 4.0.2 (changelog) have been released!

community.network collection 5.0.0 has been released! See the changelog for details. Special thanks to felixfontein for removing flat-mapping and other improvements!

Community Network Collection 4.0.0 has been released and is available to download! See changelog for details regarding the major changes and deprecated features!🎉

The community.network minor releases 2.3.0 & 3.3.0 have been released!🎉 Thanks to all the awesome people who contributed to them!❤️

community.network 1.3.7 & 2.2.2 & 3.2.0 have been released with some improvements and bug fixes (see changelogs 1.3.7, 2.2.2, 3.2.0 for more details)🎉

community.network collection versions 1.3.6, 2.2.1, and 3.1.0 have been released! Special thanks to felixfontein!

We are looking at reducing the maintenance for old stable branches for community.general and community.network collection repositories. We'd welcome your feedback, in particular if you think you may be negatively impacted by the change. Full details of the proposal, and the ability to record your vote can be done via community-topic#55.

As mentioned in last week's Bullhorn issue, cyberark.pas is subject to removal from version 9 of the Ansible community package due to unresolved Collection Requirements violations. A week has passed since the community-topics issue was filed and other SC members confirmed the violation, so a vote has been started (vote ends on 2022-12-16).

cyberark.pas is subject to removal from version 9 of the Ansible community package due to unresolved Collection Requirements violations. Please see community-topics#168 for more information.

The community steering committee has started a vote on whether we should amend the Ansible community package removal process to consider collections with unresolved Collection Requirements violations unmaintained and thus subject to removal. Please see the PR that amends the policy and the community-topics ticket for more information.

The Ansible Community Steering Committee has approved a change to the Collection Requirements re. SCM and release requirements. Collections were always required to tag releases, but we have clarified what tagging actually means. We have also explicitly stated that "collection artifacts released to Galaxy MUST be built from the sources that are tagged in the collection's git repository as that release." Please see the full change for more information.

We are happy to announce that the ibm.spectrum_virtualize collection has been included in the ansible community package. Thanks to everyone who helped review the collection and thanks to the maintainers for submitting the collection and making it satisfy the Collection requirements!

How? Copy the Review checklist into a discussion and go through it. See the complete example.

We've recently signed off on that process, which you can review here.

Your votes needed! Proposal: merge and adopt the procedures defined in Describe how collections can be removed from the Ansible package. Please vote in this issue (and not in the PR). The vote will close on 2022-04-27.

Pros: - Motivation for developers to create new collections which can become a part of Ansible package ("so popular and important in IT world", etc). - Motivation to create content satisfying the collection requirements. - Motivation to maintain included collections to avoid kicking them out from the package "I can't show off with my collection any more..:(" - ...(suggest yours)

We have docs in three places today for contributors: * ansible/ansible in the community folder * ansible/community-docs - more collection focused * ansible-collections/overview - has deeper collection contribution details