Re: [openstack-dev] [kolla] How to handle doc in kolla and kolla-ansible

I think Jeffrey's raised a good point here. Though I agree we should keep the development side under a single umbrella/namespace, to better co-ordinate our efforts, I think it makes more sense to move the end-user documentation and to the repo that it's associated with. I feel this is the right

Re: [openstack-dev] [kolla] How to handle doc in kolla and kolla-ansible

Then what's the case of kolla-kubernetes? On Mon, Nov 21, 2016 at 5:54 PM, Paul Bourke wrote: > Propose all docs stay under the kolla namespace > (http://docs.openstack.org/developer/kolla). > > Steve mentioned that we should try to keep all components (e.g. mailing list

Re: [openstack-dev] [kolla] How to handle doc in kolla and kolla-ansible

Propose all docs stay under the kolla namespace (http://docs.openstack.org/developer/kolla). Steve mentioned that we should try to keep all components (e.g. mailing list tags) under the same umbrella which I agree with. On 21/11/16 08:05, Jeffrey Zhang wrote: After the split, we have two

[openstack-dev] [kolla] How to handle doc in kolla and kolla-ansible

After the split, we have two projects and two develop docs[0][1]. These two sites have lots of duplicated lines. So will we split the doc site? if so, we need to remove the duplicated doc in the repos. if not, we need to remove one site's doc. [0] http://docs.openstack.org/developer/kolla [1]