Merge branch 'ansible:devel' into devel

.azure-pipelines/azure-pipelines.yml

@@ -46,7 +46,6 @@ stages:
           targets:
             - test: 1
             - test: 2
-            - test: 3
   - stage: Units
     dependsOn: []
     jobs:
@@ -180,7 +179,6 @@ stages:
           nameFormat: Python {0}
           testFormat: galaxy/{0}/1
           targets:
-            - test: 3.9
             - test: '3.10'
             - test: 3.11
   - stage: Generic
@@ -191,7 +189,6 @@ stages:
           nameFormat: Python {0}
           testFormat: generic/{0}/1
           targets:
-            - test: 3.9
             - test: '3.10'
             - test: 3.11
   - stage: Incidental_Windows

.azure-pipelines/commands/sanity.sh

@@ -16,14 +16,8 @@ group2_include=(
     validate-modules
 )
 
-group3_include=(
-    docs-build
-    sanity-docs
-)
-
 group1_exclude=(
     "${group2_include[@]}"
-    "${group3_include[@]}"
 )
 
 options=()
@@ -39,11 +33,6 @@ case "${group}" in
             options+=(--test "${name}")
         done
         ;;
-    3)
-        for name in "${group3_include[@]}"; do
-            options+=(--test "${name}")
-        done
-        ;;
 esac
 
 # shellcheck disable=SC2086

.github/BOTMETA.yml

@@ -59,20 +59,6 @@ files:
   .github/BOTMETA.yml:
     labels: botmeta
     support: core
-  docs/:
-    maintainers:
-    - acozine
-  docs/docsite/rst/community/:
-    maintainers:
-    - gundalow
-  docs/docsite/rst/dev_guide/:
-    maintainers:
-    - gundalow
-  docs/docsite/rst/network/:
-    labels: networking
-    maintainers:
-    - samccann
-  docs/docsite/rst/user_guide/windows: *id001
   hacking/report.py:
     notified: mattclay
   hacking/shippable/:

.github/ISSUE_TEMPLATE/documentation_report.yml

@@ -34,6 +34,32 @@ body:
       [submit a pull request]:
       https://docs.ansible.com/ansible-core/devel/community/documentation_contributions.html
 
+- type: markdown
+  attributes:
+    value: >
+      **Check the repository for your issue.**
+
+      Source files for Ansible community documentation are
+      hosted in different repositories. Please make sure to file an
+      issue in the correct project.
+
+      Documentation for modules/plugins/etc that are officially
+      supported by the Ansible Core Engineering team is available
+      in this (`ansible/ansible`) repository.
+
+      The Installation Guide, Playbook Guide, Developer Guide,
+      and other documentation is available in the
+      [ansible/ansible-documentation] repository.
+      Documentation for other modules/plugins/etc is likely to be
+      available in one of the [Ansible Collections][collections index].
+      If available in the collection documentation, select the
+      **Issue Tracker** button to go directly to the GitHub issues.
+
+
+      [ansible/ansible-documentation]: /ansible/ansible-documentation
+
+      [collections index]:
+      https://docs.ansible.com/ansible/latest/collections/index.html
 
 - type: textarea
   attributes:
@@ -64,9 +90,6 @@ body:
           <em>Why?</em>
         </summary>
 
-        We would do it by ourselves but unfortunatelly, the curent
-        edition of GitHub Issue Forms Alpha does not support this yet 🤷
-
 
         _We will make it easier in the future, once GitHub
         supports dropdown defaults. Promise!_
@@ -85,19 +108,7 @@ body:
       Write the short name of the rst file, module, plugin, task or
       feature below, *use your best guess if unsure*.
 
-
-      **Tip:** Be advised that the source for some parts of the
-      documentation are hosted outside of this repository. If the page
-      you are reporting describes modules/plugins/etc that are not
-      officially supported by the Ansible Core Engineering team, there
-      is a good chance that it is coming from one of the [Ansible
-      Collections maintained by the community][collections org]. If this
-      is the case, please make sure to file an issue under the
-      appropriate project there instead.
-
-
-      [collections org]: /ansible-collections
-    placeholder: docs/docsite/rst/dev_guide/debugging.rst
+    placeholder: lib/ansible/modules/copy.py
   validations:
     required: true
 

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,23 +1,29 @@
 ##### SUMMARY
+
 <!--- Describe the change below, including rationale and design decisions -->
 
 <!--- HINT: Include "Fixes #nnn" if you are fixing an existing issue -->
 
 ##### ISSUE TYPE
+
 <!--- Pick one below and delete the rest -->
+
 - Bugfix Pull Request
 - Docs Pull Request
 - Feature Pull Request
 - Test Pull Request
 
 ##### COMPONENT NAME
+
 <!--- Write the short name of the module, plugin, task or feature below -->
 
 ##### ADDITIONAL INFORMATION
+
 <!--- Include additional information to help people understand the change here -->
 <!--- A step-by-step reproduction of the problem is helpful if there is no related issue -->
 
 <!--- Paste verbatim command output below, e.g. before and after your change -->
+
 ```paste below
 
 ```

MANIFEST.in

