[This is meant to be one of (I hope) several conversation-provoking questions directed at prospective TC members to help the community understand their positions before considering how to vote in the ongoing election.]
We are discussing adding at least one new project this cycle, and the specific case of Adjutant has brought up questions about the criteria we use for evaluating new projects when they apply to become official. Although the current system does include some well-defined requirements [1], it was also designed to rely on TC members to use their judgement in some other areas, to account for changing circumstances over the life of the project and to reflect the position that governance is not something we can automate away. Without letting the conversation devolve too much into a discussion of Adjutant's case, please talk a little about how you would evaluate a project's application in general. What sorts of things do you consider when deciding whether a project "aligns with the OpenStack Mission," for example? Doug [1] https://governance.openstack.org/tc/reference/new-projects-requirements.html __________________________________________________________________________ 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