@ -23,7 +23,7 @@ anti-harassment policy. We expect organizers to enforce these guidelines through
and we expect attendees, speakers, sponsors, and volunteers to help ensure a safe
environment for our whole community. Specifically, this Code of Conduct covers
participation in all Ansible-related forums and mailing lists, code and documentation
contributions, public IRC channels, private correspondence, and public meetings.
contributions, public chat (Matrix, IRC), private correspondence, and public meetings.
Ansible community members are...
@ -69,7 +69,7 @@ encourage our users to ask early and ask often. Rather than asking whether you c
question (the answer is always yes!), instead, simply ask your question. You are
encouraged to provide as many specifics as possible. Code snippets in the form of Gists or
other paste site links are almost always needed in order to get the most helpful answers.
Refrain from pasting multiple lines of code directly into the IRC channels - instead use
Refrain from pasting multiple lines of code directly into the chat channels - instead use
gist.github.com or another paste site to provide code snippets.
**Helpful**
@ -115,8 +115,7 @@ Policy violations
=================
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by
contacting `codeofconduct@ansible.com <mailto:codeofconduct@ansible.com>`_, to any channel
operator in the community IRC channels, or to the local organizers of an event. Meetup
contacting `codeofconduct@ansible.com <mailto:codeofconduct@ansible.com>`_, to anyone with administrative power in community chat (Admins or Moderators on Matrix, ops on IRC), or to the local organizers of an event. Meetup
organizers are encouraged to prominently display points of contact for reporting unacceptable
Please read and understand the :ref:`code_of_conduct`.
All communication and interactions in the Ansible Community are governed by our :ref:`code_of_conduct`. Please read and understand it!
Mailing list information
========================
Asking questions over email
===========================
Ansible has several mailing lists. Your first post to the mailing list will be moderated (to reduce spam), so please allow up to a day or so for your first post to appear.
If you want to keep up with Ansible news, need help, or have a question, you can use one of the Ansible mailing lists. Each list covers a particular topic. Read the descriptions here to find the best list for your question.
Your first post to the mailing list will be moderated (to reduce spam), so please allow up to a day or so for your first post to appear.
* `Ansible Announce list <https://groups.google.com/forum/#!forum/ansible-announce>`_ is a read-only list that shares information about new releases of Ansible, and also rare infrequent event information, such as announcements about an upcoming AnsibleFest, which is our official conference series. Worth subscribing to!
* `Ansible AWX List <https://groups.google.com/forum/#!forum/awx-project>`_ is for `Ansible AWX <https://github.com/ansible/awx>`_
* `Ansible Development List <https://groups.google.com/forum/#!forum/ansible-devel>`_ is for learning how to develop on Ansible, asking about prospective feature design, or discussions about extending ansible or features in progress.
* `Ansible Development List <https://groups.google.com/forum/#!forum/ansible-devel>`_ is for questions about developing Ansible modules (mostly in Python), fixing bugs in the Ansible core code, asking about prospective feature design, or discussions about extending Ansible or features in progress.
* `Ansible Lockdown List <https://groups.google.com/forum/#!forum/ansible-lockdown>`_ is for all things related to Ansible Lockdown projects, including DISA STIG automation and CIS Benchmarks.
* `Ansible Outreach List <https://groups.google.com/forum/#!forum/ansible-outreach>`_ help with promoting Ansible and `Ansible Meetups <https://ansible.meetup.com/>`_
* `Ansible Project List <https://groups.google.com/forum/#!forum/ansible-project>`_ is for sharing Ansible tips, answering questions, and general user discussion.
* `Ansible Project List <https://groups.google.com/forum/#!forum/ansible-project>`_ is for sharing Ansible tips, answering questions about playbooks and roles, and general user discussion.
* `Molecule Discussions <https://github.com/ansible-community/molecule/discussions>`_ is designed to aid with the development and testing of Ansible roles with Molecule.
To subscribe to a group from a non-Google account, you can send an email to the subscription address requesting the subscription. For example: ``ansible-devel+subscribe@googlegroups.com``
The Ansible mailing lists are hosted on Google, but you do not need a Google account to subscribe. To subscribe to a group from a non-Google account, send an email to the subscription address requesting the subscription. For example: ``ansible-devel+subscribe@googlegroups.com``.
.._communication_irc:
IRC channels
============
Real-time chat
==============
For real-time interactions, conversations in the Ansible community happen over two chat protocols: Matrix and IRC. We maintain a bridge between Matrix and IRC, so you can choose whichever protocol you prefer. All channels exist in both places. Join a channel any time to ask questions, participate in a Working Group meeting, or just say hello.
Ansible community on Matrix
---------------------------
The Ansible community maintains its own Matrix homeserver at ``ansible.im``. To join the community using Matrix, you need two things:
* a Matrix account (from matrix.org or any other Matrix homeserver)
* a `Matrix client <https://matrix.org/clients/>`_ (we recommend `Element Webchat <https://app.element.io>`_)
Matrix chat supports:
Ansible has several IRC channels on `irc.libera.chat <https://libera.chat/>`_.
* persistence (when you log on, you see all messages since you last logged off)
* edits (so you can fix your typos)
* replies to individual users
* reactions/emojis
* bridging to IRC
* no line limits
* images
Our IRC channels may require you to register your nickname. If you receive an error when you connect, see `libera.chat's Nickname Registration guide <https://libera.chat/guides/registration>`_ for instructions.
Ansible community on IRC
------------------------
To find all ``ansible`` specific channels on the libera.chat network, use the following command in your IRC client::
The Ansible community maintains several IRC channels on `irc.libera.chat <https://libera.chat/>`_. To join the community using IRC, you need one thing:
* an IRC client
IRC chat supports:
* no persistence (you only see messages when you are logged on, unless you add a bouncer)
* simple text interface
* bridging from Matrix
Our IRC channels may require you to register your IRC nickname. If you receive an error when you connect, see `libera.chat's Nickname Registration guide <https://libera.chat/guides/registration>`_ for instructions. To find all ``ansible`` specific channels on the libera.chat network, use the following command in your IRC client::
/msg alis LIST #ansible* -min 5
@ -55,7 +86,7 @@ General channels
Working groups
--------------
Many of our community `Working Groups <https://github.com/ansible/community/wiki#working-groups>`_ meet on libera.chat IRC channels. If you want to get involved in a working group, join the channel where it meets or comment on the agenda.
Many of our community `Working Groups <https://github.com/ansible/community/wiki#working-groups>`_ meet in chat. If you want to get involved in a working group, join the Matrix room or IRC channel where it meets or comment on the agenda.
- `Amazon (AWS) Working Group <https://github.com/ansible/community/wiki/AWS>`_ - ``#ansible-aws``
- `Ansible Lockdown Working Group <https://github.com/ansible/community/wiki/Lockdown>`_ | `gh/ansible/ansible-lockdown <https://github.com/ansible/ansible-lockdown>`_ - ``#ansible-lockdown``- Security playbooks/roles
@ -90,19 +121,17 @@ Regional and Language-specific channels
- ``#ansible-fr`` - Channel for French speaking Ansible community.
- ``#ansiblezh`` - Channel for Zurich/Swiss Ansible community.
IRC meetings
------------
Meetings on chat
----------------
The Ansible community holds regular IRC meetings on various topics, and anyone who is interested is invited to
participate. For more information about Ansible meetings, consult the `meeting schedule and agenda page <https://github.com/ansible/community/blob/master/meetings/README.md>`_.
The Ansible community holds regular meetings on various topics on Matrix/IRC, and anyone who is interested is invited to participate. For more information about Ansible meetings, consult the `meeting schedule and agenda page <https://github.com/ansible/community/blob/master/meetings/README.md>`_.
Ansible Automation Platform support questions
=============================================
Red Hat Ansible `Automation Platform <https://www.ansible.com/products/automation-platform>`_ is a subscription that contains support, certified content, and tooling for Ansible including
content management, a controller, UI and REST API.
Red Hat Ansible `Automation Platform <https://www.ansible.com/products/automation-platform>`_ is a subscription that contains support, certified content, and tooling for Ansible including content management, a controller, UI and REST API.
If you have a question about Ansible Automation Platform, visit `Red Hat support <https://access.redhat.com/products/red-hat-ansible-automation-platform/>`_ rather than using the IRC channel or the general project mailing list.
If you have a question about Ansible Automation Platform, visit `Red Hat support <https://access.redhat.com/products/red-hat-ansible-automation-platform/>`_ rather than using a chat channel or the general project mailing list.
The Bullhorn
============
@ -113,4 +142,3 @@ If you have any questions or content you would like to share, please reach out t
Read past issues `here <https://github.com/ansible/community/wiki/News>`_.
`Subscribe <https://eepurl.com/gZmiEP>`_ to receive it.
@ -213,7 +213,7 @@ Unfortunately, leftover rST-files from previous document-generating can occasion
Joining the documentation working group
=======================================
The Documentation Working Group (DaWGs) meets weekly on Tuesdays on the #ansible-docs channel on the `libera.chat IRC network<https://libera.chat/>`_. For more information, including links to our agenda and a calendar invite, please visit the `working group page in the community repo <https://github.com/ansible/community/wiki/Docs>`_.
The Documentation Working Group (DaWGs) meets weekly on Tuesdays in the Docs chat (using `Matrix <https://matrix.to/#/#docs:ansible.im>`_ or using IRC at `irc.libera.chat<https://libera.chat/>`_). For more information, including links to our agenda and a calendar invite, please visit the `working group page in the community repo <https://github.com/ansible/community/wiki/Docs>`_.
..seealso::
:ref:`More about testing module documentation <testing_module_documentation>`
@ -20,9 +20,9 @@ Ansible practices responsible disclosure - if this is a security-related bug, em
Bugs in ansible-core
--------------------
If you find a bug that affects multiple plugins, a plugin that remained in the ansible/ansible repo, or the overall functioning of Ansible, report it to `github.com/ansible/ansible/issues <https://github.com/ansible/ansible/issues>`_. You need a free GitHub account. Before reporting a bug, use the bug/issue search to see if the issue has already been reported. If you are not sure if something is a bug yet, you can report the behavior on the :ref:`mailing list or IRC first <communication>`.
If you find a bug that affects multiple plugins, a plugin that remained in the ansible/ansible repo, or the overall functioning of Ansible, report it to `github.com/ansible/ansible/issues <https://github.com/ansible/ansible/issues>`_. You need a free GitHub account. Before reporting a bug, use the bug/issue search to see if the issue has already been reported. If you are not sure if something is a bug yet, you can report the behavior on the :ref:`mailing list or community chat first <communication>`.
Do not open issues for "how do I do this" type questions. These are great topics for IRC or the mailing list, where things are likely to be more of a discussion.
Do not open issues for "how do I do this" type questions. These are great topics for community chat channels or a mailing list, where things are likely to be more of a discussion.
If you find a bug, open the issue yourself to ensure we have a record of it. Do not rely on someone else in the community to file the bug report for you. We have created an issue template, which saves time and helps us help everyone with their issues more quickly. Please fill it out as completely and as accurately as possible:
@ -48,7 +48,7 @@ Many bugs only affect a single module or plugin. If you find a bug that affects
#. Click on the Issue Tracker link for that collection.
#. Follow the contributor guidelines or instructions in the collection repo.
If you are not sure whether a bug is in ansible-core or in a collection, you can report the behavior on the :ref:`mailing list or IRC first <communication>`.
If you are not sure whether a bug is in ansible-core or in a collection, you can report the behavior on the :ref:`mailing list or community chat channel first <communication>`.
@ -31,7 +31,7 @@ To contribute a module to most Ansible collections, you must:
Additional requirements may apply for certain collections. Review the individual collection repositories for more information.
Please make sure your module meets these requirements before you submit your PR/proposal. If you have questions, reach out via ``#ansible-devel``, Ansible's IRC chat channel on `irc.libera.chat <https://libera.chat>`_ or the `Ansible development mailing list <https://groups.google.com/group/ansible-devel>`_.
Please make sure your module meets these requirements before you submit your PR/proposal. If you have questions, reach out via the ``#ansible-devel`` chat channel (using Matrix at ansible.im or using IRC at`irc.libera.chat <https://libera.chat>`_) or the `Ansible development mailing list <https://groups.google.com/group/ansible-devel>`_.
@ -218,13 +218,11 @@ The :ref:`Community Guide <ansible_community_guide>` covers how to open a pull r
Communication and development support
=====================================
Join the IRC channel ``#ansible-devel`` on `irc.libera.chat <https://libera.chat/>`_ for
discussions surrounding Ansible development.
Join the ``#ansible-devel`` chat channel (using Matrix at ansible.im or using IRC at `irc.libera.chat <https://libera.chat/>`_) for discussions surrounding Ansible development.
For questions and discussions pertaining to using the Ansible product,
use the ``#ansible`` channel.
For questions and discussions pertaining to using the Ansible product, join the ``#ansible`` channel.
For more specific IRC channels look at :ref:`Community Guide, Communicating <communication_irc>`.
To find other topic-specific chat channels, look at :ref:`Community Guide, Communicating <communication_irc>`.
@ -690,8 +690,7 @@ idempotent and does not report changes. For example:
Windows communication and development support
=============================================
Join the ``#ansible-devel`` or ``#ansible-windows`` irc channels on `irc.libera.chat
<https://libera.chat/>`_ for discussions about Ansible development for Windows.
Join the ``#ansible-devel`` or ``#ansible-windows`` chat channels (using Matrix at ansible.im or using IRC at `irc.libera.chat <https://libera.chat/>`_) for discussions about Ansible development for Windows.
For questions and discussions pertaining to using the Ansible product,
@ -55,8 +55,8 @@ Ansible has a thriving and knowledgeable community of module developers that is
In the :ref:`ansible_community_guide` you can find how to:
* Subscribe to the Mailing Lists - We suggest "Ansible Development List" and "Ansible Announce list"
* ``#ansible-devel`` - We have found that communicating on the IRC channel, ``#ansible-devel`` on `libera.chat's<https://libera.chat/>`_ IRC network works best for developers so we can have an interactive dialogue.
* IRC meetings - Join the various weekly IRC meetings `meeting schedule and agenda page <https://github.com/ansible/community/blob/master/meetings/README.md>`_
* ``#ansible-devel`` - We have found that communicating on the ``#ansible-devel``chat channel (using Matrix at ansible.im or using IRC at`irc.libera.chat <https://libera.chat/>`_) works best for developers so we can have an interactive dialogue.
* Working group and other chat channel meetings - Join the various weekly meetings `meeting schedule and agenda page <https://github.com/ansible/community/blob/master/meetings/README.md>`_
Required files
==============
@ -70,7 +70,7 @@ Your collection should include the following files to be usable:
When you have these files ready, review the :ref:`developing_modules_checklist` again. If you are creating a new collection, you are responsible for all procedures related to your repository, including setting rules for contributions, finding reviewers, and testing and maintaining the code in your collection.
If you need help or advice, consider joining the ``#ansible-devel``IRC channel (see how in the :ref:`Where to get support <developing_in_groups_support>` section).
If you need help or advice, consider joining the ``#ansible-devel``chat channel (using Matrix at ansible.im or using IRC at `irc.libera.chat <https://libera.chat/>`_). For more information, see :ref:`developing_in_groups_support` and :ref:`communication`.
@ -75,7 +75,7 @@ You should check in on the status of your PR after tests have completed to see i
Getting help rebasing
=====================
For help with rebasing your PR, or other development related questions, join us on our #ansible-devel IRC chat channel on`irc.libera.chat <https://libera.chat/>`_.
For help with rebasing your PR, or other development related questions, join us on the #ansible-devel chat channel (using Matrix at ansible.im or using IRC at`irc.libera.chat <https://libera.chat/>`_).
- Re-read the AWS documentation, especially the list of `Actions, Resources and Condition Keys <https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_actions-resources-contextkeys.html>`_ for the various AWS services.
- Look at the `cloudonaut <https://iam.cloudonaut.io>`_ documentation as a troubleshooting cross-reference.
- Use a search engine.
- Ask in the Ansible IRC channel #ansible-aws (on`irc.libera.chat <https://libera.chat>`_).
- Ask in the #ansible-aws chat channel (using Matrix at ansible.im or using IRC at`irc.libera.chat <https://libera.chat/>`_).
@ -96,7 +96,7 @@ If either of these issues appear to be the case, you can rerun the Azure Pipelin
* closing and re-opening the PR (full rebuild)
* making another change to the PR and pushing to GitHub
If the issue persists, please contact us in the ``#ansible-devel``irc channel on the`irc.libera.chat <https://libera.chat/>`_ IRC network.
If the issue persists, please contact us in the ``#ansible-devel`` chat channel (using Matrix at ansible.im or usingIRC at `irc.libera.chat <https://libera.chat/>`_).
@ -180,4 +180,4 @@ Each issue will be assigned to one of the following projects:
Questions
---------
For questions about integration tests reach out to @mattclay or @gundalow on GitHub or ``#ansible-devel`` on IRC.
For questions about integration tests reach out to @mattclay or @gundalow on GitHub or the ``#ansible-devel``chat channel (using Matrix at ansible.im or using IRC at `irc.libera.chat <https://libera.chat/>`_).
@ -18,7 +18,7 @@ The document doesn't apply to other parts of Ansible for which the recommendatio
normally closer to the Python standard. There is basic documentation for Ansible unit
tests in the developer guide :ref:`testing_units`. This document should
be readable for a new Ansible module author. If you find it incomplete or confusing,
please open a bug or ask for help on Ansible IRC.
please open a bug or ask for help on the #ansible-devel chat channel (using Matrix at ansible.im or using IRC at `irc.libera.chat <https://libera.chat/>`_).
What Are Unit Tests?
====================
@ -269,8 +269,8 @@ Ansible special cases for unit testing
There are a number of special cases for unit testing the environment of an Ansible module.
The most common are documented below, and suggestions for others can be found by looking
at the source code of the existing unit tests or asking on the Ansible IRC channel or mailing
lists.
at the source code of the existing unit tests or asking on the Ansible chat channel or mailing
lists. For more infomration on joining chat channels and subscribing to mailing lists, see :ref:`communication`.
If you need additional help or feedback, reach out in the ``#ansible-network`` chat channel (using Matrix at ansible.im or using IRC at `irc.libera.chat <https://libera.chat/>`_).
* the ``#ansible-network`` channel (using Matrix at ansible.im or using IRC at`irc.libera.chat <https://libera.chat/>`_)
* `Join Ansible Network Slack <https://join.slack.com/t/ansiblenetwork/shared_invite/zt-3zeqmhhx-zuID9uJqbbpZ2KdVeTwvzw>`_ - Network & Security Automation Slack community. Check out the #devel channel for discussions on module and plugin development.
* `Ansible Network Slack <https://join.slack.com/t/ansiblenetwork/shared_invite/zt-3zeqmhhx-zuID9uJqbbpZ2KdVeTwvzw>`_ - Network & Security Automation Slack community. Check out the #devel channel for discussions on module and plugin development.
@ -21,7 +21,7 @@ In July, 2019, we announced that collections would be the `future of Ansible con
Where did this specific module go?
++++++++++++++++++++++++++++++++++
IF you are searching for a specific module, you can check the `runtime.yml <https://github.com/ansible/ansible/blob/devel/lib/ansible/config/ansible_builtin_runtime.yml>`_ file, which lists the first destination for each module that we extracted from the main ansible/ansible repository. Some modules have moved again since then. You can also search on `Ansible Galaxy <https://galaxy.ansible.com/>`_ or ask on one of our :ref:`IRC channels <communication_irc>`.
IF you are searching for a specific module, you can check the `runtime.yml <https://github.com/ansible/ansible/blob/devel/lib/ansible/config/ansible_builtin_runtime.yml>`_ file, which lists the first destination for each module that we extracted from the main ansible/ansible repository. Some modules have moved again since then. You can also search on `Ansible Galaxy <https://galaxy.ansible.com/>`_ or ask on one of our :ref:`chat channels <communication_irc>`.
.._set_environment:
@ -806,7 +806,7 @@ for contributing can be found in the docs README `viewable on GitHub <https://gi
I don't see my question here
++++++++++++++++++++++++++++
Please see the section below for a link to IRC and the Google Group, where you can ask your question there.
If you have not found an answer to your questions, you can ask on one of our mailing lists or chat channels. For instructions on subscribing to a list or joining a chat channel, see :ref:`communication`.
..seealso::
@ -816,5 +816,3 @@ Please see the section below for a link to IRC and the Google Group, where you c
Tips and tricks for playbooks
`User Mailing List <https://groups.google.com/group/ansible-project>`_
- 2020-09-15: ansible-2.10.0 rc1 and final freeze.
- After this date only changes blocking a release are accepted.
- Collections will only be updated to a new version if a blocker is approved. Collection owners should discuss any blockers at the community IRC meeting (on 9-17) to decide whether to bump the version of the collection for a fix. See the `Community IRC meeting agenda <https://github.com/ansible/community/issues/539>`_.
- Collections will only be updated to a new version if a blocker is approved. Collection owners should discuss any blockers at the community meeting (on 9-17) to decide whether to bump the version of the collection for a fix. See the `Community meeting agenda <https://github.com/ansible/community/issues/539>`_.
** Additional release candidates to be published as needed as blockers are fixed **
@ -48,4 +48,4 @@ Ansible-2.10.x patch releases will occur roughly every three weeks if changes to
Breaking changes may be introduced in ansible-3.0 although we encourage collection owners to use deprecation periods that will show up in at least one Ansible release before being changed incompatibly.
For more information, reach out on a mailing list or an IRC channel - see :ref:`communication` for more details.
For more information, reach out on a mailing list or a chat channel - see :ref:`communication` for more details.
..[1] No new modules or major features accepted after this date. In practice this means we will freeze the semver collection versions to compatible release versions. For example, if the version of community.crypto on this date was community-crypto-2.1.0; ansible-3.0.0 could ship with community-crypto-2.1.1. It would not ship with community-crypto-2.2.0.
..[2] After this date only changes blocking a release are accepted. Accepted changes require creating a new rc and may slip the final release date.
..[3] Collections will only be updated to a new version if a blocker is approved. Collection owners should discuss any blockers at a community IRC meeting (before this freeze) to decide whether to bump the version of the collection for a fix. See the `Community IRC meeting agenda <https://github.com/ansible/community/issues/539>`_.
..[3] Collections will only be updated to a new version if a blocker is approved. Collection owners should discuss any blockers at a community meeting (before this freeze) to decide whether to bump the version of the collection for a fix. See the `Community meeting agenda <https://github.com/ansible/community/issues/539>`_.
..note::
@ -49,7 +49,7 @@ Ansible 3.x.x minor releases will occur approximately every three weeks if chang
Minor releases will stop when :ref:`Ansible-4 <ansible_4_roadmap>` is released. See the :ref:`Release and Maintenance Page <release_and_maintenance>` for more information.
For more information, reach out on a mailing list or an IRC channel - see :ref:`communication` for more details.
For more information, reach out on a mailing list or a chat channel - see :ref:`communication` for more details.
:2021-04-13:Last day for new collections to be submitted for inclusion in Ansible 4. Note that collections MUST be reviewed and approved before being included. There is no guarantee that we will review every collection. The earlier your collection is submitted, the more likely it will be that your collection will be reviewed and the necessary feedback can be addressed in time for inclusion.
:2021-04-13:Ansible-4.0.0 alpha4
:2021-04-14:Community IRC Meeting topic: list any new collection reviews which block release. List any backwards incompatible collection releases that beta1 should try to accommodate.
:2021-04-21:Community IRC Meeting topic: Decide what contingencies to activate for any blockers that do not meet the deadline.
:2021-04-14:Community Meeting topic: list any new collection reviews which block release. List any backwards incompatible collection releases that beta1 should try to accommodate.
:2021-04-21:Community Meeting topic: Decide what contingencies to activate for any blockers that do not meet the deadline.
:2021-04-26:Last day for new collections to be **reviewed and approved** for inclusion in Ansible 4.
:2021-04-26:Last day for collections to make backwards incompatible releases that will be accepted into Ansible 4.
:2021-04-27:Ansible-4.0.0 beta1 -- feature freeze [1]_ (weekly beta releases. Collection owners and interested users should test for bugs).
@ -33,7 +33,7 @@ Release schedule
..[1] No new modules or major features accepted after this date. In practice, this means we will freeze the semver collection versions to compatible release versions. For example, if the version of community.crypto on this date was community-crypto-2.1.0; ansible-3.0.0 could ship with community-crypto-2.1.1. It would not ship with community-crypto-2.2.0.
..[2] After this date only changes blocking a release are accepted. Accepted changes require creating a new rc and may slip the final release date.
..[3] Collections will only be updated to a new version if a blocker is approved. Collection owners should discuss any blockers at a community IRC meeting (before this freeze) to decide whether to bump the version of the collection for a fix. See the `Community IRC meeting agenda <https://github.com/ansible/community/issues/539>`_.
..[3] Collections will only be updated to a new version if a blocker is approved. Collection owners should discuss any blockers at a Community meeting (before this freeze) to decide whether to bump the version of the collection for a fix. See the `Community meeting agenda <https://github.com/ansible/community/issues/539>`_.
..note::
@ -52,4 +52,4 @@ Ansible 4.x minor releases will occur approximately every three weeks if changes
Minor releases will stop when Ansible-5 is released. See the :ref:`Release and Maintenance Page <release_and_maintenance>` for more information.
For more information, reach out on a mailing list or an IRC channel - see :ref:`communication` for more details.
For more information, reach out on a mailing list or a chat channel - see :ref:`communication` for more details.
:2021-10-12:Last day for new collections to be submitted for inclusion in Ansible-5. Collections MUST be reviewed and approved before being included. There is no guarantee that we will review every collection. The earlier your collection is submitted, the more likely it will be that your collection will be reviewed and the necessary feedback can be addressed in time for inclusion.
:2021-10-13:Community IRC Meeting topic: List any new collection reviews which block release. List any backwards incompatible collection releases that beta1 should try to accommodate.
:2021-10-13:Community Meeting topic: List any new collection reviews which block release. List any backwards incompatible collection releases that beta1 should try to accommodate.
:2021-10-19:Ansible-5.0.0 alpha3.
:2021-10-20:Community IRC Meeting topic: Decide what contingencies to activate for any blockers that do not meet the deadline.
:2021-10-20:Community Meeting topic: Decide what contingencies to activate for any blockers that do not meet the deadline.
:2021-10-25:Last day for new collections to be **reviewed and approved** for inclusion in Ansible-5.
:2021-10-25:Last day for collections to make backwards incompatible releases that will be accepted into Ansible-5.
:2021-10-26:Create the ansible-build-data directory and files for Ansible-6; new collection approvals will target this.
@ -54,4 +54,4 @@ Ansible 5.x minor releases will occur approximately every three weeks if changes
Minor releases will stop when Ansible-6 is released. See the :ref:`Release and Maintenance Page <release_and_maintenance>` for more information.
For more information, reach out on a mailing list or an IRC channel - see :ref:`communication` for more details.
For more information, reach out on a mailing list or a chat channel - see :ref:`communication` for more details.
If you have specific issues with the ACI modules, or a feature request, or you like to contribute to the ACI project by proposing changes or documentation updates, look at the Ansible Community wiki ACI page at: https://github.com/ansible/community/wiki/Network:-ACI
You will find our roadmap, an overview of open ACI issues and pull-requests, and more information about who we are. If you have an interest in using ACI with Ansible, feel free to join! We occasionally meet online to track progress and prepare for new Ansible releases.
You will find our roadmap, an overview of open ACI issues and pull-requests, and more information about who we are. If you have an interest in using ACI with Ansible, feel free to join! We occasionally meet online (on the #ansible-network chat channel, using Matrix at ansible.im or using IRC at `irc.libera.chat <https://libera.chat/>`_) to track progress and prepare for new Ansible releases.
..seealso::
@ -655,7 +655,5 @@ You will find our roadmap, an overview of open ACI issues and pull-requests, and
A detailed guide on how to use Ansible for automating network infrastructure.
`Network Working Group <https://github.com/ansible/community/tree/master/group-network>`_
The Ansible Network community page, includes contact information and meeting information.
``#ansible-network`` on `irc.libera.chat <https://libera.chat/>`_
The #ansible-network IRC chat channel on libera.chat.
`User Mailing List <https://groups.google.com/group/ansible-project>`_
@ -47,7 +47,7 @@ If you find a bug that affects a plugin in a Galaxy collection:
Some partner collections may be hosted in private repositories.
If you are not sure whether the behavior you see is a bug, if you have questions, if you want to discuss development-oriented topics, or if you just want to get in touch, use one of our Google groups or IRC channels to :ref:`communicate with Ansiblers <communication>`.
If you are not sure whether the behavior you see is a bug, if you have questions, if you want to discuss development-oriented topics, or if you just want to get in touch, use one of our Google mailing lists or chat channels (using Matrix at ansible.im or using IRC at `irc.libera.chat <https://libera.chat/>`_) to :ref:`communicate with Ansiblers <communication>`.
If you find a bug that affects a module in an Automation Hub collection:
@ -66,5 +66,5 @@ All plugins that remain in ``ansible-core`` and all collections hosted in Automa
Examples of using modules with /usr/bin/ansible-playbook
`Mailing List <https://groups.google.com/group/ansible-project>`_
Questions? Help? Ideas? Stop by the list on Google Groups
Alicia Cozine
3 years ago
committed by