uture management - obvious can of worms given this is much better
addressed by all the tooling and scaffolding the docs team already
provides around the repos... but nonetheless some expectations may
need to be set upfront to avoid future pain.
Cheers,
On 15 July 2
Please forgive my naivete here - I am quite new to OpenStack and as such to
the community. I have found that in this project as well as in others, old
documentation
.. can be surprisingly useful, especially when marked with a date or version.
We completely agree with you here, which is why
helps,
Alex
[0]
http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html
[1] https://github.com/openstack/openstack-manuals/tree/before-migration
On 7/17/17, 3:39 AM, "Gregory Orange" wrote:
On 14/07/17 23:48, Alexandra Settle wrote:
> Please
Hi operators,
Please be aware that I have proposed the following patch:
https://review.openstack.org/#/c/483937/
This removes the Operations Guide from the openstack-manuals repo and will no
longer be accessible via docs.openstack.org after the patch merges.
The documentation team does not have
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
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
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
? Questions? Other thoughts?
Alex
From: Melvin Hillsman
Date: Friday, May 19, 2017 at 1:30 PM
To: OpenStack Operators
Subject: [Openstack-operators] Fwd: [openstack-dev] [openstack-doc] [dev]
What's up doc? Summit recap edition
-- Forwarded message --
From: Alexandra Settle mailto:
Hi Amit,
I have CC’d Andy McCrae, the OpenStack-Ansible PTL.
For all OpenStack-Ansible related queries, I would recommend tagging the
subject line with [openstack-anisble] to help those with filters :)
Either that, or potentially ask your question in the IRC channel
#openstack-ansible
Cheers,
14 matches
Mail list logo
