Difference between revisions of "Puppet/PTL"
< Puppet
(→Meetings organisation) |
|||
| Line 15: | Line 15: | ||
== Maintain a list of active subject and directions like a backlog == | == Maintain a list of active subject and directions like a backlog == | ||
This was already managed by our [https://trello.com/b/4X3zxWRZ/on-going-effort Trello board], and have a clear vision of where we are going on. | This was already managed by our [https://trello.com/b/4X3zxWRZ/on-going-effort Trello board], and have a clear vision of where we are going on. | ||
| + | |||
| + | == OpenStack Cross-Project liaison == | ||
| + | Communicate with other OpenStack projects when needed and attend [[Meetings/CrossProjectMeeting]]. | ||
Revision as of 02:49, 15 September 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 organization
- Publish a meeting agenda a minimum one day before the meeting on openstack-dev mailing list.
- Orchestrate the meeting to make sure timing is respected, topics are covered and take notes of taken actions.
- 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.
OpenStack Cross-Project liaison
Communicate with other OpenStack projects when needed and attend Meetings/CrossProjectMeeting.
