|
|
| (567 intermediate revisions by 63 users not shown) |
| Line 1: |
Line 1: |
| | = Weekly Openstack Ansible Deployment team meeting = | | = Weekly Openstack Ansible Deployment team meeting = |
| | | | |
| − | If you're interested in Ansible deploying OpenStack, we hold two public meetings weekly: | + | If you're interested in Ansible deploying OpenStack, we hold a public meetings weekly. |
| | | | |
| − | No meeting the May 14 - 21 due to all core members of the OpenStack Ansible Deployment project traveling or otherwise being at the OpenStack summit. Meetings will resume May 26.
| + | Join us on OFTC [[IRC]] network, in <code><nowiki>#openstack-ansible</nowiki></code>, |
| | + | on [https://www.google.com/search?q=current+utc+time Tuesday at 15:00 UTC], every Tuesday. |
| | | | |
| − | == Community Meeting == | + | == Meeting history and how our meeting works now == |
| − | * On [[IRC]] in <code><nowiki>#openstack-meeting-4</nowiki></code>, on [https://www.google.com/search?q=current+utc+time Thursday at 16:00 UTC].
| |
| | | | |
| − | == Bug Triage ==
| + | Historically, we had two meetings per week: One community meeting, and one bug triage meeting. Due to the lower attendance of both of those, we |
| − | * On [[IRC]] in <code><nowiki>#openstack-ansible</nowiki></code> on [https://www.google.com/search?q=current+utc+time Tuesday at 16:00 UTC].
| + | reduced the amount of meetings to one per week, with a focus on the bug triage. |
| | | | |
| − | ----- | + | The community meeting was important to raise issues/awareness or continue discussions on certain topics. |
| | + | Over time, we realized most of the discussions are happening live on the #openstack-ansible channel, so a formal meeting was not required anymore: |
| | + | the meeting became be a place where people had to repeat what they said on the channel, with the hope of having more visibility and logging the conversation. |
| | | | |
| − | == Regular attendees ==
| + | To avoid repetitions, and still raise awareness of topics, '''anyone can add on this page''' in the section "Agenda", a link to a discussion that happened on the mailing lists, etherpads, or on IRC. |
| | | | |
| − | Add yourself to this list to be pinged prior to each meeting (Please use your <code>irc_handle</code>):
| + | Each meeting will start by giving the links to the discussions, for the record. |
| | + | If any further discussion is required, it can be done after the triage of the bugs. |
| | | | |
| − | * cloudnull, mattt, andymccr, d34dh0r53, hughsaunders, b3rnard0, palendae, Sam-I-Am, odyssey4me, serverascode, rromans, mancdaz, dolphm, _shaps_, BjoernT, claco, echiu, dstanek, jwagner
| + | == Agenda == |
| | | | |
| − | -----
| + | The meeting is split in the following parts: |
| | | | |
| − | == Agenda for next meeting ==
| + | * rollcall |
| | + | * what happened since last meeting |
| | + | * open discussion |
| | + | * bug triage |
| | | | |
| − | Please feel free to add items to the agenda below with your <code>name</code> or <code>irc_handle</code> and we'll cover them.
| + | === Start meeting and rollcall === |
| − | * Agenda & rollcall
| |
| − | * Review action items from last week
| |
| − | * Blueprints
| |
| − | ** Developer docs https://blueprints.launchpad.net/openstack-ansible/+spec/developer-docs / https://review.openstack.org/#/c/173155/. Specifically, a section was added to discuss extending os-ansible-deployment. This spec is now in its final draft. - <code>Nolan Brubaker / palendae</code>
| |
| − | * Reviews
| |
| − | ** Adding Sphinx machinery for developer docs https://review.openstack.org/#/c/178503/ - <code>Nolan Brubaker / palendae</code>
| |
| − | * Bugs
| |
| − | * Milestones
| |
| − | * Open discussion
| |
| | | | |
| − | -----
| + | <code><nowiki> #startmeeting openstack_ansible_meeting </nowiki></code> |
| | + | |
| | + | <code><nowiki> #topic rollcall </nowiki></code> |
| | | | |
| | == Previous meetings & logs == | | == Previous meetings & logs == |
| | | | |
| − | * Meeting #15 | Weekly Meeting | 5 May 2015 | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-05-07-16.00.log.html logs] | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-05-07-16.00.html summary]
| + | Our new meeting logs and details can be found here: [http://eavesdrop.openstack.org/#OpenStack_Ansible_Deployment_Meeting] |
| − | * Bug triage #15 | 5 May 2015 | [https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-05-05-16.00 notes]
| + | |
| − | * Meeting #14 | Weekly Meeting | 30 April 2015 | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-04-30-16.01.log.html logs] | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-04-30-16.01.html summary]
| + | === Meetbot Commands === |
| − | * Bug triage #14 | 28 April 2015 | [https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-04-28-16.00 notes]
| + | |
| − | * Meeting #13 | Weekly Meeting | 23 April 2015 | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-04-23-16.03.log.html logs] | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-04-23-16.03.html summary]
| + | Please see the startmeeting command above. |
| − | * Bug triage #13 | 21 April 2015 | [https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-04-21-16.00 notes]
| |
| − | * Meeting #12 | Weekly Meeting | 16 April 2015 | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-04-16-16.00.log.html logs] | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-04-16-16.00.html summary]
| |
| − | * Bug triage #12 | 14 April 2015 | [https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-04-14-16.00 notes]
| |
| − | * Meeting #11 | Weekly Meeting | 9 April 2015 | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-04-09-16.00.log.html logs] | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-04-09-16.00.html summary]
| |
| − | * Bug triage #11 | 7 April 2015 | [https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-04-07-16.00 notes]
| |
| − | * Meeting #10 | Weekly Meeting | 2 April 2015 | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-04-02-16.02.log.html logs] | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-04-02-16.02.html summary]
| |
| − | * Bug triage #10 | 31 March 2015 | [https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-03-31-16.00 notes]
| |
| − | * Meeting #9 | Weekly Meeting | 26 March 2015 | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-03-26-16.01.log.html logs] | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-03-26-16.01.html summary]
| |
| − | * Bug triage #9 | 24 March 2015 | [https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-03-24-16.00 notes]
| |
| − | * Bug triage #8 | 17 March 2015 | [https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-03-17-16.00 notes]
| |
| − | * Meeting #8 | Weekly Meeting | 12 March 2015 | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-03-12-16.00.log.html logs] | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-03-12-16.00.html summary]
| |
| − | * Bug triage #7 | 10 March 2015 | [https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-03-10-16.00 notes]
| |
| − | * Meeting #7 | Weekly Meeting | 5 March 2015 | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-03-05-16.02.log.html logs] | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-03-05-16.02.html summary]
| |
| − | * Bug triage #6 | 3 March 2015 | [https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-03-03-16.00 notes]
| |
| − | * Meeting #6 | Weekly Meeting | 26 February 2015 | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-26-16.02.log.html logs] | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-26-16.02.html summary]
| |
| − | * Bug triage #5 | 24 February 2015 | [https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-02-24-16.00 notes]
| |
| − | * Meeting #6 | Weekly Meeting | 19 February 2015 | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-19-16.01.log.html logs] | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-19-16.01.html summary]
| |
| − | * Bug triage #4 | 17 February 2015 | [https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-02-17-16.00 notes]
| |
| − | * Meeting #6 | Weekly Meeting | 12 February 2015 | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-12-16.00.log.html logs] | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-12-16.00.html summary]
| |
| − | * Bug triage #3 | 10 February 2015 | [https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-02-10-16.00 notes]
| |
| − | * Meeting #5 | Weekly Meeting | 5 February 2015 | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-05-16.00.log.html logs] | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-02-05-16.00.html summary]
| |
| − | * Meeting #4 | Weekly Meeting | 29 January 2015 | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-01-29-16.00.log.html logs] | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-01-29-16.00.html summary]
| |
| − | * Bug triage #1 | 27 January 2015 | [https://etherpad.openstack.org/p/openstack_ansible_bug_triage.2015-01-27-16.00 notes]
| |
| − | * Meeting #3 | Weekly Meeting | 22 January 2015 | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-01-22-16.00.log.html logs] | [http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-01-22-16.00.html summary]
| |
| − | * Meeting #2 | Weekly Meeting | 15 January 2015 | [https://etherpad.openstack.org/p/openstack-ansible_meeting.2015-01-15-16.00 agenda] | [http://eavesdrop.openstack.org/meetings/openstack_ansible/2015/openstack_ansible.2015-01-15-15.57.log.html logs] | [http://eavesdrop.openstack.org/meetings/openstack_ansible/2015/openstack_ansible.2015-01-15-15.57.html summary]
| |
| − | * Meeting #1 | Weekly Meeting | 18 December 2014 | [https://etherpad.openstack.org/p/meeting2-os-ansible-deployment agenda]
| |
| | | | |
| − | === Agenda Archives ===
| + | Additional commands: [https://github.com/openstack-infra/meetbot/blob/master/doc/Manual.txt Meetbot Manual] |
| − | Previous agendas are archived here: [https://etherpad.openstack.org/p/openstack-ansible-meeting-agenda-archives agenda archives]
| |
If you're interested in Ansible deploying OpenStack, we hold a public meetings weekly.
Historically, we had two meetings per week: One community meeting, and one bug triage meeting. Due to the lower attendance of both of those, we
reduced the amount of meetings to one per week, with a focus on the bug triage.
The community meeting was important to raise issues/awareness or continue discussions on certain topics.
Over time, we realized most of the discussions are happening live on the #openstack-ansible channel, so a formal meeting was not required anymore:
the meeting became be a place where people had to repeat what they said on the channel, with the hope of having more visibility and logging the conversation.
Each meeting will start by giving the links to the discussions, for the record.
If any further discussion is required, it can be done after the triage of the bugs.
