Contributors of the project :)
- Dominant language
- TypeScript
- Stars
- 72.7k
- Forks
- 8.6k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 83
Description
So, i spend some time on testing and experimenting with the project, alot of things need testing and i provide issues back that claude code swarms are analysing and fixing.
I agreen that the people running these swarms and provide the fixes are the contributors - but i am also thinking that with the way this is done there are also alot of contribution value in providing issues for AI to fix even though its not us running the swarms. I also agree that there are a cost to running a swarm that i dont have a solution to but i do think we need a way to attribute those peolpe who provide good issues that helps the AI transforming this from a mock to real @ruvnet ;)
Dont know how to solve that other than i have to setup my development flow to also go implement my own issues :D
Contributor guide
Research direction
The issue discusses recognizing people who report useful issues alongside contributors who implement fixes, but it names no files, tests, or entry points. Start by clarifying the desired attribution model and where contributor records are maintained; done would require an agreed design and an explicitly defined implementation scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100