On Tuesday 6th December 2016, the Ansible Core Team re-merged the module repositories back into ansible/ansible in GitHub. The two module repos will be essentially locked, though they will be kept in place for the existing 2.1 and 2.2 dependencies. Once 2.2 moves out of official support (early 2018), these repositories will be fully readonly for all branches. Until then, any issues/PRs opened there will be auto-closed with a note to open it on ansible/ansible.
For those who’ve been using Ansible long enough, you know that originally we started with a single repository. The original intention of the core vs. extras split was that core would be better supported/tested/etc. Extras would have been a bit more of a “wild-west” for modules, to allow new modules to make it into the distribution more quickly. Unfortunately this never really worked out, as well as the following:
As part of this move, we will be introducing module metadata, which will contain a couple of pieces of information regarding modules:
The documentation pages for modules will be updated to reflect the above information as well, so that users can evaluate the status of a module before committing to using it in playbooks and roles.
A tool has been developed to move a PR from the old repos to ansible/ansible this can be found at prmover tool
Before using prmover please ensure you have a fork of the Ansible repo.
To move issues please use GitHub Issue Mover
If you have any issues with updating your PR please ask for support in #ansible-devel
For support please use #ansible-devel on Freenode IRC