Documentation needs to be changed to include these projects as they become useful.
Some example names for a section would be:
Awesome jecs projects
Related projects
etc
Within this documentation, there should be a brief description on what these projects do, why they exist, and links to either the project repo or additional documentation as necessary.
Alternatives
An alternative is to have a GitHub team which hosts the useful projects and is open for others to contribute to. This is ideal for centralizing projects and guaranteeing that they all work together, but can also take much more effort than just adding related projects to a documentation page.
EncodedVenom
commented
3 weeks ago
This is a meta-issue discussing how related projects should be handled, and as such will not be following the current templates.
Motivation
There are a number of jecs projects that are intrinsically related and useful for jecs, but are not part of the main project.
Such examples: #104, change tracker implementations, and several more in the jecs thread on the ROSS server.
Current Proposed Solution
Documentation needs to be changed to include these projects as they become useful. Some example names for a section would be:
Within this documentation, there should be a brief description on what these projects do, why they exist, and links to either the project repo or additional documentation as necessary.
Alternatives
An alternative is to have a GitHub team which hosts the useful projects and is open for others to contribute to. This is ideal for centralizing projects and guaranteeing that they all work together, but can also take much more effort than just adding related projects to a documentation page.