blob: 5f13a1a3fe9ed6b2f6bac1bbf5328003d5c05fb1 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
=========
PTL Guide
=========
This is just a reference guide that a PTL may use as an aid, if they choose.
It is meant to complement the `official PTL guide
<https://docs.openstack.org/project-team-guide/ptl.html>`__, and is laid out in
rough chronological order.
Some or all of these tasks may be delegated to other team members.
New PTL
=======
* Update the kolla meeting chair
* https://opendev.org/opendev/irc-meetings/src/branch/master/meetings/kolla-team-meeting.yaml
* Update the team wiki
* https://wiki.openstack.org/wiki/Kolla#Active_Contributors
* Get acquainted with the release schedule, bearing in mind that Kolla is a
cycle-trailing project
* Example: https://releases.openstack.org/train/schedule.html
Open Infrastructure Summit
==========================
Ideally the Kolla PTL will be able to attend the summit. If not, try to arrange
for another member of the core team to represent the team. Good interaction
with the community at these events is crucial to encourage upstream
involvement, onboard new users, collect feedback and for the perceived health
of the project.
* Create a summit planning etherpad and alert about it in the kolla IRC meeting
and openstack-discuss mailing list
* Example: https://etherpad.openstack.org/p/kolla-train-summit
* Gather ideas for forum sessions
* Example: user feedback & roadmap, design sessions
* Prepare the project update presentation. Enlist help of others
* Prepare the on-boarding session materials. Enlist help of others
* Represent and promote the project while at the summit
Project Team Gathering (PTG)
============================
Some of the Kolla team may decide to meet in person at the Project Team
Gathering (PTG). Alternatively, they may decide to host a virtual PTG at a
different time if there is not a critical mass of contributors attending the
PTG.
* Create PTG planning etherpad and alert about it in the
kolla IRC meeting and openstack-discuss mailing list
* Example: https://etherpad.openstack.org/p/kolla-train-ptg
* Run sessions at the PTG
* Have a discussion about priorities for the upcoming release cycle at the PTG
* Sign up for group photo at the PTG (if applicable)
After Summit & PTG
==================
* Send session summaries to the openstack-discuss mailing list
* Update the `Kolla whiteboard
<https://etherpad.openstack.org/p/KollaWhiteBoard>`__ with decided priorities
for the upcoming release cycle
Day to Day
==========
* Subscribe to the kolla projects on Launchpad to receive all bug and blueprint
updates.
* :doc:`Triage new bugs <bug-triage>`
* Monitor the status of the CI system for all supported branches. Fix issues
that break the gate
* Chair the IRC meetings
* Be available in IRC to help new and existing contributors
* Keep track of the progress of cycle priorites
* Monitor the core team membership, mentor potential cores
Release Management
==================
* Follow the project's :doc:`release management <release-management>` guide
* Use the IRC meeting and/or mailing list to communicate release schedule to
the team who might not be so famailiar with it
Handing Over
============
* Support the new PTL in their new role. Try to remember the issues you
encountered
* Update this page with any useful information you have learned
|
