projectM-visualizer / projectM-visualizer/projectm
[INFO] Tracking projectM in Downstream Package Ecosystem
Open
Nobody has claimed this yet.
3rd-party-integration
- Dominant language
- C++
- Stars
- 4.5k
- Forks
- 485
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 5
Description
projectm is split into 2 projects (projectm and projectm-eval) on repology:
There is an open request to merge them into 1 project under projectm
Also I have begun to bump downstream repos to update to 4.0.0
Example Alpine testing (see below)
TODO
Contributor guide
No contributing guide indexed for this repository
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
Review the Repology pages for projectm and projectm-eval, then inspect the Alpine package entry and the freshcode.club project record linked in the issue. Confirm the downstream 4.0.0 update status and complete or update the remaining Alpine item in the tracking checklist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100