matrix-org / matrix-org/matrix.org
Document criteria for "client" ecosystem project type
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 616
- Forks
- 463
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 19
Description
As a part of a wider effort, let's define what we are referring to when we use the term "client" within the context of the ecosystem project pages.
> [!IMPORTANT]
> The criteria documented here are very much a work in progress. If you’re looking to provide feedback, please remember that this comment is a living document. Quote the specific section you want to discuss, as it may be edited or removed.
- ...
Contributor 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.
Research direction
The issue does not name a file or test; start by locating the ecosystem project pages and the current uses of “client” on the matrix.org site. Review the living criteria in the issue and document a clear definition for this project type, with the page content reflecting the resulting criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100