ariya
Increasing maintenance capacity
This is a meta-discussion to collect ideas on how to increase the maintenance effort of PhantomJS.
For the background, please read the previous issue #14541 on Communicating maintenance capacity and prioritization.
Other related issues:
- #14543 Lowering the barrier to contribution
- #13861 How I can help PhantomJS development?
When proposing ideas for solving this problem, please keep in mind that it has be realistic and there is a possibility of a follow-up.
Some ideas from #14541, as proposed by (among others) @gsouf @Ivanca @annulen:
- Create a source of funding to pay someone to work on PhantomJS
- Build a business that leverages PhantomJS (and contributes back)
- Look for people who can afford to dedicate their time
Hi folks. We spoke late last year about the possibility of having my firm Changeset Consulting do bug triage, prioritization, release management, and similar work on your behalf, and I'd be interested in submitting a fresh grant to Mozilla (the newer Mission Partners track is more applicable to PhantomJS than the Foundational Technology track was). I'd also be interested in doing the legwork to talk with companies that use PhantomJS, to see whether they'd fund our work to get the next releases out faster. I'll get notifications on this issue in case we want to coordinate that way.
