JS Community

Why?

1. Kill the waste of effort caused by maintaining lots of duplicates libraries
2. Ensure no libraries become unmaintained and its users orphaned

How?

• Working together
• Stop Not invented here syndrom

Requirements

Structural

1. At least one maintainer (preferably a few)
2. More than one npm owner (reduce the bus factor)!
3. Community oriented (see the code of conduct)
4. Issues and pull requests should be handled (answered, merged, closed) quickly

Technical

1. Do one thing and do it well
2. Tend toward being fully tested
   • continuous integration (Node and/or browsers) (Travis CI, CircleCI, SauceLabs may help)
   • code coverage
3. The least and lightest dependencies possible
4. Keep dependencies up-to-date (Greenkeeper may help)

Code of conduct

TODO: replace by a more complete one such as this one.

Guidelines

• Be friendly and patient
• Be welcoming
• Be considerate
• Be careful in the words that we choose
• Try to understand why we disagree

Reporting issues

If you experience or witness unacceptable behavior —or have any other concerns—please report it by contacting us via julien.fontanet@isonoe.net. All reports will be handled with discretion. In your report please include:

• Your contact information.
• Names (real, nicknames, or pseudonyms) of any individuals involved. If there are additional witnesses, please include them as well. Your account of what occurred, and if you believe the incident is ongoing. If there is a publicly available record (e.g. a mailing list archive or a public IRC logger), please include a link.
• Any additional information that may be helpful.