Difference between revisions of "Puppet/PTL"
< Puppet
| Line 11: | Line 11: | ||
== Bug triage / management == | == Bug triage / management == | ||
| − | + | Keep Launchpad bugs in a sane status, make triage when needed and also organize team triage sessions (during weekly meetings or sprints). | |
| − | == Maintain a list of active subject and directions | + | == Maintain a list of active subject and directions using a backlog == |
| − | + | Make sure our [https://trello.com/b/4X3zxWRZ/on-going-effort Trello board] is regularly updated. | |
== OpenStack Cross-Project liaison == | == OpenStack Cross-Project liaison == | ||
Communicate with other OpenStack projects when needed and attend [[Meetings/CrossProjectMeeting]]. | Communicate with other OpenStack projects when needed and attend [[Meetings/CrossProjectMeeting]]. | ||
Revision as of 02:51, 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
Keep Launchpad bugs in a sane status, make triage when needed and also organize team triage sessions (during weekly meetings or sprints).
Maintain a list of active subject and directions using a backlog
Make sure our Trello board is regularly updated.
OpenStack Cross-Project liaison
Communicate with other OpenStack projects when needed and attend Meetings/CrossProjectMeeting.
