Hi, I'm currently trying to put together a draft project governance document that, most importantly, lists the actual TSC members.
At the TSC meeting earlier this week, those present approved the appointment of: * Danny Greenstein (SPI) as the (interim, and maybe more?) TSC chair and project representative to the ASWF TAC. * Larry Gritz (SPI) as the chief architect. We did not get to name any other members but I believe I have previously received explicit commitments from: * Anton Dukhovnikov (or future designee) - Wētā Digital / Unity * Joseph Goldstone - ARRI * Luke Emrose (or future designee) - Animal Logic * Robin Rowe (Robin, how do you want your affiliation listed?) * Thiago Ize - Autodesk The TSC doesn't need to be huge, but I think the project would be strengthened by adding perhaps another 3-4 people, each from a different company or project among those relying heavily on OpenImageIO, preferably with a diversity of corporate and demographic backgrounds, and including some people new to leadership roles in the ASWF or other open source projects. We had a lot of other attendees at the meeting, but I'm really not sure who was there just to observe and who came intending to volunteer for TSC or other ongoing project involvement. If you would like to make a commitment to serve as a voting member of the TSC (whether or not you attended the first meeting), please speak up here or DM me so I can add you to the list of initial TSC members. For those new to projects with TSCs, it may help to know that the TSC responsibilities include: * Coordinating technical direction of the Project. * Project governance and contribution policy. * GitHub repository administration. * Maintaining the list of additional Committers. * Appointing representatives to work with other open source or open standards communities. * Discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects. * Coordinating any marketing, events, or communications regarding the project. * Addressing issues, responding to user and developer questions, and reviewing code, where your expertise allows. * It is hoped that a substantial number of TSC members will be significant and ongoing maintainers and contributors to the code base (but some will almost never do this, instead concentrating on organizational or advisory duties). It is ok to attend a couple more meetings to see what they're like before committing to serving on the TSC. It is ok to be a consistent and major contributor to the project (in code or any number of other ways) without being a TSC member. It is ok to attend and participate in TSC meetings without being a member (though you would not vote at the very infrequent occasions when a formal vote is needed). It is ok to volunteer now and then un-volunteer later if you realize it's not for you. In short, it's all good, whatever your involvement level turns out to be. But if you represent a major stakeholder, consider making a major commitment. -- Larry Gritz l...@larrygritz.com
_______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
