---- On Mon, 10 Sep 2018 20:31:11 +0900 Doug Hellmann <d...@doughellmann.com> wrote ---- > Excerpts from jean-phili...@evrard.me's message of 2018-09-10 13:15:02 +0200: > > Hello everyone, > > > > In my candidacy [1], I mentioned that the TC should provide more tools to > > help the PTLs at their duties, for example to track community health. > > > > I have questions for the TC candidates: > > - What is your opinion about said toolkit? Do you see a purpose for it? > > - Do you think said toolkit should fall under the TC umbrella? > > > > After my discussion with Rico Lin (PTL of the Heat project, and TC > > candidate) yesterday, I am personally convinced that it would be a good > > idea, and that we should have those tools: As a PTL (but also any person > > interested to see health of projects) I wanted it and I am not alone. PTLs > > are focusing on their duties and, as a day is only composed of so few > > hours, it is possible they won't have the focus to work on said tools to > > track, in the longer term, the community. > > > > For me, tracking community health (and therefore a toolkit for the > > PTLs/community) is something TC should cover for good governance, and I am > > not aware of any tooling extracting metrics that can be easily visible and > > used by anyone. If each project started to have their own implementation > > of tools, it would be opposite to one of my other goals, which is the > > simplification of OpenStack. > > > > Thanks for reading me, and do not hesitate to ask me questions on the > > mailing lists, or in real life during the PTG! > > > > Regards, > > Jean-Philippe Evrard (evrardjp) > > > > [1]: > > https://git.openstack.org/cgit/openstack/election/plain/candidates/stein/TC/jean-phili...@evrard.me > > > > We've had several different sets of scripts at different times to > extract review statistics from gerrit. Is that the sort of thing you > mean? > > What information would you find useful?
Yeah, if we can have exact requirement or Action items PTL miss then, it will be more clear about having such tooling. Overall I like the idea of giving more awareness about PTL work but that is more kind of teaching and guiding the PTL. Before we think of tool to manage PTL responsibility, we need to list down the issues it will solve. Personally as PTL, I have gone through PTL responsibility guide[1] and filtered the PTL tagged email which i daily check on priority. Further I follow the TODO things PTL has to do in release, PTG, Summit etc. which work perfectly for me. I find this more PTL responsibility than TC track those for PTL. That's my point of view as PTL and as TC candidate but i would like to hear from other PTLs on this if they need help on their responsibility tracking and why. [1] https://docs.openstack.org/project-team-guide/ptl.html > > Doug > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
