3:11 PM Frank Kloeker > <mailto:eu...@arcor.de>> wrote:
> >
> > Am 2018-09-19 20:54, schrieb Andreas Jaeger:
> > > On 2018-09-19 20:50, Petr Kovar wrote:
> > >> Hi all,
> > >>
> > >> Based on our PTG discussion
Hi all,
Just wanted to share a summary of docs- and i18n-related meetings
and discussions we had in Denver last week during the Stein Project
Teams Gathering.
The overall schedule for all our sessions with additional comments and
meeting minutes can be found here:
Hi all,
Based on our PTG discussion, I'd like to nominate Ian Y. Choi for
membership in the openstack-doc-core team. I think Ian doesn't need an
introduction, he's been around for a while, recently being deeply involved
in infra work to get us robust support for project team docs translation and
Hi all,
With the Rocky release quickly approaching, I wanted to draw your attention
to installation guides testing. With each project team now maintaining
their own installation guide, and with the old coordinated effort to test
installation docs now retired, the Docs team recently updated
Hi all,
This is a request for an FFE to release openstackdocstheme 1.21.2.
This mostly fixes usability issues in rendering docs content, so we would
like to update the theme across all project team docs on docs.o.o.
See also the update constraint request at
://review.openstack.org/#/c/583239/1/doc/doc-contrib-guide/source/rst-conv/titles.rst
Thanks,
pk
On Fri, 29 Jun 2018 16:45:53 +0200
Petr Kovar wrote:
> Hi all,
>
> Feedback from the Queens PTG included requests for the Documentation
> Project to provide guidance and recommendations on how to stru
Hi all,
Feedback from the Queens PTG included requests for the Documentation
Project to provide guidance and recommendations on how to structure common
content typically found on the front page for project team docs, located at
doc/source/index.rst in the project team repository.
I've created a
/578398/
Thanks,
pk
On Wed, 20 Jun 2018 14:21:57 +0200
Petr Kovar wrote:
> Hi all,
>
> Due to low attendance in docs project meetings in recent months, I'd like
> to propose turning regular docs meetings into office hours, like many other
> OpenStack teams did.
>
> My i
On Tue, 26 Jun 2018 12:36:52 -0500
Sean McGinnis wrote:
> >
> > Plan
> >
> > So to recap above, I would propose the following actions be taken:
> >
> > 1. Create sig-operators as a group to manage operator efforts at least
> > related
> >to what needs to be done in repos.
> > 2.
Hi all,
Due to low attendance in docs project meetings in recent months, I'd like
to propose turning regular docs meetings into office hours, like many other
OpenStack teams did.
My idea is to hold office hours every Wednesday, same time we held our
docs meetings, at 16:00 UTC, in our team
Hi all,
Apologies but have to cancel today's docs meeting due to a meeting
conflict.
Have questions for the docs team? We hang out at #openstack-doc.
Thanks,
pk
__
OpenStack Development Mailing List (not for usage
===
#openstack-doc: docteam
===
Meeting started by pkovar at 16:00:44 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/docteam/2018/docteam.2018-05-30-16.00.log.html
.
Meeting summary
---
* Ops docs discussion
Hi all,
The docs meeting will continue today at 16:00 UTC in
#openstack-doc, as scheduled. For more details, see the meeting page:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Cheers,
pk
__
OpenStack Development
On Thu, 17 May 2018 15:03:23 +
Jeremy Stanley <fu...@yuggoth.org> wrote:
> On 2018-05-17 16:35:36 +0200 (+0200), Petr Kovar wrote:
> > On Wed, 16 May 2018 17:05:15 +
> > Jeremy Stanley <fu...@yuggoth.org> wrote:
> >
> > > On 2018-05-1
On Thu, 24 May 2018 07:19:29 -0700
"Jonathan D. Proulx" wrote:
> My intention based on current understandign would be to create a git
> repo called "osops-docs" as this fits current naming an thin initial
> document we intend to put there and the others we may adopt from
>
Hi all,
I'd like to thank Brian Moss and Maria Zlatkova who
recently stepped down from the docs core team, for all their
contributions to OpenStack documentation in the past years.
Thank you for your community work, insight, and ideas you shared with
the community while in your core role. Hope
On Wed, 16 May 2018 17:05:15 +
Jeremy Stanley <fu...@yuggoth.org> wrote:
> On 2018-05-16 18:24:45 +0200 (+0200), Petr Kovar wrote:
> [...]
> > I'd like to propose replacing the reference to the IBM Style Guide
> > with a reference to the developerWorks editoria
On Wed, 16 May 2018 13:26:46 -0600
Wesley Hayutin wrote:
> On Wed, May 16, 2018 at 3:05 PM Doug Hellmann wrote:
>
> > Excerpts from Wesley Hayutin's message of 2018-05-16 12:51:25 -0600:
> > > On Wed, May 16, 2018 at 2:41 PM Doug Hellmann
Hi all,
For OpenStack documentation contributors, we provide a basic style guide
that describes most important guidelines for writing, user interface
guidelines, and RST conventions:
https://docs.openstack.org/doc-contrib-guide/writing-style.html
Hi all,
In the past few years, we've seen several efforts aimed at automating
procedural documentation, mostly centered around the OpenStack
installation guide. This idea to automatically produce and verify
installation steps or similar procedures was mentioned again at the last
Summit
Hi all,
The docs meeting will continue today at 16:00 UTC in
#openstack-doc, as scheduled. For more details, see the meeting page:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Cheers,
pk
__
OpenStack Development
"OpenStack Development Mailing List (not for usage questions)"
> <OpenStack-dev@lists.openstack.org>
> Cc: Petr Kovar <pko...@redhat.com>, Jean-Philippe Evrard
> <jean-phili...@evrard.me>
> Subject: [openstack-dev][docs][openstack-ansible]
>
> Hi all,
>
&g
Hi all,
Apologies but have to go offline now so canceling today's docs meeting.
If you want to talk to the docs team, join #openstack-doc.
Thanks,
pk
__
OpenStack Development Mailing List (not for usage questions)
On Tue, 01 May 2018 10:08:23 -0400
Doug Hellmann wrote:
> The TC has had an item on our backlog for a while (a year?) to
> document "constellations" of OpenStack components to make it easier
> for deployers and users to understand which parts they need to have
> the
===
#openstack-doc: docteam
===
Meeting started by pkovar at 16:02:48 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/docteam/2018/docteam.2018-04-18-16.02.log.html
.
Meeting summary
---
* Open discussion
Hi all,
The docs meeting will continue today at 16:00 UTC in
#openstack-doc, as scheduled. For more details, see the meeting page:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Cheers,
pk
__
OpenStack Development
On Fri, 06 Apr 2018 15:52:46 +0100
Stephen Finucane wrote:
> On Fri, 2018-04-06 at 08:02 -0500, Sean McGinnis wrote:
> > > >
> > > > How can we enable warning_is_error in the gate with the new PTI? It's
> > > > easy enough to add the -W flag in tox.ini for local builds,
===
#openstack-doc: docteam
===
Meeting started by pkovar at 16:02:31 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/docteam/2018/docteam.2018-04-04-16.02.log.html
.
Meeting summary
---
* dropdown menus on
Hi all,
The docs meeting will continue today at 16:00 UTC in
#openstack-doc, as scheduled. For more details, see the meeting page:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Cheers,
pk
__
OpenStack Development
Hi all,
Apologies but have to cancel today's docs meeting due to a meeting
conflict.
If you want to talk to the docs team, we're in #openstack-doc, as always!
Thanks,
pk
__
OpenStack Development Mailing List (not for
On Mon, 19 Mar 2018 14:57:58 +
Jim Rollenhagen wrote:
> Ironic (and surely other projects) have had to point out many times that
> specs are a point in time design discussion, and not completed
> documentation. It's obviously too much work to go back and update specs
Hi all,
For historical reasons, the docs team maintains a separate core group for
the docs-specs repo. With the new docs processes in place, we agreed at the
Rocky PTG to further simplify the docs group setup and retire
openstack-doc-specs-core by removing the existing members and adding
On Wed, 14 Mar 2018 10:38:37 -0500
Jay S Bryant <jungleb...@gmail.com> wrote:
>
>
> On 3/14/2018 10:04 AM, Petr Kovar wrote:
> > On Tue, 13 Mar 2018 18:57:24 -0500
> > Jay S Bryant <jungleb...@gmail.com> wrote:
> >
> >> Amy,
> >>
e deployment and admin docs as well?
> >
> > Amy (spotz)
> >
> > On Tue, Mar 13, 2018 at 2:55 PM, Jay S Bryant <jungleb...@gmail.com
> > <mailto:jungleb...@gmail.com>> wrote:
> >
> >
> >
> > On 3/13/2018 1:38 PM,
On Thu, 8 Mar 2018 12:54:06 -0600
Jay S Bryant wrote:
> Good overview. Thank you!
>
> One additional goal I want to mention on the list, for awareness, is the
> fact that we would like to eventually get some consistency to the pages
> that the 'Contributor Guide' lands
Hi all,
Canceling today's docs meeting as there is not much to share beyond what
was in the PTG summary I sent.
As always, we're in #openstack-doc if you want to talk to us!
Thanks,
pk
__
OpenStack Development Mailing
Hi all,
Just wanted to share a summary of docs- and i18n-related meetings
and discussions we had in Dublin last week during the Rocky Project
Teams Gathering.
I think we can say both our teams, docs and i18n, are now pretty stable
member-wise, following new processes and goals set up earlier in
Hi all,
Similarly to the Queens PTG, we will have docs people around at the Rocky
PTG from Wednesday through Friday next week to help project teams with their
docs!
People from the docs team can meet with your project team to discuss your
documentation needs. Together, we can look into planning,
On Sun, 18 Feb 2018 15:44:04 -0500
Doug Hellmann wrote:
> Excerpts from Jeremy Stanley's message of 2018-02-18 16:01:52 +:
> > On 2018-02-18 03:55:51 -0600 (-0600), Monty Taylor wrote:
> > [...]
> > > I'd honestly argue in favor of assuming bash and using 'source'
> >
===
#openstack-doc: docteam
===
Meeting started by pkovar at 16:01:11 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/docteam/2018/docteam.2018-02-21-16.01.log.html
.
Meeting summary
---
* Rocky PTG (pkovar,
Hi all,
The docs meeting will continue today at 16:00 UTC in
#openstack-doc, as scheduled. For more details, see the meeting page:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Cheers,
pk
__
OpenStack Development
On Fri, 16 Feb 2018 17:49:37 +0100
Thomas Goirand <z...@debian.org> wrote:
> On 02/16/2018 03:42 PM, Petr Kovar wrote:
> > On Thu, 15 Feb 2018 09:31:19 +0100
> > Thomas Goirand <z...@debian.org> wrote:
> >
> >> Hi,
> >>
> >> Since I'm
On Thu, 15 Feb 2018 09:31:19 +0100
Thomas Goirand wrote:
> Hi,
>
> Since I'm getting some pressure from other DDs to actively remove Py2
> support from my packages, I'm very much considering switching all of the
> Debian packages for Queens to using exclusively Py3. I would
===
#openstack-doc: docteam
===
Meeting started by pkovar at 16:00:38 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/docteam/2018/docteam.2018-02-07-16.00.log.html
.
Meeting summary
---
* retired internal -core
Hi all,
The docs meeting will continue today at 16:00 UTC in
#openstack-doc, as scheduled. For more details, see the meeting page:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Cheers,
pk
__
OpenStack Development
Hi all,
I'd like to announce my candidacy for PTL of the Docs project for Rocky.
I've been the Docs PTL since Queens and besides my work on OpenStack docs, I
also contribute to the RDO Project.
During the Queens cycle, we mostly finalized our work on project docs
migration, we also continued
Hi all,
This is more of an FYI for people interested in all things docs that the
docs core team agreed on opening up the process for new docs core
nominations or removals. Instead of using a private list, this will now be
discussed in public, using the openstack-dev list, as documented here:
===
#openstack-doc: docteam
===
Meeting started by pkovar at 16:00:51 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/docteam/2018/docteam.2018-01-24-16.00.log.html
.
Meeting summary
---
* roll call (pkovar,
Hi all,
The docs meeting will continue today at 16:00 UTC in
#openstack-doc, as scheduled. For more details, see the meeting page:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Cheers,
pk
__
OpenStack Development
===
#openstack-doc: docteam
===
Meeting started by pkovar at 16:00:32 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/docteam/2018/docteam.2018-01-10-16.00.log.html
.
Meeting summary
---
* roll call (pkovar,
Hi all,
The docs meeting will continue today at 16:00 UTC in
#openstack-doc, as scheduled. For more details, see the meeting page:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Cheers,
pk
__
OpenStack Development
On Thu, 4 Jan 2018 16:06:53 +
Graham Hayes wrote:
> On 04/01/18 15:39, Stephen Finucane wrote:
> > I'm not sure what the procedure for this is but here goes.
> >
> > I've noticed that the 'os-api-ref' project seems to have its own group
> > of cores [1], many of whom are no
On Tue, 17 Oct 2017 19:15:32 +0200
Petr Kovar <pko...@redhat.com> wrote:
> On Thu, 28 Sep 2017 12:51:18 -0400
> Doug Hellmann <d...@doughellmann.com> wrote:
>
> > At the Queens PTG in Denver the documentation team members present
> > discussed a new reten
===
#openstack-doc: docteam
===
Meeting started by pkovar at 16:01:40 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/docteam/2017/docteam.2017-12-13-16.01.log.html
.
Meeting summary
---
* roll call (pkovar,
Hi all,
The docs meeting will continue today at 16:00 UTC in
#openstack-doc, as scheduled. For more details, and the agenda, see the meeting
page:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Cheers,
pk
__
Hi all,
At the last docs meeting, we agreed to start planning on what
docs and i18n topics to focus on during the docs meetup at the upcoming
Dublin PTG. Apart from reviewing our progress on action items defined at
the previous PTG, we also want to cover other high-priority areas,
infrastructure
Hi all,
As previously announced, I'm sending a final notice that we are closing
down openstack-d...@lists.openstack.org.
Please use openstack-dev@lists.openstack.org with the [docs] tag in
subject for documentation-related discussions.
No new subscriptions or postings will be allowed for
===
#openstack-doc: docteam
===
Meeting started by pkovar at 16:00:16 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/docteam/2017/docteam.2017-11-29-16.00.log.html
.
Meeting summary
---
* roll call (pkovar,
Hi all,
The docs meeting will continue tomorrow, Wednesday at 16:00 UTC in
#openstack-doc, as scheduled. For more details, and the agenda, see the meeting
page:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Cheers,
pk
Hi all,
To keep everybody updated on the recent docs meetups and IRL conversations,
I wanted to share a summary of the Sydney Summit docs sessions that I
took part in. Though a bit belated, posting it just in time before the next
docs meeting this Wednesday.
On Thu, 23 Nov 2017 09:38:34 +0100
Thierry Carrez wrote:
> Doug Hellmann wrote:
> >
> >> On Nov 22, 2017, at 11:22 AM, Ian Y. Choi wrote:
> >>
> >> Hello,
> >>
> >> Maybe there would be some chance to be also considered with PDF builds?
> >>
> >> I
All,
Please consider today's meeting canceled.
Thanks,
pk
> From: "Petr Kovar" <pko...@redhat.com>
> To: openstack-dev@lists.openstack.org
> Cc: "enstack.org" <openstack-d...@lists.openstack.org>
> Sent: Tuesday, November 14, 2017 11:37:3
Hi docs people,
Our next documentation meeting is scheduled for Wednesday, 15th November.
As I'm traveling this week, I'll be unable to host the meeting. Is
anybody available to run the meeting in my stead?
If not, let's cancel it and meet in two weeks.
Thank you,
pk
Below are the meeting minutes from today's docs team meeting.
===
#openstack-doc: docteam
===
Meeting started by pkovar at 16:00:43 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/docteam/2017/docteam.2017-11-01-16.00.log.html
Hi all,
Based on the input provided by the docs community, we are changing the docs
meeting day from Thursday to Wednesday. Another change is that we'll
meet in #openstack-doc. The time of the day remains the same.
To reiterate, we'll meet tomorrow, 1st November at 16:00 UTC in
#openstack-doc.
is of interest to you, please have
a look and let us know what you think. This is a great chance to provide
input on what you think the OpenStack docs community should focus on in the
next 12 months or so.
Thank you,
pk
On Fri, 27 Oct 2017 16:20:27 +0200
Petr Kovar <pko...@redhat.com>
that goes. If you have any objections, please let me know.
Cheers,
pk
On Fri, 20 Oct 2017 18:33:46 +0200
Petr Kovar <pko...@redhat.com> wrote:
> Chason,
>
> Thanks for bringing this up. I definitely don't want contributors from Asia
> to feel excluded. We discussed it in the docs
On Tue, 17 Oct 2017 17:27:10 +0200
Petr Kovar <pko...@redhat.com> wrote:
> Thanks for your feedback, everybody. I made some more edits to the
> document and tried to address the remaining comments left in the etherpad.
>
> I think the current revision of the doc provi
> When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of OpenStack-docs digest..."
> >
> >
> > Today's Topics:
> >
> > 1. [docs] Documentation meeting Thursday (Petr Kovar)
> >
> >
Below are the meeting minutes from yesterday's docs team meeting.
Because we ran out of time (too many items to cover!), the conversation
about site map automation continued in #openstack-doc after the meeting:
Hi all,
The docs meeting will continue tomorrow, Thursday at 16:00 UTC in
#openstack-meeting, as scheduled. For more details, and the agenda, see the
meeting page:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Cheers,
pk
On Thu, 28 Sep 2017 12:51:18 -0400
Doug Hellmann wrote:
> At the Queens PTG in Denver the documentation team members present
> discussed a new retention policy for content published to
> docs.openstack.org. I have a spec up for review to document that
> policy and the
; > I've made a bit of progress on the collaborative vision for the Docs
> > > team:
> > > https://docs.google.com/document/d/1Xy78CnmnKlQ7SbR1XewqgrUdGe7DqnKAGYw_9aj5Ndg/edit#
> > >
> > >
> > >
> > > This still needs plenty of work, but I wanted to put out what we
As for logging 301s, 302s and 404s and the scope, I don't think we are
interested in checking EOL content for those.
As we are about to approve https://review.openstack.org/#/c/507629/, we
also want everybody to understand broken links found in EOL content won't
be fixed, since no content updates
Hi all,
Just a quick update on how the contributor portal project will be
organized.
We created a new subteam under the Documentation Project.
This subteam (specialty team), led by Mike, will maintain the
portal repo openstack/contributor-guide.
Patches addressing this have been merged:
On Wed, 4 Oct 2017 09:59:34 -0500
Jay S Bryant wrote:
>
>
> On 9/29/2017 3:27 PM, Doug Hellmann wrote:
> > Excerpts from Petr Kovar's message of 2017-09-29 21:09:02 +0200:
> >> On Tue, 26 Sep 2017 18:53:04 -0500
> >> Jay S Bryant wrote:
> >>
> >>>
>
Hi all,
The docs meeting will continue today at 16:00 UTC in #openstack-meeting, as
scheduled. For more details, and the agenda, see the meeting page:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Cheers,
pk
__
On Tue, 26 Sep 2017 18:53:04 -0500
Jay S Bryant wrote:
>
>
> On 9/25/2017 3:47 AM, Alexandra Settle wrote:
> >
> > > I completely agree consistency is more important, than bike shedding
> > over the
> > > name :)
> > > To be honest, it would be easier
Hi all,
Just wanted to share a few notes and a brief summary of what happened in
Denver last week, during the Project Team Gathering, in docs and i18n
shared sessions.
We had a fairly good attendance of 5 to 15 ppl during the first two
days. A number of people primarily working on other projects
Hi all,
Just a reminder that we are meeting tomorrow at 9 am in Colorado Ballroom C
for an Install Guides testing session.
Interested? Sign up here:
https://etherpad.openstack.org/p/docs-i18n-ptg-queens
See you there!
pk
On Fri, 01 Sep 2017 09:47:18 +0200
Frank Kloeker wrote:
Hi all,
For those attending the PTG in Denver, let's have team lunch today. We'd
meet at 12 pm in front of the PTG registration desk.
See you there,
pk
__
OpenStack Development Mailing List (not for usage questions)
Hi all,
The docs meeting will continue tomorrow, Thursday at 16:00 UTC in
#openstack-meeting, as scheduled. For more details, and the agenda, see the
meeting page:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Cheers,
pk
> > missing pages. At this point, the missing docs will need to be backported to
> > the stable/pike branches for those projects.
> > Let me know if you need help approving things in the stable branches.
> >
> > [1] https://doughellmann.com/doc-migration/
> >
> > __
On Fri, 25 Aug 2017 15:40:07 +0200
Roger Luethi wrote:
> I don't know what will get changed or created until the release, but
> what I can find right now in terms of installation instructions is this:
>
> https://docs.openstack.org/pike/install/
>
> leading to the "OpenStack Installation
Hi all,
The docs meeting will continue tomorrow, Thursday at 16:00 UTC in
#openstack-meeting, as scheduled. For more details, and the agenda, see the
meeting page:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Cheers,
pk
Hi all,
With the core docs suite moving from openstack-manuals to individual
project repos as per
http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html,
it's also time to update the docs team mission statement from
that docs are a great way to get involved in the project for
both the non- and developers.
Thank you,
pk
--
Petr Kovar
Sr. Technical Writer | Customer Content Services
Red Hat Czech, Brno
__
OpenStack Development Mailing List
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 is not related to the topic:
> “doc-migration”.
>
> We are currently in the
On Mon, 22 May 2017 09:39:09 +
Alexandra Settle wrote:
(...)
> Until this point, the documentation team has owned several manuals that
> include
> content related to multiple projects, including an installation guide, admin
> guide, configuration guide, networking
89 matches
Mail list logo