communication guide: overhaul

[Andersson007]

Also removes some ghost town rooms

Related to https://forum.ansible.com/t/proposal-consolidating-ansible-discussion-platforms/6812/15.
If you have general thoughts on the changes (not on wording/structure nuances), please express them in the forum topic ^.

[gundalow]

Thanks for tidying this page up.

I'd like to propose this structure

1. Code of Conduct
2. Forum
   2a) What is it, how to register, how to subscribe
   2b) Bullhorn
   2c) Regional and Language-specific channels

[samccann]

The next thing on our list of things to remove is that separate meetings calendar. We should get the four current community meetings to get it on the forum events calendar and then we can change the links to that. Just a note for the future :-)

[Andersson007]

@samccann

The forum 'new group' button seems to have most of the details and is a form template we can update if we want to add more details - https://forum.ansible.com/g/custom/new

FWIF here's a group description template we use https://forum.ansible.com/t/a-standard-group-description-layout-for-teams/287

[Andersson007]

Feedback incorporated. Ready for review

[gundalow]

I'm happy for this to me merged.
It's a huge improvement over what we had, thanks for the discussion around the feedback.

[patchback]

Backport to stable-2.16: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply b519a73 on top of patchback/backports/stable-2.16/b519a730cecdb7f24c9edc34736e584add4d7e31/pr-1667

Backporting merged PR #1667 into devel

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible/ansible-documentation.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-2.16/b519a730cecdb7f24c9edc34736e584add4d7e31/pr-1667 upstream/stable-2.16

4. Now, cherry-pick PR communication guide: overhaul #1667 contents into that branch:

   $ git cherry-pick -x b519a730cecdb7f24c9edc34736e584add4d7e31

   If it'll yell at you with something like fatal: Commit b519a730cecdb7f24c9edc34736e584add4d7e31 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x b519a730cecdb7f24c9edc34736e584add4d7e31

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR communication guide: overhaul #1667 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-2.16/b519a730cecdb7f24c9edc34736e584add4d7e31/pr-1667

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to stable-2.15: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply b519a73 on top of patchback/backports/stable-2.15/b519a730cecdb7f24c9edc34736e584add4d7e31/pr-1667

Backporting merged PR #1667 into devel

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible/ansible-documentation.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-2.15/b519a730cecdb7f24c9edc34736e584add4d7e31/pr-1667 upstream/stable-2.15

4. Now, cherry-pick PR communication guide: overhaul #1667 contents into that branch:

   $ git cherry-pick -x b519a730cecdb7f24c9edc34736e584add4d7e31

   If it'll yell at you with something like fatal: Commit b519a730cecdb7f24c9edc34736e584add4d7e31 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x b519a730cecdb7f24c9edc34736e584add4d7e31

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR communication guide: overhaul #1667 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-2.15/b519a730cecdb7f24c9edc34736e584add4d7e31/pr-1667

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to stable-2.17: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.17/b519a730cecdb7f24c9edc34736e584add4d7e31/pr-1667

Backported as #1668

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[Andersson007]

@gundalow @oraNod @samccann thanks for reviewing! It's a way better now