@@ -2,18 +2,11 @@ include COPYING
 include bin/*
 include changelogs/CHANGELOG*.rst
 include changelogs/changelog.yaml
-include examples/ansible.cfg
-include examples/hosts
-include examples/scripts/ConfigureRemotingForAnsible.ps1
-include examples/scripts/upgrade_to_ps3.ps1
-include hacking/build-ansible.py
-include hacking/templates/*.j2
 include hacking/test-module.py
 include hacking/update-sanity-requirements.py
 include licenses/*.txt
 include requirements.txt
 recursive-include docs *
-recursive-include hacking/build_library *.py
 recursive-include packaging *.py *.j2
 recursive-include test/integration *
 recursive-include test/sanity *.in *.json *.py *.txt

README.md

@@ -0,0 +1,89 @@
+[![PyPI version](https://img.shields.io/pypi/v/ansible-core.svg)](https://pypi.org/project/ansible-core)
+[![Docs badge](https://img.shields.io/badge/docs-latest-brightgreen.svg)](https://docs.ansible.com/ansible/latest/)
+[![Chat badge](https://img.shields.io/badge/chat-IRC-brightgreen.svg)](https://docs.ansible.com/ansible/latest/community/communication.html)
+[![Build Status](https://dev.azure.com/ansible/ansible/_apis/build/status/CI?branchName=devel)](https://dev.azure.com/ansible/ansible/_build/latest?definitionId=20&branchName=devel)
+[![Ansible Code of Conduct](https://img.shields.io/badge/code%20of%20conduct-Ansible-silver.svg)](https://docs.ansible.com/ansible/latest/community/code_of_conduct.html)
+[![Ansible mailing lists](https://img.shields.io/badge/mailing%20lists-Ansible-orange.svg)](https://docs.ansible.com/ansible/latest/community/communication.html#mailing-list-information)
+[![Repository License](https://img.shields.io/badge/license-GPL%20v3.0-brightgreen.svg)](COPYING)
+[![Ansible CII Best Practices certification](https://bestpractices.coreinfrastructure.org/projects/2372/badge)](https://bestpractices.coreinfrastructure.org/projects/2372)
+
+# Ansible
+
+Ansible is a radically simple IT automation system. It handles
+configuration management, application deployment, cloud provisioning,
+ad-hoc task execution, network automation, and multi-node orchestration. Ansible makes complex
+changes like zero-downtime rolling updates with load balancers easy. More information on the Ansible [website](https://ansible.com/).
+
+## Design Principles
+
+* Have an extremely simple setup process with a minimal learning curve.
+* Manage machines quickly and in parallel.
+* Avoid custom-agents and additional open ports, be agentless by
+  leveraging the existing SSH daemon.
+* Describe infrastructure in a language that is both machine and human
+  friendly.
+* Focus on security and easy auditability/review/rewriting of content.
+* Manage new remote machines instantly, without bootstrapping any
+  software.
+* Allow module development in any dynamic language, not just Python.
+* Be usable as non-root.
+* Be the easiest IT automation system to use, ever.
+
+## Use Ansible
+
+You can install a released version of Ansible with `pip` or a package manager. See our
+[installation guide](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html) for details on installing Ansible
+on a variety of platforms.
+
+Power users and developers can run the `devel` branch, which has the latest
+features and fixes, directly. Although it is reasonably stable, you are more likely to encounter
+breaking changes when running the `devel` branch. We recommend getting involved
+in the Ansible community if you want to run the `devel` branch.
+
+## Get Involved
+
+* Read [Community Information](https://docs.ansible.com/ansible/latest/community) for all
+  kinds of ways to contribute to and interact with the project,
+  including mailing list information and how to submit bug reports and
+  code to Ansible.
+* Join a [Working Group](https://github.com/ansible/community/wiki),
+  an organized community devoted to a specific technology domain or platform.
+* Submit a proposed code update through a pull request to the `devel` branch.
+* Talk to us before making larger changes
+  to avoid duplicate efforts. This not only helps everyone
+  know what is going on, but it also helps save time and effort if we decide
+  some changes are needed.
+* For a list of email lists, IRC channels and Working Groups, see the
+  [Communication page](https://docs.ansible.com/ansible/latest/community/communication.html)
+
+## Coding Guidelines
+
+We document our Coding Guidelines in the [Developer Guide](https://docs.ansible.com/ansible/devel/dev_guide/). We particularly suggest you review:
+
+* [Contributing your module to Ansible](https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_checklist.html)
+* [Conventions, tips, and pitfalls](https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_best_practices.html)
+
+## Branch Info
+
+* The `devel` branch corresponds to the release actively under development.
+* The `stable-2.X` branches correspond to stable releases.
+* Create a branch based on `devel` and set up a [dev environment](https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_general.html#common-environment-setup) if you want to open a PR.
+* See the [Ansible release and maintenance](https://docs.ansible.com/ansible/devel/reference_appendices/release_and_maintenance.html) page for information about active branches.
+
+## Roadmap
+
+Based on team and community feedback, an initial roadmap will be published for a major or minor version (ex: 2.7, 2.8).
+The [Ansible Roadmap page](https://docs.ansible.com/ansible/devel/roadmap/) details what is planned and how to influence the roadmap.
+
+## Authors
+
+Ansible was created by [Michael DeHaan](https://github.com/mpdehaan)
+and has contributions from over 5000 users (and growing). Thanks everyone!
+
+[Ansible](https://www.ansible.com) is sponsored by [Red Hat, Inc.](https://www.redhat.com)
+
+## License
+
+GNU General Public License v3.0 or later
+
+See [COPYING](COPYING) to see the full text.