problem statement - the ansible PyPI package
called version 3.0.0 will beta at start of Feb 2021 timeframe and
some time after that, the ansible-core PyPI package called version
2.11 will release. We need a way for docs to reflect the two
“streams” of versions. Ansible 3.0.0 docs need to reference back to
ansible-base 2.10 docs for all Ansible features that are not
collections.(samccann,
15:36:18)
proposal docs.ansible.com/ansible becomes
Ansible the Package documentation. docs.ansible.com/ansible-core
becomes the core only documentation.(samccann,
15:36:32)
current status Reviewing internally to get full
buyin from management later this week(samccann,
15:36:50)
Today's meeting goals - implementation -
assuming we get approval, how can we accomplish all this in 3 weeks
and 2 days (to have a docsite for 3.0.0 beta)(samccann,
15:37:14)
If a user installs Ansible 3.x it will never
install ansible=core 2.11(samccann,
16:07:41)
Ansible 4.x would never install core-2.12
either(samccann,
16:09:12)
Docs will reflect what is in Ansible the
package and not attempt to match what a user may manually upgrade
after that(samccann,
16:14:53)
new repo for new community guides etc(samccann, 16:16:39)
We know there are various gaps in the community
documentation, especially around how to look after (maintain, own,
manage) Collection & Collection repos. We have a lot of brand
new docs to write. Currently we've been using
https://github.com/ansible-collections/overview to host some RST.
Though this was always viewed as a short term solution(gundalow,
16:18:39)
I wonder if we could start a new top level
docsite for these brand new docs (docs.ansible.com/community)(gundalow,
16:19:28)
Example index page
https://hackmd.io/uKhHRhFUStG_bVNhY10cLQ#New-Index-structure(gundalow,
16:19:45)