Update community topics links

[Andersson007]

Update community topics links

Relates to a comment #1421 (comment)

[Andersson007]

ready for review

[mariolenz]

What about Community Topics in maintainers_guidelines.rst?

Otherwise LGTM!

[Andersson007]

What about Community Topics in maintainers_guidelines.rst?

Otherwise LGTM!

@mariolenz good catch, thanks! missed it somehow in the grep output, fixed, PTAL

[mariolenz]

LGTM

[Andersson007]

@oraNod @mariolenz thanks for reviewing!

[patchback]

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

❌ Failed to cleanly apply 83b7c12 on top of patchback/backports/stable-2.15/83b7c122ed48ae2844eea867650b7d880ef026ab/pr-1451

Backporting merged PR #1451 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/83b7c122ed48ae2844eea867650b7d880ef026ab/pr-1451 upstream/stable-2.15

4. Now, cherry-pick PR Update community topics links #1451 contents into that branch:

   $ git cherry-pick -x 83b7c122ed48ae2844eea867650b7d880ef026ab

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

   $ git cherry-pick -m1 -x 83b7c122ed48ae2844eea867650b7d880ef026ab

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

   $ git push origin patchback/backports/stable-2.15/83b7c122ed48ae2844eea867650b7d880ef026ab/pr-1451

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.16: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 83b7c12 on top of patchback/backports/stable-2.16/83b7c122ed48ae2844eea867650b7d880ef026ab/pr-1451

Backporting merged PR #1451 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/83b7c122ed48ae2844eea867650b7d880ef026ab/pr-1451 upstream/stable-2.16

4. Now, cherry-pick PR Update community topics links #1451 contents into that branch:

   $ git cherry-pick -x 83b7c122ed48ae2844eea867650b7d880ef026ab

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

   $ git cherry-pick -m1 -x 83b7c122ed48ae2844eea867650b7d880ef026ab

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

   $ git push origin patchback/backports/stable-2.16/83b7c122ed48ae2844eea867650b7d880ef026ab/pr-1451

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/83b7c122ed48ae2844eea867650b7d880ef026ab/pr-1451

Backported as #1462

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

[Andersson007]

@samccann which version do we need to backport it to besides 2.17?

[patchback]

Backport to stable-2.16: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.16/83b7c122ed48ae2844eea867650b7d880ef026ab/pr-1451

Backported as #1469

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

[samccann]

I got this to backport to 2.16 which we should technically still do as that is latest. 2.15 is a stretch goal and even after banging away at local cherry-picks I hit multiple other bits of content that didn't backport to 2.15 so... I gave up.