TSC meeting schedule The next TSC meeting is Monday, June 5, 2-3pm PDT, and (for now, anyway) repeats every 2 weeks at that day/time. See the https://www.aswf.io/meeting-calendar/ to get zoom link or add it to your calendar.
Reminder: TSC meetings are open Zoom meetings, anybody interested in the project may attend and participate. It's actually quite rare that anything we do in TSC meetings needs a formal vote in which only the official members count -- generally only elections and major organizational policy matters. Everything else is decided by discussion and consensus among whoever bothers to show up and participate. Reminder #2: It's not too late to volunteer yourself to be on the formal TSC. Also, it's fine to come to a few meetings to get the feel of what they're about before committing. Also, it's fine to be a major steerer or code contributor without holding a TSC seat. Recap of the initial TSC meeting on 22 May 2023 25 attendees, yay! Choose a chair: OCIO and OSL have had success splitting the leadership role into separate chair (run the meetings, set the agenda, represent us at the TSC and externally, healthy for the role to rotate among people from time to time), and chief architect (direct the design and implementation of the software, should be long-term stable to the extent possible). We agreed by consensus that this division of labour made sense for us as well. Larry Gritz volunteered as architect and Danny Greenstein (SPI) accepted nomination to be chair (at least for a few months while the project gets on its feet, then will decide if it makes sense to stay in the role). Both roles were approved by all present. CLA: after discussion, consensus emerged that having a CLA helps some organizations approve use and participation. It was resolved to use the standard ASWF CLA that most other projects use and which is based on the Apache CLA. License: The project has historically used BSD-3-clause. Current standard preferred for new projects is Apache 2.0, and there are some advantages to that if it's not too hard to change, and doing so now is the least painful time. We resolved to ask LF to advise what we would need to do to transition to Apache 2.0. (Larry, John, and LF will follow up.) Meeting schedule: We resolved to try meeting at this same time (Mondays 2pm PT, every second week),with the ability to change or rotate times if we find it's not working out (which could be because of holidays often falling on Mondays, or because time of day is inconvenient for certain parts of the world). TSC members: we didn't settle on TSC members. Follow-up: Larry will pencil in the people who previously seemed to volunteer, and we'll edit from there. Progress since then: Formal ownership transfer: LG is working with LF on this. License policy: LG, Danny, John Mertic met with LF VP of new projects about licensing. He said it's straightforward to have new code come in as Apache 2.0 and to relicense old code as the opportunity arises. The overhead is that we'd need to take some care to document which files or parts are BSD, Apache, or a mix. It is already known that 95% of the lines of code come from 6 authors, 99% of code from 30 authors. Danny is also investigating by file -- if LG and a fairly small number of the next several largest committers relicense, are most of the source files Apache 2.0 and only a small number need to be labeled as complicated mixes? We will report back. LF will provide us with (a) revised project charter to reflect the proposed licensing policy, (b) instructions for how to relicense old contributions, (c) what language to use to label the files and sections correctly. Logo: the exiting, newly designed logo has been deposited with the foundation: https://artwork.aswf.io/projects/openimageio/ Meeting is on the ASWF meeting calendar: https://www.aswf.io/meeting-calendar/ Slack channel #openimageio is set up on the ASWF slack: https://slack.aswf.io/ Draft documents: LG has a pull request <https://github.com/OpenImageIO/oiio/pull/3850> with the various in-progress draft documents: charter, governance, edited contribution guide, proposed CLAs, code of conduct, project intake checklist. Community members and TSC members should feel free to voice concerns, suggestions, or approval on the PR itself. LG will merge soon (they are still all in draft form and don't take effect until ratified by the TSC and in some cases only when the repo is finally moved to ASWF's account), after which point further suggestions should be made via additional PR or issue. VTH/BOF: We are signed up for a pre-SIGGRAPH "virtual town hall" for Tue Aug 1, 3-4pm PT. We do not have plans for a formal BOF at SIGGRAPH. Action items for TSC and next meeting agenda: Approve project charter, if the final proposed language is ready. Approve the plan for licensing/relicensing policy and CLA. Approve other documents (governance, CoC, etc.), or give everybody homework to read them in time to vote or suggest changes by the next meeting. Review who appears to be on the TSC, who else volunteers or should be asked, try to reach a "final initial" TSC roster. Make plan for what to do/say at the virtual town hall. Once CLA and licensing get approved, discuss schedule for moving the repository and having new CLAs signed. Discuss schedule for the mail list switchover. Should we turn on DCO requirement now (even before repo is transferred) to get people used to signing off on commits? -- Larry Gritz l...@larrygritz.com
_______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
