Call for Contributors

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

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.

@dignifiedquire I am very much willing to contribute!

Tell me how I can help :)

I am very much willing to contribute!

Awesome, from the areas listed above, are there specific things you would like to work on?

I would like to help ... preferably I would like to fix bugs if you could point me in a direction

I would like to help ... preferably I would like to fix bugs if you could point me in a direction

Great, you can start by looking at this list:

• main repo: https://github.com/karma-runner/karma/issues?q=is%3Aopen+is%3Aissue+label%3A%22type%3A+bug%22
• all repos: https://github.com/search?utf8=%E2%9C%93&q=org%3Akarma-runner+is%3Aissue++state%3Aopen+label%3A%22type%3A+bug%22&type=Issues&ref=searchresults If you find something that you work on, leave a comment. If it's not clear how to fix or you need some guidance just let me know just write on the issue and I'll try to help as I can

@dignifiedquire I would like to contribute as well

@dignifiedquire I would like to contribute, but at a glance it seems overwhelming for me... I have professional experience with AngularJS and exploring E2E testing with Protractor (and some shallow exploration of webdriver), I hope this info is good enough to provide some guidance..

As much as I'd love to offer to take over maintenance of karma-mocha, we barely have enough resources to manage our own code.

At the risk of broaching a sensitive subject...

All these projects are copyright Google? Users must sign a CLA to contribute. Google's CLA is not particularly friendly to contributions by 3rd-party employees (or anyone except Google, really). This means fewer contributions, of course. Node.js dropped its CLA for similar reasons.

Does Google still "own" this project? Isn't it used by the Angular team? Where are the internal resources?

@dignifiedquire Are you a Google employee? Perhaps you can provide some insight?

@dignifiedquire I would love to take up improvements in the following areas:

• Documentation and Website
• karma-intellij

I will also help in triaging issues.

Awesome, from the areas listed above, are there specific things you would like to work on?

@dignifiedquire if help is still required, then count me in!

I'm using Karma on a daily basis, so I'm very interested in projects well-being.

I would like to contribute, but at a glance it seems overwhelming for me

@tiagomsmagalhaes I will try to start labeling issues with difficulty to help with that. In the meantime things like going through the documentation and making sure things are up to date should give you a good way to learn your way around.

@vivganes added you to the main repo and karma-intellij

if help is still required, then count me in!

@jeserkin we have enough work for everyone :)

Anything in particular you would like to start working on?

@boneskull I am not a Google employee, but @vojtajina the original author of karma was when he wrote the project which is the reason it is still under the Google umbrella right now. I'm talking to them about changing this, but I don't know if and how fast things in this area will change.

I would like to contribute as well

@kostkobv great, anything in particular you would like to start working on?

@dignifiedquire I think closest topics to me are:

• karma-phantomjs-launcher
• karma-mocha
• karma-jasmine

Plus labeling issues or requesting more information.

@dignifiedquire I would like to work with karma-mocha, karma-jasmine and karma-phantomjs-launcher for the same reason as @dignifiedquire.

Still I'm open to assist with any kind of issues on any plugin

@jeserkin @kostkobv added you to those three repos.

For everyone I have given write access: Please no merges without review of at least one other contributor, and on karma itself no merges without my approval. Also no pushes to master please. Also please keep your work to personal forks rather for now. Thank you 🎉

@dignifiedquire Hmm. Are they just no longer interested in Karma?

I would like to assist as well - in particular, I would like to assist with the core, and maybe other plugins. In particular, I (selfishly) would like to work on whatever is necessary to implement support for headless Chrome, as I've been bitten more than once by PhantomJS (including today) :) , but I also am willing to work on any other task needed too.

Is there a gathering point for people to discuss strategy, i.e. what issues to address first, things that should be changed when, etc.? Such a chatroom would also be useful for being relayed information quicker. I investigated some of the issues earlier this year, some of them eluded me when I was trying to work on them individually, and I ended up running out of time due to traveling a lot & being promoted to a tech lead/engineering manager. My time is starting to free up a little more though, so I am looking to get involved with open source more again.

Regarding @wesleycho second paragraph. I've also thought about a way to discuss quickly some questions. There are different ways for it. Gitter, Slack, Skype, SO Private chat room. Those who take part in managing karma-runner repos should probably vote and decide. What do you think guys?

@dignifiedquire I would be willing to help with contributing karma-cli:)

@wesleycho added you to the main repo, so you can add labels.

@everyone I appreciate all the feedback and work already being done. Thank you!

• Discussion about chat/forum: #2485
• Issue about headless chrome: #2489

@abouthiroppy great, it really needs some love =)

Hrm- I wouldn't mind helping with karma-browserstack-launcher. It's not a huge codebase to maintain, and we use it at work.

@krotscheck great to hear :)

I would like to contribute to the website. Here is my first pull request https://github.com/karma-runner/karma-runner.github.com/pull/40

@dignifiedquire I would like to help but first i have to make work karma in my project.

Basically a Node api, with webpack, typescript, karma, jasmine, and trying to integrate karma-coverage, until that happens i'll be of no use.

@dignifiedquire I want to help. Code, documentation, project management, issues & bugs, etc.

Hey @dignifiedquire i actually managed to get through it, i have a current Node.js app running on karma, jasmine and typescript with karma coverage on, wanna take a look?

Although i need to updated since the real project in which i have it working is in Bitbucket in a privated repo: Luchillo/Node-typescript-karma-base