collection requirements/steering committee inclusion policy: change

[Andersson007]

See https://forum.ansible.com/t/should-we-keep-the-fortinet-collections-fortinet-fortimanager-fortinet-fortios-in-the-community-ansible-package/3014

[Andersson007]

Should we vote on this PR or we can merge after someone else from SC approves the PR, ideas?

[samccann]

my non-voting opinion is this needs a formal vote.

[Andersson007]

my non-voting opinion is this needs a formal vote.

yeah, we discussed it a bit yesterday, will open the vote on Monday, was going but forgot to update the comment:)

[gundalow]

I approve as we have In case of rejection/removal, the collection maintainers receive comprehensive feedback from the Committee explaining the reasons of the decision.

Key thing I want to see is that we give clear feedback early to the Collection Maintainer, and continue to help them. We've done a good job at this so far.

[felixfontein]

This has been approved in https://forum.ansible.com/t/vote-ended-sc-vote-on-inclusion-policy-changes/3194/4.

[patchback]

Backport to stable-2.16: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.16/d9e034c86253cfd97550405ce6ca9bfba0d15729/pr-995

Backported as #1047

🤖 @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 d9e034c on top of patchback/backports/stable-2.15/d9e034c86253cfd97550405ce6ca9bfba0d15729/pr-995

Backporting merged PR #995 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/d9e034c86253cfd97550405ce6ca9bfba0d15729/pr-995 upstream/stable-2.15

4. Now, cherry-pick PR collection requirements/steering committee inclusion policy: change #995 contents into that branch:

   $ git cherry-pick -x d9e034c86253cfd97550405ce6ca9bfba0d15729

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

   $ git cherry-pick -m1 -x d9e034c86253cfd97550405ce6ca9bfba0d15729

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR collection requirements/steering committee inclusion policy: change #995 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-2.15/d9e034c86253cfd97550405ce6ca9bfba0d15729/pr-995

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.

[Andersson007]

Thanks everyone!