I proposed a blueprint to track the work done: https://blueprints.launchpad.net/tripleo/+spec/tripleo-deploy-guide Target: pike-3
Volunteers to work on it with me, please let me know. Thanks, On Tue, Mar 14, 2017 at 7:00 AM, Alexandra Settle <[email protected]> wrote: > Hey Emilien, > > You pretty much covered it all! Docs team is happy to provide guidance, but > in reality, it should be a fairly straight forward process. > > The Kolla team just completed their deploy-guide patches and were able to > help refine the process a bit further. Hopefully this should help the TripleO > team :) > > Reach out if you have any questions at all :) > > Thanks, > > Alex > > On 3/13/17, 10:32 PM, "Emilien Macchi" <[email protected]> wrote: > > Team, > > [adding Alexandra, OpenStack Docs PTL] > > It seems like there is a common interest in pushing deployment guides > for different OpenStack Deployment projects: OSA, Kolla. > The landing page is here: > https://docs.openstack.org/project-deploy-guide/newton/ > > And one example: > https://docs.openstack.org/project-deploy-guide/openstack-ansible/newton/ > > I think this is pretty awesome and it would bring more visibility for > TripleO project, and help our community to find TripleO documentation > from a consistent place. > > The good news, is that openstack-docs team built a pretty solid > workflow to make that happen: > https://docs.openstack.org/contributor-guide/project-deploy-guide.html > And we don't need to create new repos or do any crazy changes. It > would probably be some refactoring and sphinx things. > > Alexandra, please add any words if I missed something obvious. > > Feedback from the team would be welcome here before we engage any work, > > Thanks! > -- > Emilien Macchi > > -- Emilien Macchi __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
