CreateJS Consortium

The GSkinner team is encouraging the community to get involved in in the maintenance and direction of CreateJS.

A plan needs to be made clear to give confidence that this is a wise decision.

This document describes actions that need to be taken in order for confidence to be had in the community-driven effort.

Vision

What is is this project's vision?

Let humans and machines each do what they are good at. For example, humans can make high level design decisions, and machines can build and release a version of the project.
Protect stability, performance

Anyone can submit a pull request for a change. PRs are automatically checked via automated build, and bots.

The core team are trusted to represent the interests of the whole.

Only they can merge PRs, and approve high-level decisions.

Responsible community members will agree to uphold the chosen standards of the project.

They will be responsible for reviewing and approving code changes, ensuring they take adequate time to understand the change.

They uphold the project code of conduct.

Test coverage can only ever increase.
Peer review of code - approved by 2 or more core developers, other than the submitter.
Follow semantic versioning.
Provide backwards compatibility for as long as possible. Deprecate code, and pull it out only when major version change (such as 2.x.x -> 3.0.0)
Stale bot to close issues if contributor is being waited on

Answer these questions, as checklist items above.