Replies: 11 comments
-
|
The Digital Assets Management Working Group Charter was voted on and approved, so now the group can start working.
|
Beta Was this translation helpful? Give feedback.
-
|
The Technical Interoperability and End-User Troubleshooting Exploratory Group Charter was voted on and approved:
|
Beta Was this translation helpful? Give feedback.
-
|
This slide defines the term "SSO" more clearly and includes different pathways toward more inclusive SSO participation. For example, OMI could be considred an SSO and would perhaps come under the "Principal Fee Waiver for SSOs" category. Also, it's interesting to note that the following addition of text was based on some suggestions by OMI folks (re: the basis of it was the draft of the no-dues criteria document:
While the language is different, the addition of the above sentence directly relates to OMI. Neil also gave OMI a shout-out and expressed that we/MSF must be mindful of making space for / including community organizations that are involved in standards setting (like OMI) when creating policies like this. (Yay!)
There was also discussion of what pathways there might be for an individual to join MSF -- and the addition of the "individual expert" category, which would be an option subject to MSF board discretion. Based on some discussions in today's MSF-delegates meeting amongst @funksoup @JoyceBettencourt @evo @humbletim @fire and others -- I (@funksoup) suggested that it would be beneficial to clarify what that pathway would entail: what would be the criteria for an 'expert' and what would the process be? Also mentioned that having OMI as the 'first stop' before someone pursued the 'indivudual expert' category wasn't necessarily a solid option since 1. that might dilute that individual's voting power (i.e., an organization gets one vote vs an individual gets one vote), and 2. funneling everyone who wants to participate to OMI would be a huge administrative lift for OMI --> therefore, a pathway for individuals to join must be clarified. Neil and folks agreed but also acknowledged that that would be a larger effort that they/Khronos would like to tackle after incorporating, as it may take several months to define, and the deadline for incorporation is in March (next month). All in all, it was still a very positive and productive discussion, as the general trend of the last few weeks' discussions has gotten more and more inclusive. |
Beta Was this translation helpful? Give feedback.
-
Metaverse Standards Forum: Oversight
Wednesday, 22 February 2023 from 21:00-22:30 EST (02:00-03:30 UTC)
Agenda:
Mobile World Congress Member Meetup and Outreach Event
Domain Group Pipeline
Incorporation Update
--> Google slides<--
--> Slides as PDF<--
Beta Was this translation helpful? Give feedback.
All reactions