Merge branch 'master' of https://github.com/mpusz/units

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+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, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, 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 mateusz.pusz@gmail.com. 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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,29 @@
+# Contributing to `mp-units`
+
+👍🎉 First off, thanks for taking the time to contribute! 🎉👍
+
+## Download, Build, Install
+
+Please refer to our official docs for [download, build, and install instructions](https://mpusz.github.io/units/usage.html).
+
+## Where to start?
+
+If you are looking for a good issue to start with, please check the following:
+- [good first issue](https://github.com/mpusz/units/labels/good%20first%20issue) - issues that should be pretty simple to implement.
+- [help wanted](https://github.com/mpusz/units/labels/help%20wanted) - issues that typically are a bit more involved than beginner issues.
+- [high priority](https://github.com/mpusz/units/labels/high%20priority) - things to fix ASAP but often of higher complexity.
+
+## Code Formatting
+
+We intend to use `clang-format` when it finally learns what a C++ concept is :wink:.
+
+Until then, please code alike what is there already:
+- 2 spaces for indentation
+- no indentation for namespaces
+- types, functions, variables naming in a `standard_case`
+- template parameters in a `PascalCase`
+
+## Backward Compatibility
+
+Before submission, please remember to check if the code compiles fine on all the supported compilers (especially gcc-9.3 and MSVC are tricky).
+Unfortunately, we cannot add gcc-9.3 to the CI process as it is [not supported by Conan Docker images](https://github.com/conan-io/conan-docker-tools/issues/200).

conanfile.py

@@ -91,7 +91,7 @@ class UnitsConan(ConanFile):
         if self._run_tests:
             self.build_requires("catch2/2.13.0")
             self.build_requires("doxygen/1.8.18")
-            self.build_requires("linear_algebra/0.7.0@public-conan/testing")
+            self.build_requires("linear_algebra/0.7.0@public-conan/stable")
 
     def build(self):
         cmake = self._configure_cmake()

docs/CHANGELOG.md

@@ -1,7 +1,8 @@
 # Release notes
 
 - **0.6.0 WIP**
-  - linear_algebra updated to 0.7.0/testing
+  - Minimum compiler version supported changed to gcc-9.3
+  - linear_algebra updated to 0.7.0/stable
   - fmt updated to 7.0.3
   - range-v3 updated to 0.11.0
   - catch2 updated to 2.13.0