Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Due to the takeover of freenode we're moving to a different irc network. #74775

Merged
merged 4 commits into from
Jun 1, 2021

Conversation

abadger
Copy link
Contributor

@abadger abadger commented May 20, 2021

  • Our channels updated to point at the same channel name on libera.chat
  • Some links went to webchat.freenode.net. At this time, libera.chat
    doesn't point you to an official webchat client so I changed these to
    https://libera.chat. (kiwi irc does work with libera.chat so that
    could be another option).
  • In general, I used the name irc.libera.net for link names and
    https://libera.chat for link targets. This is because the irc service
    is hosted on irc.libera.chat but the project web server is hosted on
    libera.chat. (This appears to also be true for freenode but we were
    using http://irc.freenode.net which doesn't seem to work. Oops).
  • Removed http://irc.freenode.net from the linkcheck exceptions.
    linkcheck was actually correct to flag that as invalid (should have
    been http://frenode.net instead).
ISSUE TYPE
  • Docs Pull Request
COMPONENT NAME
ADDITIONAL INFORMATION

Do not merge until the Steering Committee decides whether we're actually moving to libera.net or to another irc service (oftc.net is the leading alternative at this point).

\CC @acozine @samccann @gundalow @felixfontein

* Our channels updated to point at the same channel name on libera.chat
* Some links went to webchat.freenode.net.  At this time, libera.chat
  doesn't point you to an official webchat client so I changed these to
  https://libera.chat. (kiwi irc does work with libera.chat so that
  could be another option).
* In general, I used the name irc.libera.net for link names and
  https://libera.chat for link targets.  This is because the irc service
  is hosted on irc.libera.chat but the project web server is hosted on
  libera.chat.  (This appears to also be true for freenode but we were
  using http://irc.freenode.net which doesn't seem to work.  Oops).
* Removed http://irc.freenode.net from the linkcheck exceptions.
  linkcheck was actually correct to flag that as invalid (should have
  been http://frenode.net instead).
@ansibot
Copy link
Contributor

ansibot commented May 20, 2021

@abadger This PR was evaluated as a potentially problematic PR for the following reasons:

  • More than 50 changed files.

Such PR can only be merged by human. Contact a Core team member to review this PR on IRC: #ansible-devel on irc.freenode.net

click here for bot help

@ansibot ansibot added WIP This issue/PR is a work in progress. Nevertheless it was shared for getting input from peers. affects_2.12 docs This issue/PR relates to or includes documentation. needs_rebase https://docs.ansible.com/ansible/devel/dev_guide/developing_rebasing.html needs_triage Needs a first human triage before being processed. labels May 20, 2021
@abadger
Copy link
Contributor Author

abadger commented May 20, 2021

Since I was editing all the files, I also compiled a list of what pages were pointing to which channels. I'll include it below. There's some things that are surprising to me. For instance, the dev_guide pages pointing to #ansible instead of #ansible-devel. Maybe more things should point to #ansible-community. Th aws scenario guide should maybe point at #ansible-aws in addition to #ansible.

#ansible

  • community/communication.rst
  • dev_guide/developing_modules_general_windows.rst
  • dev_guide/developing_modules.rst
  • dev_guide/developing_modules_general.rst
  • dev_guide/developing_plugins.rst
  • dev_guide/developing_api.rst
  • dev_guide/developing_collections.rst
  • dev_guide/developing_collections_contributing.rst
  • dev_guide/developing_collections_creating.rst
  • dev_guide/developing_collections_distributing.rst
  • dev_guide/developing_collections_migrating.rst
  • dev_guide/developing_collections_shared.rst
  • dev_guide/developing_inventory.rst
  • dev_guide/developing_collections_testing.rst
  • galaxy/dev_guide.rst
  • dev_guide/developing_collections_changelogs.rst
  • dev_guide/developing_collections_structure.rst
  • plugins/action.rst
  • plugins/become.rst
  • plugins/cache.rst
  • plugins/callback.rst
  • plugins/connection.rst
  • plugins/inventory.rst
  • plugins/plugins.rst
  • plugins/shell.rst
  • plugins/strategy.rst
  • plugins/vars.rst
  • plugins/lookup.rst
  • reference_appendices/YAMLSyntax.rst
  • reference_appendices/common_return_values.rst
  • reference_appendices/glossary.rst
  • reference_appendices/test_strategies.rst
  • reference_appendices/faq.rst
  • reference_appendices/release_and_maintenance.rst
  • scenario_guides/guide_aws.rst
  • user_guide/become.rst
  • user_guide/intro_adhoc.rst
  • user_guide/intro_bsd.rst
  • user_guide/intro_dynamic_inventory.rst
  • user_guide/modules_support.rst
  • user_guide/playbooks_advanced_syntax.rst
  • user_guide/playbooks_async.rst
  • user_guide/playbooks_blocks.rst
  • user_guide/playbooks_debugger.rst
  • user_guide/playbooks_error_handling.rst
  • user_guide/modules.rst
  • user_guide/modules_intro.rst
  • user_guide/intro_patterns.rst
  • user_guide/playbooks_environment.rst
  • user_guide/playbooks_lookups.rst
  • user_guide/playbooks_filters_ipaddr.rst
  • user_guide/playbooks_loops.rst
  • user_guide/playbooks_prompts.rst
  • user_guide/playbooks_strategies.rst
  • user_guide/windows_faq.rst
  • user_guide/windows_dsc.rst
  • user_guide/windows_setup.rst
  • user_guide/windows_usage.rst
  • user_guide/windows_winrm.rst
  • user_guide/collections_using.rst
  • user_guide/playbooks_tags.rst
  • user_guide/playbooks_variables.rst
  • user_guide/playbooks_templating.rst
  • user_guide/intro_getting_started.rst
  • user_guide/playbooks_delegation.rst
  • user_guide/playbooks_conditionals.rst
  • user_guide/playbooks_tests.rst
  • user_guide/playbooks_filters.rst
  • user_guide/intro_inventory.rst
  • docs/templates/collections_galaxy_meta.rst.j2
  • hacking/ticket_stubs/bug_is_really_a_question.md
  • hacking/ticket_stubs/collections.md

#ansible-aws

  • community/communication.rst
  • dev_guide/platforms/aws_guidelines.rst

#ansible-awx

  • community/communication.rst

#ansible-azure

  • community/communication.rst

#ansible-community

  • community/communication.rst
  • roadmap/ansible_roadmap_index.rst

#ansible-container

  • community/communication.rst

#ansible-devel

  • community/communication.rst
  • dev_guide/style_guide/resources.rst
  • dev_guide/developing_modules_checklist.rst
  • dev_guide/developing_modules_in_groups.rst
  • dev_guide/developing_core.rst
  • dev_guide/developing_modules_general_windows.rst
  • dev_guide/developing_rebasing.rst
  • dev_guide/developing_modules_general.rst
  • dev_guide/testing.rst
  • roadmap/ansible_core_roadmap_index.rst
  • hacking/ticket_stubs/proposal.md
  • dev_guide/developing_core.rst

#ansible-digitalocean

  • community/communication.rst

#ansible-docs

  • community/documentation_contributions.rst
  • community/communication.rst
  • dev_guide/style_guide/index.rst
  • docs/docsite/README.md

#ansible-es

  • community/communication.rst

#ansible-eu

  • community/communication.rst

#ansible-fr

  • community/communication.rst

#ansiblezh

  • community/communication.rst

#ansible-galaxy

  • community/communication.rst

#ansible-jboss

  • community/communication.rst

#ansible-lightbulb

  • community/communication.rst

#ansible-linode

  • community/communication.rst

#ansible-lockdown

  • community/communication.rst

#ansible-meeting

  • community/communication.rst

#ansible-molecule

  • community/communication.rst

#ansible-network

  • community/communication.rst
  • network/dev_guide/developing_resource_modules_network.rst
  • network/getting_started/network_resources.rst
  • plugins/cliconf.rst
  • plugins/httpapi.rst
  • plugins/netconf.rst
  • scenario_guides/guide_aci.rst

#ansible-vmware

  • community/communication.rst

#ansible-windows

  • community/communication.rst
  • dev_guide/developing_modules_general_windows.rst

#yaml -- which we do not control -- left it as freenode

  • reference_appendices/YAMLSyntax.rst

@gundalow gundalow self-requested a review May 20, 2021 15:36
@gundalow gundalow self-assigned this May 20, 2021
@samdoran samdoran removed the needs_triage Needs a first human triage before being processed. label May 20, 2021
@abadger abadger changed the title [WIP] Due to the takeover of freenode we're moving to a different irc network. Due to the takeover of freenode we're moving to a different irc network. May 26, 2021
@abadger
Copy link
Contributor Author

abadger commented May 26, 2021

At today's IRC meeting, it was decided that we're moving to libera.chat. This is now ready for review.

@ansibot ansibot added core_review In order to be merged, this PR must follow the core review workflow. needs_revision This PR fails CI tests or a maintainer has requested a review/revision of the PR. and removed WIP This issue/PR is a work in progress. Nevertheless it was shared for getting input from peers. labels May 26, 2021
@@ -68,7 +68,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 join the ``#ansible-devel`` IRC channel (see how in the "Where to get support").
If you need help or advice, consider joining the ``#ansible-devel`` IRC channel (see how in the "Where to get support").
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you need help or advice, consider joining the ``#ansible-devel`` IRC channel (see how in the "Where to get support").
If you need help or advice, consider joining the ``#ansible-devel`` IRC channel (see how in the "Where to get support").

While here, would be nice to add a reference to the "Where to get support" section

Comment on lines 236 to 238
`irc.libera.chat <https://libera.chat/>`_
#ansible IRC chat channel
`irc.freenode.net <https://freenode.net/>`_
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
`irc.libera.chat <https://libera.chat/>`_
#ansible IRC chat channel
`irc.freenode.net <https://freenode.net/>`_
#ansible IRC chat channel
`irc.libera.chat <https://libera.chat/>`_

or something

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmmm..... they weren't ready to decide whether to move over to libera.chat when I spoke to them last but it looks like all the important people are there now.

@@ -736,8 +736,8 @@ the filter ``slaac()`` generates an IPv6 address for a given network and a MAC A
:ref:`playbooks_reuse_roles`
Playbook organization by roles
:ref:`playbooks_best_practices`
Tips and tricks for playbooks
Tips and tricks for playbooks
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't there be one less space, than one more space here?

Add a link target and then link to where contributors should get support
for developing groups of modules.
@ansibot ansibot added ci_verified Changes made in this PR are causing tests to fail. and removed core_review In order to be merged, this PR must follow the core review workflow. labels May 27, 2021
Copy link
Contributor

@gundalow gundalow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for doing this Toshio, many more references than I thought. How about

  1. merge (and backport this)
  2. once the Matrix bridge is up we tidy up communication.rst and review the links (dev_guide points to Ansible rather than ansible-devel)

Co-authored-by: Felix Fontein <felix@fontein.de>
@ansibot ansibot removed the ci_verified Changes made in this PR are causing tests to fail. label Jun 1, 2021
@ansibot ansibot added the core_review In order to be merged, this PR must follow the core review workflow. label Jun 1, 2021
@gundalow gundalow merged commit 80e7e1a into ansible:devel Jun 1, 2021
@abadger abadger deleted the move-to-libera.chat branch June 1, 2021 16:18
Andersson007 pushed a commit to Andersson007/ansible that referenced this pull request Jun 11, 2021
…rk. (ansible#74775)

* Due to the takeover of freenode we're moving to a different irc network.

* Our channels updated to point at the same channel name on libera.chat
* Some links went to webchat.freenode.net.  At this time, libera.chat
  doesn't point you to an official webchat client so I changed these to
  https://libera.chat. (kiwi irc does work with libera.chat so that
  could be another option).
* In general, I used the name irc.libera.net for link names and
  https://libera.chat for link targets.  This is because the irc service
  is hosted on irc.libera.chat but the project web server is hosted on
  libera.chat.  (This appears to also be true for freenode but we were
  using http://irc.freenode.net which doesn't seem to work.  Oops).
* Removed http://irc.freenode.net from the linkcheck exceptions.
  linkcheck was actually correct to flag that as invalid (should have
  been http://frenode.net instead).

* Looks like hte important people in #yaml are now in libera.chat

* Link to where contributors should get help

Add a link target and then link to where contributors should get support
for developing groups of modules.

* Update docs/docsite/rst/dev_guide/developing_modules_in_groups.rst

Co-authored-by: Felix Fontein <felix@fontein.de>

Co-authored-by: John R Barker <john@johnrbarker.com>
Co-authored-by: Felix Fontein <felix@fontein.de>
(cherry picked from commit 80e7e1a)
acozine pushed a commit that referenced this pull request Jun 14, 2021
…rk. (#74775) (#74968)

* Updates our channels to point at the same channel name on libera.chat
* Links that used to point to webchat.freenode.net now point to https://libera.chat
* Removes http://irc.freenode.net from the linkcheck exceptions.
* Updates docs/docsite/rst/dev_guide/developing_modules_in_groups.rst

(cherry picked from commit 80e7e1a)

Co-authored-by: John R Barker <john@johnrbarker.com>
Co-authored-by: Felix Fontein <felix@fontein.de>
Co-authored-by: Toshio Kuratomi <a.badger@gmail.com>
Andersson007 pushed a commit to Andersson007/ansible that referenced this pull request Jun 15, 2021
…rk. (ansible#74775)

* Due to the takeover of freenode we're moving to a different irc network.

* Our channels updated to point at the same channel name on libera.chat
* Some links went to webchat.freenode.net.  At this time, libera.chat
  doesn't point you to an official webchat client so I changed these to
  https://libera.chat. (kiwi irc does work with libera.chat so that
  could be another option).
* In general, I used the name irc.libera.net for link names and
  https://libera.chat for link targets.  This is because the irc service
  is hosted on irc.libera.chat but the project web server is hosted on
  libera.chat.  (This appears to also be true for freenode but we were
  using http://irc.freenode.net which doesn't seem to work.  Oops).
* Removed http://irc.freenode.net from the linkcheck exceptions.
  linkcheck was actually correct to flag that as invalid (should have
  been http://frenode.net instead).

* Looks like hte important people in #yaml are now in libera.chat

* Link to where contributors should get help

Add a link target and then link to where contributors should get support
for developing groups of modules.

* Update docs/docsite/rst/dev_guide/developing_modules_in_groups.rst

Co-authored-by: Felix Fontein <felix@fontein.de>

Co-authored-by: John R Barker <john@johnrbarker.com>
Co-authored-by: Felix Fontein <felix@fontein.de>
(cherry picked from commit 80e7e1a)
Andersson007 pushed a commit to Andersson007/ansible that referenced this pull request Jun 15, 2021
…rk. (ansible#74775)

* Due to the takeover of freenode we're moving to a different irc network.

* Our channels updated to point at the same channel name on libera.chat
* Some links went to webchat.freenode.net.  At this time, libera.chat
  doesn't point you to an official webchat client so I changed these to
  https://libera.chat. (kiwi irc does work with libera.chat so that
  could be another option).
* In general, I used the name irc.libera.net for link names and
  https://libera.chat for link targets.  This is because the irc service
  is hosted on irc.libera.chat but the project web server is hosted on
  libera.chat.  (This appears to also be true for freenode but we were
  using http://irc.freenode.net which doesn't seem to work.  Oops).
* Removed http://irc.freenode.net from the linkcheck exceptions.
  linkcheck was actually correct to flag that as invalid (should have
  been http://frenode.net instead).

* Looks like hte important people in #yaml are now in libera.chat

* Link to where contributors should get help

Add a link target and then link to where contributors should get support
for developing groups of modules.

* Update docs/docsite/rst/dev_guide/developing_modules_in_groups.rst

Co-authored-by: Felix Fontein <felix@fontein.de>

Co-authored-by: John R Barker <john@johnrbarker.com>
Co-authored-by: Felix Fontein <felix@fontein.de>
(cherry picked from commit 80e7e1a)
Andersson007 pushed a commit to Andersson007/ansible that referenced this pull request Jun 15, 2021
…rk. (ansible#74775)

* Due to the takeover of freenode we're moving to a different irc network.

* Our channels updated to point at the same channel name on libera.chat
* Some links went to webchat.freenode.net.  At this time, libera.chat
  doesn't point you to an official webchat client so I changed these to
  https://libera.chat. (kiwi irc does work with libera.chat so that
  could be another option).
* In general, I used the name irc.libera.net for link names and
  https://libera.chat for link targets.  This is because the irc service
  is hosted on irc.libera.chat but the project web server is hosted on
  libera.chat.  (This appears to also be true for freenode but we were
  using http://irc.freenode.net which doesn't seem to work.  Oops).
* Removed http://irc.freenode.net from the linkcheck exceptions.
  linkcheck was actually correct to flag that as invalid (should have
  been http://frenode.net instead).

* Looks like hte important people in #yaml are now in libera.chat

* Link to where contributors should get help

Add a link target and then link to where contributors should get support
for developing groups of modules.

* Update docs/docsite/rst/dev_guide/developing_modules_in_groups.rst

Co-authored-by: Felix Fontein <felix@fontein.de>

Co-authored-by: John R Barker <john@johnrbarker.com>
Co-authored-by: Felix Fontein <felix@fontein.de>
(cherry picked from commit 80e7e1a)
Andersson007 pushed a commit to Andersson007/ansible that referenced this pull request Jun 15, 2021
…rk. (ansible#74775)

* Due to the takeover of freenode we're moving to a different irc network.

* Our channels updated to point at the same channel name on libera.chat
* Some links went to webchat.freenode.net.  At this time, libera.chat
  doesn't point you to an official webchat client so I changed these to
  https://libera.chat. (kiwi irc does work with libera.chat so that
  could be another option).
* In general, I used the name irc.libera.net for link names and
  https://libera.chat for link targets.  This is because the irc service
  is hosted on irc.libera.chat but the project web server is hosted on
  libera.chat.  (This appears to also be true for freenode but we were
  using http://irc.freenode.net which doesn't seem to work.  Oops).
* Removed http://irc.freenode.net from the linkcheck exceptions.
  linkcheck was actually correct to flag that as invalid (should have
  been http://frenode.net instead).

* Looks like hte important people in #yaml are now in libera.chat

* Link to where contributors should get help

Add a link target and then link to where contributors should get support
for developing groups of modules.

* Update docs/docsite/rst/dev_guide/developing_modules_in_groups.rst

Co-authored-by: Felix Fontein <felix@fontein.de>

Co-authored-by: John R Barker <john@johnrbarker.com>
Co-authored-by: Felix Fontein <felix@fontein.de>
(cherry picked from commit 80e7e1a)
acozine pushed a commit that referenced this pull request Jun 23, 2021
…rk. (#74775) (#75006)

* Update channel references to point at the same channel name on libera.chat
* Update generic links to https://libera.chat
* In general, use irc.libera.net for link names/text and https://libera.chat for link targets.
  The irc service is hosted on irc.libera.chat but the project web server is hosted on
  libera.chat.
* Removed http://irc.freenode.net from the linkcheck exceptions.
* Add a link to where contributors should get support
for developing groups of modules to docs/docsite/rst/dev_guide/developing_modules_in_groups.rst

Co-authored-by: John R Barker <john@johnrbarker.com>
Co-authored-by: Felix Fontein <felix@fontein.de>
(cherry picked from commit 80e7e1a)

Co-authored-by: Toshio Kuratomi <a.badger@gmail.com>
acozine pushed a commit that referenced this pull request Jun 23, 2021
…rk. (#74775) (#75007)

* Update channel references to point at the same channel name on libera.chat
* Update generic links to https://libera.chat
* In general, use irc.libera.net for link names/text and https://libera.chat for link targets.
  The irc service is hosted on irc.libera.chat but the project web server is hosted on
  libera.chat.
* Removed http://irc.freenode.net from the linkcheck exceptions.
* Add a link to where contributors should get support
for developing groups of modules to docs/docsite/rst/dev_guide/developing_modules_in_groups.rst

Co-authored-by: John R Barker <john@johnrbarker.com>
Co-authored-by: Felix Fontein <felix@fontein.de>
(cherry picked from commit 80e7e1a)

Co-authored-by: Toshio Kuratomi <a.badger@gmail.com>
@ansible ansible locked and limited conversation to collaborators Jun 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.12 core_review In order to be merged, this PR must follow the core review workflow. docs This issue/PR relates to or includes documentation. has_issue needs_rebase https://docs.ansible.com/ansible/devel/dev_guide/developing_rebasing.html needs_revision This PR fails CI tests or a maintainer has requested a review/revision of the PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants