Policies

[richburdon]

• Remove copyright headers from files?
• We need access to npm dxos org.
• CI: Add to CircleCI? Use TravisCI?
• LICENSE + COC + CONTRIBUTING (create a github repo for this)
• Standardize linter/code style (standardx, airbnb, prettier+, custom?)
• Changelog (Use @geut/chan + chaas?, other?)
• Enable GreenKeeper to keep dependencies updated. (This can be fairly easy)
• Semver? (Start with v1.0.0 ?)
• Use latest channel (+ beta ?, + canary ?)
• Automate process to publish to nom
• Add badges (npm, tests, coverage?)
• GH Template repo for creating modules.

[richburdon]

I would very much like to have some for of header to anchor the Dx brand, culture and coding style. It doesn't need to have copyright.

I would like to keep our current coding style, although am open to some standard that is close.

Your call on all tools and technical policies -- create a POLICY.md or probably better as a github issue.