-
Notifications
You must be signed in to change notification settings - Fork 19
Contribution Guide
Stephen Mckellar edited this page Nov 16, 2017
·
13 revisions
This page is meant to function as a set of general principles for the code that is contributed to the Network Canvas suite of apps (Network Canvas, Server, and Architect). These principles are designed to help us meet our overall goals: to have software that is easy to develop, easy to extend, and easy to debug.
Contributions from any team members are welcome, but please discuss your idea on Slack first!
- Code should be self-documenting, and as far as-is possible, self-explanatory.
- Components should gracefully handle invalid/incorrect properties. Incorrect properties should not cause a component (or the app) to fail.
- No speculative implementation. Not ever.
- No committing to master. If you are under pressure, or need to fix something that quickly, something else has gone wrong in our process.
- There are no stupid questions. No one is expected to know everything. Speak up early if there's something you're not sure about, or even if you just want a sound board to help shape a new idea.