news-for-maintainers
overview
news-for-maintainers | overview | |
---|---|---|
4 | 12 | |
24 | 246 | |
- | 1.2% | |
1.3 | 3.7 | |
about 1 year ago | 9 days ago | |
- | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
news-for-maintainers
-
The Bullhorn #83 (Ansible Newsletter)
If you are using GHA to run tests on collections, you might have noticed strange failures when using ansible-test's --docker option when using ubuntu-latest. Read more about this and how to fix this in this issue.
-
The Bullhorn #52 (Ansible Newsletter)
In ansible/ansible, the stable-2.13 branch has been created (more infos), and the version of the devel branch has been bumped to 2.14.0.dev0 (more infos).
-
The Bullhorn #44 (Ansible Newsletter - now weekly!)
If you want to discuss this, we welcome feedback in ansible-collections/news-for-maintainers/discussions/4.
-
The Bullhorn #43 (Ansible Newsletter)
In accordance with the Community decision, we have created the news-for-maintainers repository for announcements of changes impacting collection maintainers (see the examples) instead of Issue 45 that has just been closed. To keep yourself well-informed and, therefore, things in your collection working, please subscribe to the repository by using the Watch button in the upper right corner on the repository's home page. If you do not want to get notifications about related discussions, please subscribe only to Issues. Please read the brief guidelines on how the repository should be used. Please avoid unnecessary discussions in issues, use the Discussions feature. Every comment posted will notify a lot of folks!
overview
-
The Bullhorn #84 (Ansible Newsletter)
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).
-
The Bullhorn #83 (Ansible Newsletter)
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 Bullhorn #80 (Ansible Newsletter)
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 Bullhorn #79 (Ansible Newsletter)
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.
-
The Bullhorn #69 (Ansible Newsletter)
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!
-
The Bullhorn #62 (Ansible Newsletter)
How? Copy the Review checklist into a discussion and go through it. See the complete example.
-
The Bullhorn #56 (Ansible Newsletter)
We've recently signed off on that process, which you can review here.
-
The Bullhorn #55 (Ansible Newsletter)
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.
-
Future of Ansible package
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)
-
The Bullhorn #49 (Ansible Newsletter)
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
What are some alternatives?
community.aws - Ansible Collection for Community AWS
Ansible - Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy and maintain. Automate everything from code deployment to network configuration to cloud management, in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com.
ansible.utils - A collection of ansible utilities for the content creator.
docsite - Static HTML and assets for docs.ansible.com
ansible-borgbase - Ansible modules for managing borgbase SSH keys and repositories
awx - AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
community.google
ansible-lint - Best practices checker for Ansible [Moved to: https://github.com/ansible/ansible-lint]
ara - ARA Records Ansible and makes it easier to understand and troubleshoot.
community-docs - docs.ansible.com/community
community.network - Ansible Community Network Collection