[Openstack] [user-committee] [openstack-operators] [openstack-community] [osops] Team Bi-Weekly Meeting Summary

Melvin Hillsman mrhillsman at gmail.com
Sun Mar 5 06:13:40 UTC 2017

Apologies for the delay,

We had a great reboot meeting! The previous and upcoming agendas can be
found at the following:


*The next meeting is 3/13 1400UTC in #openstack-meeting-5*

We focused on quite a few things and are looking to start hashing out some
actionable work around the discussions in the coming days, below is just a
snapshot of some items:

   - Establish structure/pluggability around the "when approved" repo (tool
   creators should only have to worry about the logic of what the tool will do
   - common tasks imported via libs)
   - Work towards stable/release branches and tags approach (starting with
   stable/newton being ocata was just released not long ago)
   - Standardizing in general (an example is every tool requires a README
   so at a glance user is aware of pertinent information about the tool)
   - Documentation assistance (it is not about writing but reviewing what
   is currently in place and filing a bug at a minimum, creating a patch is
   always encouraged)
   - Reviewing and contributing user stories -
   https://github.com/openstack/openstack-user-stories (this is significant
   as users have to back the stories for work to be potentially allocated; the
   more +1s/reviews a story gets, more likely it is seen as valuable work)

*We hope to see you in the next meeting, invite a friend or two or 10 and
come with your opinions, grievances, ideas, and dreams!*

Kind regards,

Melvin Hillsman
Ops Technical Lead
OpenStack Innovation Center

mrhillsman at gmail.com
phone: (210) 312-1267
mobile: (210) 413-1659

Learner | Ideation | Belief | Responsibility | Command
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20170305/b73bbb07/attachment.html>

More information about the Openstack mailing list