By the way, for anybody following along, here is the calendar item link: https://calendar.google.com/calendar/event?eid=X2R0bDQ2cHBlNjRyM2djcG82Z3NqaWQ5bDYwcTNjZGhpNjRwamljaGVhMTQzZ3RhMGRoa242dDNqNXBnbjZ0cjY1cGttdSBpdWdndW81ZWtlb29kanBvY201b2gwODViMmQ4djdyYkBp
> On May 11, 2023, at 9:08 PM, Larry Gritz <l...@larrygritz.com> wrote: > > Please excuse the spam and risk of being off-topic, but I think people in > this community have a lot of overlap with OpenImageIO and so may be > interested stakeholders. > > As many of you know, OpenImageIO has been admitted as an ASWF project. One of > the next steps is to form the Technical Steering Committee (TSC), which is > the formal leadership of the project. > > If you or your organization, product, or software project have OIIO as a > major dependency or are power users, then congratulations -- you are a > stakeholder! Please consider also being a contributor in some way, up to and > including being on the TSC. > > We have scheduled the first meeting for Monday, May 22, at 2pm PDT, over > Zoom. This is an open meeting and all stakeholders are welcome. TSC meetings > are likely to be ongoing and every two weeks, as is typical for these groups > (day and time TBD, it doesn't have to be this slot, will depend on what is > most convenient for TSC members). I don't have the zoom link yet, but the > ASWF calendar is here https://www.aswf.io/meeting-calendar/ and so watch that > space for this meeting to show up in the next day or so (or you can email me > or John Mertic directly to ensure you get an invite). > > The most important items on the agenda for this first meeting will be: > * Actually formalizing who will comprise the TSC (the only prerequisite is > being a stakeholder with a willingness to participate on an ongoing basis), > and to the extent possible, mapping out which tasks or topics might fall into > the wheelhouse of different participants. > * Officially voting (if we can reach agreement) to ratify the charter, choose > a chair, lock down the choice of license and CLA, and other such matters. > * Reviewing and doling out administrative tasks that need to happen to > complete the project intake and get us up to speed as an operating ASWF > project. > > You don't need to be a prolific contributor of code to be on the TSC (though > it's best if *most* TSC members are also committed to actually working on the > code to some degree). Nor do you need to be a TSC member to work, even > extensively, on the code. And you don't need to be a TSC member to attend > meetings or even to be a major force in helping to steer the project. It is > actually very seldom that we do something that requires a formal TSC vote. > > It's also worth noting that TSC membership is not a lifelong obligation. > People's jobs, responsibilities, and time commitments change over time, so > it's fine to turn your seat over to a different person at your organization > when circumstances change, or even to start out knowing that you are > temporary and a more suitable long-term replacement will be substituted at > some point. > > I hope to see some of you at the meeting. > > -- > Larry Gritz > l...@larrygritz.com > > > > > -- Larry Gritz l...@larrygritz.com
_______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
