Open dignifiedquire opened 7 years ago
@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:
@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:
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:
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!
@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
I would like contribute, @dignifiedquire. I could help in Issues & Support, and Coding.
@dignifiedquire I can help with karma-chrome-launcher & karma-cli
@gcca @rogeriopvl great to hear :) feel free to start responding to issues and making PRs for fixes :)
@dignifiedquire already did a PR and checked some issues, but it would be easier if you add me to the repo/org so I can starting labelling and cleaning stuff.
Hey @dignifiedquire , I have installed the karma@latest from npm, and it come with version 1.7.3 of socket.io. At work we're having problems to run ours test and probably that update can solve our problem. I've noticed come people with some type of problem with socket.io dep in #2777 #2735, some PRs about it #2744 #2821 and I've reported something like in august at #2798. Can I try to do something for help?
@dignifiedquire I’d like to contribute to issue management, the backlog here is tremendous.
Thanks @EzraBrooks for the help. Getting through this backlog would be great! I just added you as a collaborator to the repo.
I wanna join too
@dignifiedquire I'd like to contribute as well.
@dignifiedquire I can help you on karma-qunit if you want 😉
@dignifiedquire hereby volunteering to help with karma-runner/karma-qunit (on behalf of @qunitjs), and also with karma-runner/grunt-karma (on behalf of Wikimedia).
@Krinkle I added you to these projects. karma-qunit is in pretty good shape if the recent PRs land. grunt-karma could use some love.
@dignifiedquire I have investigated doing development time security fixes as I need to use karma. Also I want to try and get the IE11 karma-ie-launcher fixed, as its failing to run properly.
There are loads of issues with handlebars under istanbul for both karma-typescript and karma-coverage. The issue is istanbul has been frozen and also has many many more development time security issues that this npm audit does not find.
There is a new cli replacement for istanbul called nyc.
I have made a minor pull request to istanbul hoping they will take it.
https://github.com/gotwarlost/istanbul/pull/924
Heres an audit of a test project :-
https://github.com/AaronNGray/karma-typescript-mocha-chai-sinon-es6-modules
C:\Users\aaron\Examples\TypeScript\karma-typescript-mocha-chai-sinon-es6-modules>npm audit
=== npm audit security report ===
Manual Review
Some vulnerabilities require your attention to resolve
Visit https://go.npm.me/audit-guide for additional guidance
Critical Prototype Pollution
Package handlebars
Patched in >=4.0.14 <4.1.0 || >=4.1.2
Dependency of karma-coverage [dev]
Path karma-coverage > istanbul > handlebars
More info https://npmjs.com/advisories/755
Critical Prototype Pollution
Package handlebars
Patched in >=4.0.14 <4.1.0 || >=4.1.2
Dependency of karma-typescript [dev]
Path karma-typescript > karma-coverage > istanbul > handlebars
More info https://npmjs.com/advisories/755
Critical Prototype Pollution
Package handlebars
Patched in >=4.0.14 <4.1.0 || >=4.1.2
Dependency of karma-typescript [dev]
Path karma-typescript > istanbul > handlebars
More info https://npmjs.com/advisories/755
Critical Prototype Pollution
Package handlebars
Patched in >=4.0.14 <4.1.0 || >=4.1.2
Dependency of karma-typescript [dev]
Path karma-typescript > remap-istanbul > istanbul > handlebars
More info https://npmjs.com/advisories/755
High Prototype Pollution
Package handlebars
Patched in >=4.3.0
Dependency of karma-coverage [dev]
Path karma-coverage > istanbul > handlebars
More info https://npmjs.com/advisories/1164
High Prototype Pollution
Package handlebars
Patched in >=4.3.0
Dependency of karma-typescript [dev]
Path karma-typescript > karma-coverage > istanbul > handlebars
More info https://npmjs.com/advisories/1164
High Prototype Pollution
Package handlebars
Patched in >=4.3.0
Dependency of karma-typescript [dev]
Path karma-typescript > istanbul > handlebars
More info https://npmjs.com/advisories/1164
High Prototype Pollution
Package handlebars
Patched in >=4.3.0
Dependency of karma-typescript [dev]
Path karma-typescript > remap-istanbul > istanbul > handlebars
More info https://npmjs.com/advisories/1164
Moderate Denial of Service
Package handlebars
Patched in >=4.4.5
Dependency of karma-coverage [dev]
Path karma-coverage > istanbul > handlebars
More info https://npmjs.com/advisories/1300
Moderate Denial of Service
Package handlebars
Patched in >=4.4.5
Dependency of karma-typescript [dev]
Path karma-typescript > karma-coverage > istanbul > handlebars
More info https://npmjs.com/advisories/1300
Moderate Denial of Service
Package handlebars
Patched in >=4.4.5
Dependency of karma-typescript [dev]
Path karma-typescript > istanbul > handlebars
More info https://npmjs.com/advisories/1300
Moderate Denial of Service
Package handlebars
Patched in >=4.4.5
Dependency of karma-typescript [dev]
Path karma-typescript > remap-istanbul > istanbul > handlebars
More info https://npmjs.com/advisories/1300
High Arbitrary Code Execution
Package handlebars
Patched in >=4.5.2
Dependency of karma-coverage [dev]
Path karma-coverage > istanbul > handlebars
More info https://npmjs.com/advisories/1316
High Arbitrary Code Execution
Package handlebars
Patched in >=4.5.2
Dependency of karma-typescript [dev]
Path karma-typescript > karma-coverage > istanbul > handlebars
More info https://npmjs.com/advisories/1316
High Arbitrary Code Execution
Package handlebars
Patched in >=4.5.2
Dependency of karma-typescript [dev]
Path karma-typescript > istanbul > handlebars
More info https://npmjs.com/advisories/1316
High Arbitrary Code Execution
Package handlebars
Patched in >=4.5.2
Dependency of karma-typescript [dev]
Path karma-typescript > remap-istanbul > istanbul > handlebars
More info https://npmjs.com/advisories/1316
High Arbitrary Code Execution
Package handlebars
Patched in >=4.5.3
Dependency of karma-coverage [dev]
Path karma-coverage > istanbul > handlebars
More info https://npmjs.com/advisories/1324
High Arbitrary Code Execution
Package handlebars
Patched in >=4.5.3
Dependency of karma-typescript [dev]
Path karma-typescript > karma-coverage > istanbul > handlebars
More info https://npmjs.com/advisories/1324
High Arbitrary Code Execution
Package handlebars
Patched in >=4.5.3
Dependency of karma-typescript [dev]
Path karma-typescript > istanbul > handlebars
More info https://npmjs.com/advisories/1324
High Arbitrary Code Execution
Package handlebars
Patched in >=4.5.3
Dependency of karma-typescript [dev]
Path karma-typescript > remap-istanbul > istanbul > handlebars
More info https://npmjs.com/advisories/1324
High Prototype Pollution
Package handlebars
Patched in >=4.5.3
Dependency of karma-coverage [dev]
Path karma-coverage > istanbul > handlebars
More info https://npmjs.com/advisories/1325
High Prototype Pollution
Package handlebars
Patched in >=4.5.3
Dependency of karma-typescript [dev]
Path karma-typescript > karma-coverage > istanbul > handlebars
More info https://npmjs.com/advisories/1325
High Prototype Pollution
Package handlebars
Patched in >=4.5.3
Dependency of karma-typescript [dev]
Path karma-typescript > istanbul > handlebars
More info https://npmjs.com/advisories/1325
High Prototype Pollution
Package handlebars
Patched in >=4.5.3
Dependency of karma-typescript [dev]
Path karma-typescript > remap-istanbul > istanbul > handlebars
More info https://npmjs.com/advisories/1325
found 24 vulnerabilities (4 moderate, 16 high, 4 critical) in 4296 scanned packages
24 vulnerabilities require manual review. See the full report for details.
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
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
plus
docs need updating and we don't have them for many pluginsCode
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 is an awesome project, but to get it to the next level I will need your help to achieve it.