We need a `contributing.md` doc that shares community conventions. ## Stamp conventions - [ ] Naming stamps: `your-module-name-stamp` - [ ] Keywords for `package.json`: `stamp`, `stampit` ### Automatic code quality conventions :sunglasses: - [ ] Use the [prod-module-boilerplate](https://github.com/ericelliott/prod-module-boilerplate) (soon to be replaced with `npm install -g cloverfield cf-package && cf build package`) - see [Cloverfield](https://github.com/cloverfield-tools/cloverfield) - [ ] Remember to add unit tests [tape](https://github.com/substack/tape) or [blue-tape](https://github.com/spion/blue-tape) preferred. Aim for 100% coverage (see generated `coverage` directory for reports) - [ ] Use CI integration with [CircleCI](https://circleci.com) or [Travis](https://travis-ci.org/) ## Getting your stamp added to stampit-org: - [ ] Create a [new issue with [new stamp]](https://github.com/stampit-org/stampit/issues/new?title=[new%20stamp]) in the title. cc @troutowicz @nkbt @unstoppablecarl
We need a
contributing.mddoc that shares community conventions.Stamp conventions
your-module-name-stamppackage.json:stamp,stampitAutomatic code quality conventions 😎
npm install -g cloverfield cf-package && cf build package) - see Cloverfieldcoveragedirectory for reports)Getting your stamp added to stampit-org:
cc @troutowicz @nkbt @unstoppablecarl