OpenStack health tracker
TC members are attached as liaisons to each of the project teams, SIGs, or UC working groups. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.
Liaisons should monitor their groups by:
- reading meeting logs or participating in meetings
- watching summit "project update" videos
- reading relevant messages on the mailing list
- talking with the PTL, chair, and other group members
- checking contribution rates and review turnaround times
|App Dev Enablement||zaneb|
|Edge/Massively Distributed Clouds||ttx|
|Chef Openstack||pabelanger, mnaser|
|Openstack Charms||ttx, emilien|
|Puppet Openstack||cmurphy, pabelanger|
|Quality Assurance||cdent, fungi|
|Release Management||dhellmann, smcginnis|
|Stable Branch Maintenance||fungi, smcginnis|
- Still uses pycrypto 
- freezer and freezer-web-ui missed the Rocky-2 milestone
- murano and murano-dashboard missed the Rocky-2 milestone
Update 13 June 2018, dhellmann
- Recent US government action against ZTE has had an impact on the team, because ZTE employees are key contributors to the project and the core team. It is unclear how much ZTE will be able to continue to contribute in the future. 
- The murano-core team has members froM AT&T and Mirantis, as well as ZTE.
- Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors
- oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.
- oslo.service has some issues with the WSGI service not working under python3. The plan is to encourage all projects to stop using that feature, deprecate, then remove it.
- taskflow is one of several projects that needs to update to a newer version of networkx, but the API changes in networkx mean reworking some of taskflow. Supporting both versions of the APIs may be complicated.
Update: 12 June 2018, dhellmann
- The team is small, but active and working on recruiting.
- Team produces regular and frequent releases for the maintained libraries
- Team meets weekly using IRC
- Team had both onboarding and project update sessions in Vancouver
- The level of activity within each library varies.
- Several of the libraries are reaching a "stable" state in which they may not see many updates beyond bug fixes. This has spurred a discussion of how to treat projects like that, led by the release management team 
- need more reviewers, badly, as discussed a joint leadership meeting in Vancouver
Update: 14 June 2018, dhellmann
- team has recently lost several members
- most work is really down to 3 people (Matt, Dirk, Tony)
- they work for 3 separate companies, but the team is so small that the diversity measures are questionable
- the changes this cycle to stop syncing requirements should lower the review burden somewhat, but the move to python 3 is going to take some work
- meets regularly
- accomplishments this cycle
- stopped syncing dependencies between projects
- working on networkx upgrade
- uncapped eventlet
- uncapped sphinx
- added optional lower-constraints test jobs for project teams that want them
- searchlight and searchlight-ui missed the Rocky-1 milestone
- Release forced for searchlight and searchlight-ui for the Rocky-2 milestone
- No project update in Vancouver
- Missed rocky-2 milestone
- Questions from some public cloud providers on whether they can count on it
Update: June 12, ttx
- The team changed leadership in Rocky
- The new team is small, but pretty alive and active
- Mostly contributors in China (AWCloud, China Telecom, China Mobile)
- Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
- Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
- Regular weekly meetings, well run with clear documentation of outcomes
- Tracks completion of Rocky community goals
- A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
- Missed Rocky-2 milestone, but mostly due to a misunderstanding of release policy.
- No project update in Vancouver, but was discussed in meeting: sadly no team member was present.
- Reached out to PTL by email on June 12 for additional concerns / questions.
- zaqar and zaqar-ui missed the Rocky-2 milestone
Update: June 13, emilien
Reported issues: none, yet. The team changed leadership in Queens.
- 87 modules touched (+87%)
- 17 languages supported (+6%)
- 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)
- 7 companies support (-22%)
I18n team previously had team meetings but decided to have office hours instead. Usually tracks completion of Rocky community goals. A lot of collaboration with Doc team. Dedicated mailing-list: openstack-i18n - pretty busy Reached out to PTL by email on June 13 for additional concerns / questions.
Update: June 13, emilien
Reported issues: none, yet.
- The team changed leadership in Queens
- Last PTG was virtual
- Most commits in Rocky are from Red Hat
- The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews
- Latest survey shows that Sahara is used in production by 3% of deployments and 8% in test phase. 25% of users are interested by Sahara
- Following goals and releases
- Email sent to PTL on June 13th
Update: June 13, emilien
- Mainly Red Hat. Some contributors from vendors (storage/network plugins)
- Number of contributors / core reviewers always increasing
- Quite healthy, no problem reported so far