Relationship between this repo and maintained version at C-Frame/aframe-particle-system-component

[diarmidmackenzie]

For a few years that A-Frame component ecosystem has had problems with community components falling out of date, which can lead to components that don't work correctly with the latest versions of A-Frame.

To help solve this problem, a group of us have come together to create C-Frame, a community organization that is committed to maintaining up-to-date versions of popular A-Frame components.

We've recently created a C-Frame fork of this repo, and brought it up-to-date so that it works with A-Frame 1.4.1. This addresses a longstanding community issue of there not being a reliable up-to-date version of this component available.

We will shortly also publish this to npm @c-frame/aframe-particle-system-component.

We'd like some input from the maintainers of this repo (@weddingdj and perhaps others?) about the right relationship between the two repos going forwards.

Would you be willing to consider either of the following?

1. Transfer this repo to C-Frame. We'll merge in the changes in our fork and then transfer this repo across. Happy for current maintainers of this repo to retain access.

2. Add a banner notice at the top of the readme of this repo, pointing to the C-Frame repo as a place to get the latest maintained code. If you prefer this approach, I'll create a suitable PR.

As well as the GitHub repo, there's also a question of the code on npm. The package at npm/aframe-particle-system is currently out of date, and it would be great to publish a working version on npm. Alternatively, we'd like to at least ensure that the npm page for aframe-particle-system points to a working npm version at @c-frame/aframe-particle-system, which could be done by pushing this repo to npm after making a suitable update to the readme.