c-frame registry

[Fabien Benetou]

The registry https://github.com/aframevr/aframe-registry is not maintained anymore. Yet, it does provide an interesting perspective, namely to both track documented maintained components and provide an efficient way to integrate them, something very useful to other tools, e.g the https://github.com/aframevr/aframe-inspector . In fact IMHO community made and maintained components themselves, now that core works (being in 1.x), is the most important aspect of AFrame.

Maintaining the official AFrame registry itself was unfortunately not a sucess for multiple reasons. Among these reasons arguably centralization was a problem as it was demanding already busy maintainers to keep track of things that were, by definition, not the core of the project.

Consequently it could be interesting to revive the registry but from the lessons learned from this. I believe this would mean pursue the c-frame perspective, as in not being part of AFrame itself. That means that the c-frame registry would not be "the" canonical registry but rather the first one among possibly many. It could even follow a federated model but I would suggest only as a 2nd step, where each project maintains and make publicly available its registry.yml file.

[Vincent Fretin]

For now we maintain https://aframe.wiki/en/#!pages/component-directory.md
If you want to edit it, create a first PR for the file and I'll add you as member of the repo so you can push right away next time
https://github.com/c-frame/aframewiki/blob/gh-pages/en/pages/component-directory.md

[Vincent Fretin]

Actually I just sent you an invite to the c-frame organization, you can edit the wiki and create new repositories in the organization.