karma-runner / karma-runner/karma

Call for Contributors

Open
#2,474 42 comments 31 reactions 0 assignees View on GitHub
discuss help wanted type: meta
Dominant language
JavaScript
Stars
12k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

As you might have noticed, I'm struggling to maintain all of the karma eco system. This is why I am asking today for **your** help. If you want to help, please leave comment here so we can get talking. The things that need help the most are

## Issues & Support

- Adding labels to issues
- Responding and asking for more feedback
- Closing outdated and solved issues
- Responding to support and help questions on the issue tracker and stack overflow
- Figuring out if gitter is good or if we should have another support channel
- Investigating issues that have the `needs: investigation` label. Those need confirmation that it is a bug or if it is a support issue.

## Documentation & Website

The documentation is pretty good, but needs updates and additions

- The code in https://github.com/karma-runner/karma-runner.github.com is outdated and needs some work
- Many of the `plus` docs need updating and we don't have them for many plugins
- All the individual plugins need more documentation
- The site needs updating with new content on the front page. Some ideas for this are in #2200

## Code

- Lots of bugs and features that are waiting to be implemented on the issue tracker :)

## Future work

I would like to start discussions around major pain points and improvements in the user experience for karma users. Especially with lessons lerned from tools like Jest and Ava. But also looking to other great testing tools like [pytest](http://docs.pytest.org/en/latest/)

## Maintaining

I can maintain the main repo, but for the many plugins I need help, especially as there are often for tools I don't use or have good experience with.
The major ones are

- karma-slimerjs-launcher
- karma-coffee-preprocessor
- karma-script-launcher
- karma-dart
- karma-opera-launcher
- karma-phantomjs-launcher
- karma-mocha
- karma-teamcity-reporter
- karma-coverage
- karma-chrome-launcher
- karma-requirejs
- karma-ng-html2js-preprocessor
- karma-junit-reporter
- karma-browserstack-launcher
- karma-closure
- karma-ng-scenario
- karma-googmodule-preprocessor
- karma-commonjs
- karma-dojo
- karma-firefox-launcher
- karma-sauce-launcher
- karma-jasmine
- karma-webdriver-launcher
- karma-ie-launcher
- karma-safari-launcher
- karma-growl-reporter
- karma-ember-preprocessor
- karma-cli
- karma-intellij
- maven-karma-plugin
- karma-traceur-preprocessor
- karma-nodeunit
- karma-tyrtle

Karma is an awesome project, but to get it to the next level I will need your help to achieve it.

Contributor guide

Open the contributing guide

Research direction

This is a broad contributor call rather than a bounded task; the named documentation site is karma-runner/karma-runner.github.com, and issue #2200 contains front-page ideas. Start by reviewing those materials and the needs: investigation issue label, then choose one specific maintenance or documentation task whose completion can be demonstrated with an updated page, resolved issue, or documented plugin.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
developer-experience, documentation, testing-qa
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.