# OMI Weekly Meeting 10 6/30/2021 ## From [Github Discussions](https://github.com/omigroup/OMI/discussions/52) Weekly Meeting 10 is happening on Wednesday 6/30/2021 from 9:00 AM PDT - 10:00 AM PDT You can add it to your calendar [here](https://calendar.google.com/calendar/u/1?cid=Y18wZHB1Z2Y5ZjgzZXE0cWVrbWI2b21xYmptZ0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t). We'll be meeting again in the omi-weekly-meeting channel of the [AngellXR Discord](https://discord.gg/NJtT9grz5E). ## Agenda - [OMI Open Collective Fundraising](https://opencollective.com/omigroup) - [OMI Website](https://omigroup.org) ### :wave: Welcome to new contributors / guests ![](https://i.imgur.com/XIK1F2A.png) - And drew stone (**stonedrew**) joined introduced themself in the end of the meeting! - ![](https://i.imgur.com/vaM6fM3.png) ### :fuelpump: Open Collective Application Evo, Mauve, and Robert worked on the open collective application this week. We received approval for our account. More information can be found from last weeks [OMI 6.24.21 notes](https://hackmd.io/v-lpn9rxRdms1u5vwcGfUw)and the meeting recording as well. https://opencollective.com/omigroup Fiscal sponsor application accepted! We can now take donations and can give out grants and allocate our budget for various activities. ### :spider_web: The OMI Website is coming along: https://omigroup.org/ We've got Docusaurus set up and anyone can contribute to the site by submitting a pull request to the website repo: https://github.com/omigroup/website ### :lower_left_fountain_pen: Let's write content / resources We could start showcasing members projects, and a number of different metaverse platforms and new features. Could be a great resource for new people coming into the space who want to get a better sense or documentation. We could create the MDN (mozilla dev network) equivalent for the metaverse. A collection of resources in a community driven way. #### :tv: Short form video If anyone has video skills, that would be great... we are looking to make a few short form videos to share on places like twitter. #### :spiral_note_pad: Our previous list of resources We have [put together a list](https://github.com/omigroup/OMI/discussions/12) previously on github discussions. We may want to revise, and then publish this. ### A few small things #### Need more :stars: To speed up our fiscal sponsor process, we also need to get to 100 stars on our OMI GitHub repository. If you haven't starred our repo yet, help us out and give us a star: :star: https://github.com/omigroup/OMI #### :joystick: Last weeks HH was a blast! Some OMI members got together on Friday to play jackbox, and a little gorilla tag. #### :european_castle: Our meeting space Matt (**mbcool**) has submitted the first draft of some OMI meeting space assets. [![](https://i.imgur.com/Wx1eVff.png) ](https://hubs.mozilla.com/Y2F5wPX/omi-asset-testing) ### Virtual World URI's source: [github pages](https://github.com/omigroup/OMI/discussions/23) We have been exploring the protocol Webfinger for experimentation. This is useful for giving associated links for a given identifier. So if you have a URI of any virtual world that meets this spec, you should be able to get metadata about that world. Main use case would be for portal in interoperable worlds. Leveraging 360 images or projections. We are looking to get this info in one place, and write a concrete proposal as a github issue, and then we need multiple adopters. > ## If you are a platform owner, and you're interested in adopting this protocol for your world, please reach out to us. Regarding webfinger: We are not set in stone about any solution. We are looking to experiment, and will wait to put our stamp of approval or formal recommendations after testing, adoption, and refinement. We are always looking for alternative proposals and perspectives. We ask that all members submit alternatives through github discussions. **:question: Is this 'spec' more about the technical frameworks, or the UX design or something else?** We would like to be able to render 3d thumbnails essentially. ### GLTF content portability Robert, iFire, gFodor and some others have been talking about exending gltf capabilities. (tried to capture everything I could :sweat_smile:) Make GLTF scenes into richer metaverse assets. We need to create JSON schema, and a reference. We can experiment in our own repo to ensure we have everything before submitting to the [glTF Extension Registry](https://github.com/KhronosGroup/glTF/blob/master/extensions/README.md) We may want an OMI vendor prefix for OMI led extensions, but we can also include extensions led by specific vendors in this repository. We need to be careful about what extensions we want to standardize. Things can quickly become too complex or be too specific for a single platform. We want to focus on extensions with broad appeal first. These extensions should also not require scripting. #### possible glTF extensions * sound emitters - Spatial (panning), 2D (background music?) * colliders - capsule, sphere, box, Mesh??, Cylinder?? * physics (rigid bodies) - based on blender? bullet? * physics (fixed joints, spring joints?) - based on ??? * position, rotation, scale constraints - based on blender * hot spots (such as spawn points) - nodes with metadata? do we need a spec for metadata ## Additional comments: - Drew Stone introduced themself - Maybe we can create a virtual stage - Did we miss anything? If you have additional comments or questions or suggestions please reach out to Jesse, Evo or Robert.