-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop Scenario Guides #2022
Drop Scenario Guides #2022
Conversation
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 10m 11s |
055011b
to
3158c3c
Compare
3158c3c
to
ae03449
Compare
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 11m 01s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Do we want to offer something in return? |
I'm not sure. The problem is that we would have to keep the documentation up to date and we already have problems with keeping up with all the isuues and PRs. So, yes, it would be nice to have some some kind of scenario guides or similar, but who's going to maintain that? FYI My main reason to remove the scenario guides is that they fail the CI since the last antsibull-docs docs release and I didn't find a way to fix this. Droping them completely saves a lot of work and prevents to run into similar situations in the future. |
Build succeeded (gate pipeline). ✔️ ansible-tox-linters SUCCESS in 11m 05s |
54fa055
into
ansible-collections:main
Drop Scenario Guides SUMMARY Those scenario guides are pretty outdated, most of them 3 years old. I think it's better to remove them instead of keeping outdated documentation. ISSUE TYPE Docs Pull Request Reviewed-by: Sandra McCann <samccann@redhat.com> Reviewed-by: Alexander Nikitin <ihumster@ihumster.ru>
SUMMARY
Those scenario guides are pretty outdated, most of them 3 years old. I think it's better to remove them instead of keeping outdated documentation.
ISSUE TYPE