Greeting yt developers,First, I want to congratulate everyone here on the successful releaseof yt-3.0. This was a massive effort on the part of so many and atrue testament to the strength of this team.At the time of writing this, there are 78 members of the yt-devmailing list. As someone who does most of their work in very smallcollaborations, this amazes me and make me very proud. In case you'rewondering, the yt-users list has 268 members.As a project, yt has a significant amount of infrastructure: codereview with pull requests, issue tracking, automated testing, emailslists, an IRC channel, enhancement proposals, workshops. All of thisis evidence of our legitimacy as a Real Thing. However, one bigmissing piece is a system of governance. I don't know exactly whatthis means, but I have some ideas, which I will share below. What Iwant to do right now is to start a discussion that will, hopefully,include as many people as possible on this list.For me, governance means (roughly) the following:- a set of procedures in writing for how various things are to bedone, such as acceptance of pull requests, releases, designatingdevelopers as core contributors, etc.
- a governing body to make decisions and help guide the project.
This accomplishes a number of things, which as a project I think weneed, such as:- overall stability of the project.- providing a system for conflict resolution.- maintaining the spirit of yt as a team effort.- providing a way for active contributors to get credit for theircontribution in the form of official recognition.
So, these are my initial thoughts, but I really think this deserves athorough discussion with as many people participating as possible.Please, think about what governance means to you, whether we need it,what it should be, and what we might get out of it, and share yourthoughts over the next few days. I look forward to this discussion.Britton
yt-dev mailing list