+
+### Development
+
+* Master is the latest working version.
+* New features and bug fixes should be developed on branches (or forks), and merged into master.
+
+### Releases
+
+* Once we've merged a few things in and want to make a release, we tag it on master.
+* Not every commit on master will get a tag, we'll accumulate a few changes before making a release, unless there's a reason to release straight away.
+* Once we're confident that the tagged release is building and stable, we merge it into the stable branch.
+
+## Code of Conduct
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+### Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+### Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+### Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/
diff --git a/openflexure_microscope/api/static/LICENSE b/openflexure_microscope/api/static/LICENSE
new file mode 100644
index 00000000..10537ed5
--- /dev/null
+++ b/openflexure_microscope/api/static/LICENSE
@@ -0,0 +1,674 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. + +
+ ++ +
++ +
++ +
+ ++ Some important microscope calibration data is currently missing. +
++ Your microscope will still function, however some functionality will + be limited, and image quality will likely suffer. +
++ Click Next to begin microscope calibration. +
++ Your lens-shading table has already been calibrated. Click Next + to move on. +
++ Follow the important steps below before starting lens-shading + calibration! +
+Once you're ready, click auto-calibrate.
+ ++ Your camera-stage mapping has already been calibrated. Click Next + to move on. +
++ No stage connected. Please skip this step, or connect a valid + stage, then reboot your microscope. +
++ Follow the important steps below before starting camera-stage + mapping calibration! +
+Once you're ready, click auto-calibrate.
+ ++ Calibration complete +
++ Click Finish to return to your microscope, or Restart to re-run the + calibration routine +
++ + + + +
+Path: {{ captureState.path }}
+Time: {{ captureState.metadata.image.acquisitionDate }}
+ID: {{ captureState.metadata.image.id }}
+Format: {{ captureState.metadata.image.format }}
+ ++ {{ key }}: {{ value }} +
+Time: {{ metadata.image.acquisitionDate }}
+ID: {{ metadata.image.id }}
+ ++ {{ key }}: {{ value }} +
++ +
+${message}
+