Difference between revisions of "Meetings/Puppet/PTL"
(→Meetings organisation) |
|||
| Line 7: | Line 7: | ||
== Meetings organisation == | == Meetings organisation == | ||
We need a chair to ensure that the meeting is correctly orchestrated, the PTL publish also a meeting agenda a minimum 5 days before the meeting (see this example in openstack-tc). | We need a chair to ensure that the meeting is correctly orchestrated, the PTL publish also a meeting agenda a minimum 5 days before the meeting (see this example in openstack-tc). | ||
| − | The PTL also publish meeting notes on the Mailing-list and | + | The PTL also publish meeting notes on the Mailing-list and Wiki (for archive / easy search purposes). |
== Bug triage / management == | == Bug triage / management == | ||
Revision as of 20:35, 2 April 2015
This page is under construction and is not a definitive guide. It does not replace the PTL guide, but aims to add more informations about specific tasks related to our way to work.
Contents
Community group manager
The PTL would keep abreast of upcoming meetings (summits, OPS meetups) where it would be interesting for our community to be represented.
Meetings organisation
We need a chair to ensure that the meeting is correctly orchestrated, the PTL publish also a meeting agenda a minimum 5 days before the meeting (see this example in openstack-tc). The PTL also publish meeting notes on the Mailing-list and Wiki (for archive / easy search purposes).
Bug triage / management
The subject was raised during the lasts meetings, but we are thinking about organizing some bug triage sessions.
Maintain a list of active subject and directions like a backlog
This was already managed by our Trello board, and have a clear vision of where we are going on.
