Jump to: navigation, search

Documentation/WhatsUpDoc

< Documentation
Revision as of 03:42, 22 January 2016 by Loquacity (talk | contribs) (Core Team Changes)

Documentation Newsletters

This is where I draft the 'What's Up, Doc?' documentation newsletters. The newsletter is distributed every Friday (ish), to the openstack-docs mailing list. If you want to be added to the distribution list, or have content to add, please edit these sections:

Distribution List

Your suggestions for content

  • Your
  • Content
  • Here
  • Core reviewer responsibilities

Looking for older editions?

You can see older newsletters here: Documentation/WhatsUpDoc_Archive

22 January 2016

Hi everyone,

Welcome to 2016! A short newsletter this week as I get my feet back under me after my vacation. I hope you all had a wonderful holiday period, and got some well-earned down time. I'm looking forward to working hard with you all over the next few months to get Mitaka out into the wild :)

Progress towards Mitaka

75 days to go!

345 bugs closed so far for this release.

RST Conversions

  • All RST conversions are now complete! Well done to all the contributors and reviewers who made this happen so quickly this time around. We are now, with only a couple of exceptions, completely converted. Great job :)

Reorganisations

DocImpact

  • After some discussion on the dev list, we're adjusting our approach to this problem. Watch this space.

Speciality Teams

HA Guide - Bogdan Dobrelya Meeting moved http://lists.openstack.org/pipermail/openstack-docs/2016-January/008209.html. Kenneth finished his Galera patch https://review.openstack.org/#/c/263075/, there were also several patches from different contributors, so things are improving.

Installation Guide - Christian Berendt AODH instructions near completion, EU/US meeting moved (Every two weeks (on even weeks) on Tuesday at 1600 UTC), APAC meeting will be dropped the next weeks if if not more participants join.

Networking Guide - Edgar Magana No update this week.

Security Guide - Nathaniel Dillon No update this week.

User Guides - Joseph Robinson One patch combining Images and Instances content merged, and a patch on Shared File Systems is now available for review. User Guide team meetings are set to begin next Thursday, with guidelines for combining admin and cloud admin files a topic for discussion.

Ops and Arch Guides - Shilla Saebi No update this week.

API Docs - Anne Gentle Anne imported and triaged over 60 GitHub Issues into Launchpad bugs. Anne working on build jobs for making API docs with fairy-slipper: https://review.openstack.org/#/c/269809. Anne emailed over 25 individuals about the plans for API docs and answered follow-up questions. Karen worked on validated Swagger: https://review.openstack.org/#/c/266527/. Need to release fairy-slipper this week or next.

Config Ref - Gauvain Pocentek No update this week.

Training labs - Roger Luethi Liberty is making good progress, trying to get Liberty patches working. Early beginnings of Fedora support switched to CentOS. Copy-on-write disks for KVM. Bug fixing and refactoring, as usual. Early work on python port. Plan to host training labs on a web page.

Training Guides - Matjaz Pancur German translation of the Upstream training (http://docs.openstack.org/de/upstream-training/) - this makes 3 full translations (en, de, ko_kr), ja is at 80%. A patch that enables direct bug reporting on the slides (https://review.openstack.org/#/c/259654/), several other patches.

Hyperviser Tuning Guide - Joe Topjian No update this week.

Core Team Changes

The next core team review will occur on 1 February. In the meantime, it's probably a good time to go over what being a core means, and how the review system works. For more detail, see the Contributor Guide: http://docs.openstack.org/contributor-guide/docs-review.html

Docs cores have the ability to +2 docs reviews, and they also have the ability to merge reviews. Reviews are merged by cores only once there's been *two* +2 votes, and at least one +1. There are very few exceptions to this rule, for changes that need to go through very quickly to resolve gate breakages or similar, but this rule holds in just about every situation. Cores are assigned based on merit, usually through the core review process that we do every month. During a core review, the PTL gathers statistics on reviews made, and patches created and merged, and uses that to determine who should be added to (or removed from) the core list. That then goes to a vote of the existing core team before being actioned and announced. Core team members also have the ability to nominate (and vote on) exceptional team members, where the statistics might not reflect the amount of effort they have put in.

If you ever have any questions about becoming a docs core, or about getting your docs patch merged, you can contact the team on the usual docs mailing list, or ping any of us on IRC.

Doc team meeting

There's been some confusion over the meeting schedule, but as far as I can tell, these are the next meeting dates:

Next meetings: US: Wednesday 20 January, 14:00 UTC APAC: Wednesday 27 January, 00:30 UTC

Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting

--

Keep on doc'ing!

Lana

15 January 2016

Hi everyone,

Welcome to 2016! A short newsletter this week as I get my feet back under me after my vacation. I hope you all had a wonderful holiday period, and got some well-earned down time. I'm looking forward to working hard with you all over the next few months to get Mitaka out into the wild :)

Progress towards Mitaka

82 days to go!

324 bugs closed so far for this release.

RST Conversions

  • All RST conversions are now complete! Well done to all the contributors and reviewers who made this happen so quickly this time around. We are now, with only a couple of exceptions, completely converted. Great job :)

Reorganisations

DocImpact

  • After some discussion on the dev list, we're adjusting our approach to this problem. Watch this space.

Speciality Teams

No updates this week, as I'm totally disorganised. Next week for sure!

Core Team Changes

I would like to offer a warm welcome to Atsushi Sakai as our newest core team member. Welcome to the team :)

We will resume regular reviews in February 2016.

Doc team meeting

There's been some confusion over the meeting schedule, but as far as I can tell, these are the next meeting dates:

Next meetings: US: Wednesday 20 January, 14:00 UTC APAC: Wednesday 27 January, 00:30 UTC

Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting

--

Keep on doc'ing!

Lana