This repository has been archived by the owner on May 30, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Increasing maintenance capacity #14548
Labels
Projects
Comments
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. |
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
The text was updated successfully, but these errors were encountered: