Migrate dev and scenario guides #298
Conversation
mariolenz
changed the title
|
@akinross @lhercot @sajagana Any chance to get this merged? The Steering Committee would be much obliged. |
|
Hi @mariolenz, I saw your PR (thanks!) and will have a look as soon as possible. |
|
@akinross Any news on this PR? Not to put too fine a point on it, but "will have a look as soon as possible" somehow sounded like you would do it within a few weeks, but we're waiting for two months now. I don't even touch your code here. It's just about documentation. Please be fair to the ansible-core developers and help to remove collection-specific development and scenario guides from there repository. Actually, this PR helps you because you can update your documentation yourself in this repository instead of having to open a PR in ansible-core. |
|
@akinross @lhercot this PR will remove the old/stale guide from docs.ansible.com in the next couple of days.. FYI - ansible/ansible#79795 |
|
🤷 |
Greetings from the Steering Committee!
All collection-specific development and scenario guides must be migrated to their respective collections. This improves the ability of a user/developer to find this content on docs.ansible.com and for collection owners to keep this content accurate and up to date.
Fixes #278
cc @samccann