> I completely agree consistency is more important, than bike shedding over
the
> name :)
> To be honest, it would be easier to change everything to ‘guide’ – seeing
as
> all our URLs are ‘install-guide’.
> But that’s the lazy in me speaking.
>
> Industry wise – the
> For me, a tutorial is something that teaches. So after I've gone through a
> tutorial I would expect to have learned how installs work and would just
know
> these things (with an occasional need to reference a few points) going
forward.
>
> A guide to me is something that I know
Hi everyone,
The documentation team meeting is cancelled today as I am unable to host this
afternoon due to a conflict,
and Petr is travelling home from the PTG.
The next documentation team meeting will be scheduled in #openstack-meeting at
16:00 UTC, 5 October 2017.
Petr has asked me to menti
Hi everyone,
I hope everyone had a safe trip home after the PTG!
Since the doc-migration, quite a number or individuals have had questions
regarding the usage of “Install Tutorial” vs. “Install Guide” in our
documentation in the openstack-manuals repo and in the project-specific repos.
We (the
On 9/6/17, 12:10 PM, "Doug Hellmann" wrote:
Excerpts from Doug Hellmann's message of 2017-09-05 13:53:40 -0400:
> Excerpts from Boden Russell's message of 2017-09-05 11:25:34 -0600:
> >
> > On 9/5/17 11:03 AM, Doug Hellmann wrote:
> > > Is eventlet being initialized (or par
I have updated the mission statement as per Thierry’s suggestion (thank you, I
liked that a lot!)
See the review here: https://review.openstack.org/#/c/499556/
It is currently in WIP. Petr and I agree that the best place to discuss this
will be at the PTG.
On 8/22/17, 5:34 PM, "Doug Hellmann"
Hi everyone,
The documentation team is searching for volunteers to help test and verify the
OpenStack installation instructions here:
https://docs.openstack.org/install-guide/
Previously this action has been undertaken by a series of volunteers, mostly
from the documentation team. However due
Hey Ruby!
Good point – thanks for bringing it up :)
I was brought up to think that red was one of those colours that people had
different (and sometimes really negative) associations with. When I look at our
latest and greatest! ironic documentation (e.g. [1]), I see red. Not only do I
see red
Hi everyone,
I’ve updated the docs PTG etherpad with a few details:
https://etherpad.openstack.org/p/denver-doc-PTG
All those attending, could you please put your names/availability on the
etherpad.
Also – to those interested who cannot attend on the Mon-Tues for Queens
planning sessions, ple
Sigh. The Queen release deliverables*, not the Pike release deliverables.
One day I will send out an email without something incorrect.
From: Alexandra Settle
Date: Thursday, August 17, 2017 at 10:22 AM
To: openstack-docs , "OpenStack Development
Mailing List (not for usage ques
Hi everyone,
The PTL nomination period is now over, so I'm pleased to be able to confirm
that Petr Kovar is our new PTL for Queens.
Congratulations, Petr! I am excited to be working with you on the doc team
future, and I can't wait to see what the docs team can achieve under your
stewardship.
Reminder: Docs meeting as normally scheduled in #openstack-meeting today at
16:00UTC.
Agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Thanks,
Alex
From: Alexandra Settle
Date: Tuesday, August 8, 2017 at 11:13 AM
To: openstack-docs , "OpenStack Development
Mailing List
Hi everyone,
With the upcoming PTG and all of the big changes with the migration, I will be
hosting the docs meeting as normally scheduled in #openstack-meeting on
Thursday, 10th of August at 16:00UTC.
I will send out the agenda closer to the day. I *strongly* urge all to attend.
I know it’s n
Hey everyone,
Put your hand in the air* if you’re attending the PTG!
Myself and the potential PTL will need to start planning shortly, and it would
be good to get an idea of numbers, and who we are planning for.
I will be looking at hosting a working bee or hack session for migration
related i
Hi everyone,
As you all know, we have been changing the way the documentation team operates.
Chief among those
changes are reducing the workload on the shrinking team. The migration to move
installation, admin, and
configuration documentation to project-team repositories is the first phase of
t
Just to add to this, today I have spent some time going through and abandoning
patches that were against the master branch for openstack-manuals and I have
backported those applicable to Ocata.
If anyone has patches against the master branch that are addressing a
bug/fix/enhancement in the inst
Sound proposal. +1
Thanks Andreas
On 6/30/17, 2:16 PM, "Andreas Jaeger" wrote:
It's IMHO time to retire
http://git.openstack.org/cgit/openstack/clouddocs-maven-plugin/ - this
was used to build documents from XML.
We converted all documents to RST, have released the last ve
Hi everyone,
If you have any questions/concerns/comments/feelings you have about the doc
migration, bring ‘em to #openstack-meeting at 1600UTC today :)
I’ll be there to chat instead of our regularly scheduled meeting :)
Cheers,
Alex
From: Alexandra Settle
Date: Wednesday, June 28, 2017 at 6
Hey everyone,
The docs meeting will continue in #openstack-meeting as scheduled (Thursday,
29th of June at 16:00 UTC).
There will be no official agenda, I am opening up this meeting for any docs
liaisons and PTLs to come and chat about the docs migration and any questions
they may have.
The m
you again! Anyone else able to help Mario?
Cheers,
Alex
From: Mario Pranjic
Date: Wednesday, June 28, 2017 at 7:32 AM
To: Alexandra Settle
Subject: Re: [OpenStack-docs] [Openstack-operators][dev][doc] Operations Guide
future
Hi,
I can help with wiki. It depends what are the schedules?
I am
Thanks everyone for your feedback regarding the proposal below.
Going forwards we are going to implement Option 3.
If anyone is able to help out with this migration, please let me know :)
Looking forward to getting started!
From: Alexandra Settle
Date: Thursday, June 1, 2017 at 4:06 PM
To
I think this is a good idea :) thanks Mike. We get a lot of people coming to
the docs chan or ML asking for help/where to start and sometimes it’s difficult
to point them in the right direction.
Just from experience working with contributor documentation, I’d avoid all
screen shots if you can –
Hi everyone,
This morning (afternoon) the specification for the documentation migration was
merged. Thanks to all that took time to review :)
You can now view here in all its glory:
https://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html
If you have any questions,
go through it with said individual.
Cheers,
Alex
On 6/23/17, 3:47 AM, "Blair Bethwaite" wrote:
Hi Alex,
On 2 June 2017 at 23:13, Alexandra Settle wrote:
> O I like your thinking – I’m a pandoc fan, so, I’d be interested in
> moving this along using a
On 6/20/17, 2:12 PM, "Anne Gentle" wrote:
On Tue, Jun 20, 2017 at 3:13 AM, Alexandra Settle
wrote:
>
>
> On 6/19/17, 6:19 PM, "Petr Kovar" wrote:
>
> On Mon, 19 Jun 2017 15:56:35 +
> Alexandra Settle
On 6/19/17, 6:19 PM, "Petr Kovar" wrote:
On Mon, 19 Jun 2017 15:56:35 +
Alexandra Settle wrote:
> Hi everyone,
>
> As of today - Monday, the 19th of June – please do NOT merge any patches
into
> the openstack-manuals repository that
Hi everyone,
As of today - Monday, the 19th of June – please do NOT merge any patches into
the openstack-manuals repository that is not related to the topic:
“doc-migration”.
We are currently in the phase of setting up for our MASSIVE migration and we
need to ensure that there will be minimal
Hi everyone,
Doug has been working hard in my absence to answer everyone’s questions and
concerns on the migration spec. Thanks to all that have taken the time to
review.
Due to our limited time frame, we are now looking for the PTLs to provide their
respective +1’s (or -1’s) on the patch.
Ch
Hi everyone,
Doug and I have written up a spec following on from the conversation [0] that
we had regarding the documentation publishing future.
Please take the time out of your day to review the spec as this affects
*everyone*.
See: https://review.openstack.org/#/c/472275/
I will be PTO from
Hi everyone,
Next week, Thursday the 15th of June, the OpenStack manuals meeting is
cancelled as I will be PTO.
The next documentation team meeting will be the following bi-weekly allotment
on the 29th of June.
If anyone has any pressing concerns, please email me and I will get back to you
wh
Date: Friday, June 2, 2017 at 1:53 PM
To: Alexandra Settle
Cc: Blair Bethwaite , OpenStack Operators
, "OpenStack Development Mailing List
(not for usage questions)" ,
"openstack-d...@lists.openstack.org"
Subject: Re: [Openstack-operators] [dev] [doc] Operations Guide future
7 at 11:15, George Mihaiescu wrote:
> +1 for option 3
>
>
>
> On Jun 1, 2017, at 11:06, Alexandra Settle wrote:
>
> Hi everyone,
>
>
>
> I haven’t had any feedback regarding moving the Operations Guide to the
> OpenStack
going with option 1, and I think
option 2 is just a workaround without fixing the problem – we are not getting
contributions to the project.
Thoughts?
Alex
From: Alexandra Settle
Date: Friday, May 19, 2017 at 1:38 PM
To: Melvin Hillsman , OpenStack Operators
Subject: Re: [Openstack-operators
Hey everyone,
The docs meeting will continue today in #openstack-meeting as scheduled
(Thursday at 16:00 UTC). For more details, and the agenda, see the meeting
page: -
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting
The meeting chair will be me! Hope you can al
On 5/24/17, 4:34 PM, "Doug Hellmann" wrote:
Excerpts from Thierry Carrez's message of 2017-05-24 16:44:44 +0200:
> Doug Hellmann wrote:
> > Two questions about theme-based initiatives:
> >
> > I would like to have a discussion about the work to stop syncing
> > requirem
> I prefer option 1, which should be obvious from Anne's reference to my
exiting work to enable that. Option 2 seems yucky (to me) because it adds yet
another docs tree and sphinx config to projects, and thus is counter to my hope
that we'll have one single docs tree per repo.
>
>
Project: Documentation and I18N
Attendees: 3-5 (maybe?)
Etherpad: https://etherpad.openstack.org/p/doc-onboarding
What we did:
We ran the session informally based off whoever was there. Due to the small
attendance, we just ran through how the project works (docs like code and all
that).
Discus
Hi everyone,
The documentation team are rapidly losing key contributors and core reviewers.
We are not alone, this is happening across the board. It is making things
harder, but not impossible.
Since our inception in 2010, we’ve been climbing higher and higher trying to
achieve the best documen
Hi everyone,
The OpenStack manuals project had a really productive week at the OpenStack
summit in Boston. You can find a list of all the etherpads and attendees here:
https://etherpad.openstack.org/p/docs-summit
As we all know, we are rapidly losing key contributors and core reviewers. We
are
Hey everyone,
The docs meeting will continue today in #openstack-meeting as scheduled
(Thursday at 16:00 UTC). For more details, and the agenda, see the meeting
page: -
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting
The meeting chair will be me! Hope you can al
This all sounds really great ☺ thanks for taking it on board, Anne!
No questions at present ☺ looking forward to seeing the new design!
From: Anne Gentle
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Monday, May 15, 2017 at 2:33 PM
To: "openstack-d...@lists.ope
Hey everyone,
The docs meeting will continue today in #openstack-meeting-alt as scheduled
(Thursday at 21:00 UTC). For more details, and the agenda, see the meeting
page: -
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting
Last meeting before the summit ☺
Thanks,
Hi everyone,
In light of the unfortunate news with OSIC, the documentation team has been hit
pretty hard. As a result, we need more than ever for our documentation liaisons
to step up and help us out.
However, looking at this list[1] it is unfortunately clear that a lot of people
listed are a
//blueprints.launchpad.net/tripleo/+spec/tripleo-deploy-guide
>>>> Target: pike-3
>>>>
>>>> Volunteers to work on it with me, please let me know.
>>>
>>>
>>> It'd be awesome to have some input from the container
Hey everyone,
Just to clarify – that is Thursday the 20th of April, 2100 UTC.
Apologies for any confusion – just attempting to get ahead of the game and
forgot to remove “today”.
See you there,
Alex
From: Alexandra Settle
Reply-To: "OpenStack Development Mailing List (not for
Hey everyone,
The docs meeting will continue today in #openstack-meeting-alt as scheduled
(Thursday at 21:00 UTC). For more details, and the agenda, see the meeting
page: -
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting
Specialty team leads – if you are unable
Team,
This week I have still been working on drafting a governance tag for our guides
called "docs:follows-policy". I have been working with Doug Hellmann
(dhellmann) in the last week to change to draft dramatically, so it would be
good for doc people and doc liaisons to review. We are trying t
Hey everyone,
The docs meeting will continue today in #openstack-meeting-alt as scheduled
(Thursday at 21:00 UTC). For more details, and the agenda, see the meeting
page: -
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting
The meeting with be hosted by Joseph Robi
On 3/28/17, 2:10 PM, "Jeremy Stanley" wrote:
On 2017-03-28 12:51:44 + (+), Alexandra Settle wrote:
[...]
> Is it possible to get docs and I18N represented here? I know we
> don’t make up a ‘project’ of OpenStack, but we play an important
> part,
Hey Lauren,
It looks great with the new mascots :)
Is it possible to get docs and I18N represented here? I know we don’t make up a
‘project’ of OpenStack, but we play an important part, and I would be nice to
be represented. Especially seeing as I18n work on translating a lot of the dev
compon
s://www.openstack.org/summit/boston-2017/summit-schedule/global-search?t=Alexandra+Settle
== Specialty Team Reports ==
* API - Anne Gentle: There's still a lot of discussion on
https://review.openstack.org/#/c/421846/ which is about API change guidelines.
Take a look and join in on th
e-3
Volunteers to work on it with me, please let me know.
Please add me (irc handle - saneax), I am interested on this.
regards
/sanjay
Thanks,
On Tue, Mar 14, 2017 at 7:00 AM, Alexandra Settle
mailto:a.set...@outlook.com>> wrote:
> Hey Emilien,
>
> You pretty much covered it al
Might be too late, but would be interested in having a docs room too :)
From: Kendall Nelson
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Wednesday, March 15, 2017 at 6:20 PM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: [opensta
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 Tr
Team team team team team,
It's been a crazy few weeks since the PTG ramping up our goals for Pike! Big
thanks to everyone who has really hit the ground running with our new set of
objectives.
This week I have been helping out Ianeta with the High Availability Guide ToC
plan, (which you can rev
Hi everyone,
The docs meeting will be on today, Thursday the 9th March at 2100 UTC in
#openstack-meeting-alt.
For more meeting details, including minutes and the agenda:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Thanks,
Alex
On 3/9/17, 11:18 AM, "John Garbutt" wrote:
On 9 March 2017 at 11:05, Alexandra Settle wrote:
> I have attached the error logs that our tester, Brian Moss, sent to me
earlier this morning.
> He has noted that some people have been able to get the instructions to
Hi everyone,
The installation guide for docs.o.o is currently broken and requires immediate
attention from the doc and nova teams.
I have moved the relevant bug[0] to be CRITICAL at request. Brian Moss (bmoss)
and Amy Marrich (spotz) have been working on a subsequent patch for the last 10
days
e's message of 2017-03-02 14:29:07 +:
> >
> >
> > From: Anne Gentle
> > Date: Thursday, March 2, 2017 at 2:16 PM
> > To: Alexandra Settle
> > Cc: "OpenStack Development Mailing List (not for usage questions)"
, &quo
On 3/2/17, 4:08 PM, "Doug Hellmann" wrote:
Excerpts from Alexandra Settle's message of 2017-03-02 14:29:07 +:
>
>
> From: Anne Gentle
> Date: Thursday, March 2, 2017 at 2:16 PM
> To: Alexandra Settle
> Cc: "OpenStack D
From: Anne Gentle
Date: Thursday, March 2, 2017 at 2:16 PM
To: Alexandra Settle
Cc: "OpenStack Development Mailing List (not for usage questions)"
, "openstack-d...@lists.openstack.org"
Subject: Re: [OpenStack-docs] [docs][release][ptl] Adding docs to the release
sched
] Adding docs to the release
schedule
On 1 Mar 2017, at 10:07, 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 o
FYI, there's a few bugs for the Configuration Reference mentioning
options for some services require updating. I've gone through the doc
and created additional bugs and included the relevant PTL and docs liaison.
Thank you, Darren! I will review this morning :(
Hi!
Anyone who is happy to help out with the liaison role, I am happy to work
alongside them and ensure they are pointed in the right direction.
As Matt said, the position at least means attending docs meetings, helping to
review docs patches that are related to nova, helping to alert the docs
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 release schedule.
>
> We would formu
Hi everyone,
I would like to propose that we introduce a “Review documentation” period on
the release schedule.
We would formulate it as a deadline, so that it fits in the schedule and making
it coincide with the RC1 deadline.
For projects that are not following the milestones, we would transl
Hi everyone,
The OpenStack manuals project had a really productive week at the first PTG in
Atlanta, collaborating with the I18n team on the Monday and Tuesday for the
horizontal sessions.
We were able to have several key leaders in the room, including previous
documentation PTL, Anne Gentle a
017, at 13:32, Alexandra Settle wrote:
>
> Please vote for your fellow documenter below:
The community voting for Boston already closed.
Christian.
--
Christian Berendt
Chief Executive Officer (CEO)
Mail: bere...@betacloud-solutions.de
Web: ht
ng-alt.
Meeting chair will be me (Alexandra Settle - asettle)! \o/
For more meeting details, including minutes and the agenda:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
--
Have a great weekend!
Alex
Lamp enthusiast and award winning marathon sleeper
IRC: as
Hi team,
I apologise for not making the meetup this lunch hour; I was caught up with
documentation priorities.
I am still around for the rest of the week, and would like to see/introduce
myself to you all at some point :)
Thanks,
Alex
From: Amy Marrich
Reply-To: "OpenStack Development Maili
Hi everyone,
The docs team will still be hosting their meeting on Thursday, 23 February at
2100 UTC in #openstack-meeting-alt. We will not be skipping the meeting in
favor for the PTG as the docs sessions are on the Mon-Tues and I would love the
opportunity to immediately report back to people
Hey everyone,
If anyone is interested, I’ll be helping out a few new contributors getting set
up with documentation tools tomorrow morning (Wednesday, 22nd February).
I’ll be on level 1, on the couches near the coffee station for anyone who’s
interested in getting setup and learning a bit about
Hi everyone,
As per the HA discussion in the session today, we’ll be meeting in the room
‘Macon’ at the Sheraton from 3pm, on Wednesday the 22nd of February.
If you would like to join remotely, please let me know :)
Thanks,
Alex
_
Hey everyone,
Ian and I have written up combined docs and I18n schedule for the PTG:
https://etherpad.openstack.org/p/docs-i18n-ptg-pike
I have packed in everything on a pretty tight schedule with time allocations
simply because we have a lot of *big* topics to talk about between the two
proje
Sorry, I’m top posting to this reply because Outlook is a terrible inline
poster.
Hey Designaters!
Have you tried pinging the docs team? (ie: me – Hello! I’m the docs PTL)
Over the last few cycles our team has been able to step in and help with
formatting, writing, and organizing documentatio
ions are on the Mon-Tues and I would love the opportunity
to immediately report back to people who cannot attend.
Meeting chair will be me (Alexandra Settle - asettle)! \o/
For more meeting details, including minutes and the agenda:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
-
Correction: 9th of February.
Apparently, I’m not very good at emails lately.
Thank you, Andreas ;)
From: Alexandra Settle
Date: Thursday, February 9, 2017 at 10:36 AM
To: "openstack-d...@lists.openstack.org" ,
"OpenStack Development Mailing List (not for usage questi
Hello everyone,
Your friendly neighbourhood PTL reminder that the weekly OpenStack manuals
(docs) IRC meeting will be Thursday, 9th of January at 2100 UTC in
in the #openstack-meeting-alt channel:
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Documentation+Team+Meeting&iso=20161117T21
Correction!
251 bugs* - good to see I can type an email without errors.
On 2/8/17, 11:25 AM, "Alexandra Settle" wrote:
Hey everyone,
We have 2 weeks until the Ocata release. Hooray! We have fixed 251 so far!
But, we have some more work to do…
I know everyo
Hey everyone,
We have 2 weeks until the Ocata release. Hooray! We have fixed 251 so far! But,
we have some more work to do…
I know everyone is busy with their respective guides and testing, but we have
24 bugs (half are wishlist!) that were assigned for Newton and Ocata that we
have not fixed
+1 from me ☺
Thanks for all your hard work, Marc!
From: Jesse Pretorius
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Friday, February 3, 2017 at 1:33 PM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: [openstack-dev] [openstack-an
Hi everyone,
As of today, all bugs for the Security Guide will be managed by
ossp-security-documentation and no longer will be tracked using the OpenStack
manuals Launchpad.
All tracking for Security Guide related bugs can be found here:
https://bugs.launchpad.net/ossp-security-documentation
Hi OpenStack-Ansible team,
I would like to propose Amy Marrich for the core team for OpenStack-Ansible.
Amy has been consistently in the top 10 reviewers for our team in the last 30
[1] and 90 [2] days, respectively, this release alone.
She has been an active and diligent member of the OpenStac
. Next week, I'll be handling the Docs PTL mantle to Alexandra Settle. I've
worked with Alex in varying capacities over many years, and I have no doubt
that she will be a fabulous PTL. I'm really looking forward to working with
her, and seeing what new directions she's able
Hi everyone,
For anyone who is not on the docs mailing list but is interested in
attending/knowing what we’re up to for the PTG, the joint docs and i18n
planning is here: https://etherpad.openstack.org/p/docs-i18n-ptg-pike
I would like to extend an invitation to anyone who would like to attend
CCing Ianeta Hutchinson and Joseph Robinson that I know were helping the
efforts ☺
On 1/24/17, 12:06 PM, "Paul Bourke" wrote:
Hi Kolla,
Does anyone know the current status of docs refactor? I believe there
was someone looking into it (apologies can't remember their name).
Hi everyone,
The documentation team has been having issues with bugs being filed asking for
troubleshooting and support for years. We have been doing our best to redirect
and close, but it is becoming increasingly unmanageable.
I know other projects struggle with this issue too. We implemented
h you more on IRC or via email.
Coo coo,
Alexandra Settle
IRC: asettle
Twitter: dewsday
Email: a.set...@outlook.com
[1] https://youtu.be/PtomtKeJ0tc?t=1783
[2]
http://docs.openstack.org/arch-design/introduction-how-this-book-was-written.html
[3] http://docs.openstack.org/project-deploy-guide/n
Hey,
I can run the meeting tomorrow ☺
Thanks,
Alex
On 1/11/17, 3:29 PM, "Major Hayden" wrote:
Hey folks,
A conflict came up and I won't be available to run tomorrow's weekly
meeting in IRC. Would someone else be able to take over this meeting for me?
--
Major Hayden
My recommendation, as a documenter for OpenStack, would be to include a link to
each project’s contributor guidelines (as most tend to keep in their developer
documentation pages) in the README file.
I appreciate the README as previously not always been for this purpose, but I
believe it would
I’m sorry to see you go, Matt ☹
Thank you for being an amazing and consistent contributor to the documentation
project. Your work has been invaluable to the Networking community and I know
many (including myself) have appreciated your tireless efforts on the
Installation Guide.
Good luck and a
To add to that, I am currently in the process of adding the driver docs policy
guidelines to the Contributor Guide: https://review.openstack.org/#/c/404785/
From: Anne Gentle
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Wednesday, November 30, 2016 at 3:12 PM
Hi everyone,
I am really pleased to announce that the OpenStack-Ansible Deployment Guide is
now available on the docs.o.o website! You can view it in all its glory here:
http://docs.openstack.org/project-deploy-guide/newton/
This now paves the way for many other deployment projects to publi
ow and we can work together to make this transition ☺
Thanks,
Alexandra Settle
Information Developer II
Rackspace Private Cloud Powered By OpenStack
London, United Kingdom
Rackspace Limited is a company registered in England & Wales (company
registered numbe
94 matches
Mail list logo
