m3
webaverse
The README.md is the front face of any open source project. The goal for this sprint is to create a beautiful easy to follow README for repos creators can engage with soonest. It should contain a visual of what's inside and be easy to quickly get started with the information. If they need help, there should be links on where to look for more info / community.
Pick your class
For contributors that are achieving results they can be eligible to level up and ascend the ladder. We can feature roles on Dework front and center as a way to overview classes like in an MMO and motivate people to play to level up.
Increased compensation
Increased status / reputation
There's 467 repositories in the Webaverse Github and 88 in the Webaverse-studios Github. It's not clear what the relation is between the projects. I suggest there be some kind of massive overview initiative first to map out the relations between repos and visualize them as such into a better interface than the default GitHub one.
Ideas:
It should be easy for a person to get a development environment setup for testing and documenting everything else. Right now it's confusing as to which repo to use. Maybe it will be that way for awhile, but atleast a MVP client would be useful in creating READMEs and helping with QA later.
apps
guides
Note: This does not need to be something super polished like a video game manual right now, it just needs to be usable to get the other READMEs done which can feed back into this later.
This is long overdue for a README. Pets are coming to many platforms, Animus from RTFKT and 3D tubby cats are almost ready to be made.
One could create their own weapons in Webaverse and there's been a multitude of different types from baseball bats to pistols and rocket launchers. However, there have been no READMEs in any of these templates which makes it confusing and difficult for a curious creator.
Another reason this is 2nd on my list is because we are done 3D modeling all of the weapons in the Anata project which can provide beautiful new assets to use in templates:
Lastly, other platforms such as Hyperfy have implemented weapons making this an interesting case study for avatar wearables, which is one of the big things we're we're focusing on in Metaverse Standards Forum: https://github.com/MetaverseStandards/Avatar-Wearables
There's been recent interest in interoperable vehicles / physics in metaverse working groups like the OMI gltf-extensions group.
With other platforms implementing vehicles, having documentation about how to create your own in Webaverse would aid metaverse standards working groups.