Re: [openstack-dev] [all] Proposal: Architecture Working Group

It appears this group could assist with the Architecture Design Guide, which is undergoing a content restructure. We are looking for more technical contributors to provide guidance and contribute information to the guide. Shaun O'Meara has written a spec:

[openstack-dev] [Openstack-docs] [docs] [arch-guide] Architecture Design Guide plan for Pike

Hi everyone, Just an update on the draft Architecture Design Guide. For Ocata, we reorganized some migrated content from the current Arch Guide and Ops Guide, and updated the compute and networking sections in the Design chapter. It is currently published at

Re: [openstack-dev] [OpenStack-docs] [docs][release][ptl] Adding docs to the release schedule

On 2/3/17 5:07 am, Alexandra Settle wrote: On 3/1/17, 5:58 PM, "John Dickinson" wrote: On 1 Mar 2017, at 9:52, Alexandra Settle wrote: > Hi everyone, > > I would like to propose that we introduce a “Review documentation” period on the

[openstack-dev] [Openstack-operators] [OpenStack-docs] [OpenStack-dev] [docs] Project upgrade notes

Hi everyone, There was an operations community discussion during the Ocata summit to include upgrade notes from the developer documentation in the Operations Guide. The spec can be reviewed here:  https://review.openstack.org/#/c/394261/ Feedback and comments are appreciated! Thanks, Darren  

Re: [openstack-dev] [OpenStack-docs] [OpenStack-operators] [docs][upgrades] time to add official docs for upgrading services?

No problem :) I simplified the spec to be more realistic about what we can achieve for Ocata. https://review.openstack.org/#/c/394261/ On Friday, 18 November 2016, 23:53, Steve Martinelli <s.martine...@gmail.com> wrote: On Thu, Nov 17, 2016 at 11:04 PM, darren chan &

Re: [openstack-dev] [OpenStack-docs] [OpenStack-operators] [docs][upgrades] time to add official docs for upgrading services?

Good timing, I was about to send a follow-up email about this spec. I agree, this content needs to be more visible, which is why the spec proposed to move upgrade notes to the Upgrades chapter in the Operations Guide. However, it seems like the general consensus is to keep content in project