Requirement clarification and recommendation
Open
@jmertic is already working on this.
Since May 28, 2025.
Assessment
This issue has not been assessed yet.
Description
In the Readme, the criteria for a repo to be considered for the Landscape were a bit confusing to me:
- Projects with at least 300 GitHub stars that clearly fit in an existing category are generally included. Put the project in the single category where it best fits.
- Projects that clearly fit in an existing category are generally included. Put the project in the single category where it best fits. We are unlikely to create a new category for projects as we'd rather find the best home with the current options.
- Projects a logo, and the logo needs to include the name.
Questions:
- Is the "at least 300 GitHub stars" an actual requirement?
- The last bullet requires an update: probably "The project requires a logo that includes the name."
- Dominant language
- No language data
- Stars
- 326
- Forks
- 116
- Avg merge
- 1m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.