From e22f9b989bb11e8dd45bd48fcd78e4b6be301e22 Mon Sep 17 00:00:00 2001 From: Mateusz Pusz Date: Sat, 5 Sep 2020 11:54:09 +0200 Subject: [PATCH 1/5] Common cmake tools fixed --- cmake/common | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cmake/common b/cmake/common index ba5b1163..eb5fbd40 160000 --- a/cmake/common +++ b/cmake/common @@ -1 +1 @@ -Subproject commit ba5b1163c1d364c4498219a16da0ccf1557e421d +Subproject commit eb5fbd40d1cb765c5a8bf50866db86082c72ef73 From 7ed09c1bb9653cd36e47c8415562474245519b37 Mon Sep 17 00:00:00 2001 From: Mateusz Pusz Date: Sat, 5 Sep 2020 13:06:09 +0200 Subject: [PATCH 2/5] Create CODE_OF_CONDUCT.md --- CODE_OF_CONDUCT.md | 76 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 76 insertions(+) create mode 100644 CODE_OF_CONDUCT.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 00000000..27fdf7a3 --- /dev/null +++ b/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 From 17d2fb7815d6d11cbd0cd509f69dcedf8a68698e Mon Sep 17 00:00:00 2001 From: Mateusz Pusz Date: Sat, 5 Sep 2020 13:36:16 +0200 Subject: [PATCH 3/5] Create CONTRIBUTING.md --- CONTRIBUTING.md | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 00000000..23a24713 --- /dev/null +++ b/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). From 81361afeb3ee28f380ee9b21c6b76fce3649fa22 Mon Sep 17 00:00:00 2001 From: Antony Peacock Date: Sat, 5 Sep 2020 12:17:36 +0100 Subject: [PATCH 4/5] Move to stable Linear Algebra Conan package --- conanfile.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conanfile.py b/conanfile.py index 40d7bbe5..21241a87 100644 --- a/conanfile.py +++ b/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() From 3c5f5f30a424c29b5fe732266c3b40a1c7ff8979 Mon Sep 17 00:00:00 2001 From: Mateusz Pusz Date: Sat, 5 Sep 2020 19:18:43 +0200 Subject: [PATCH 5/5] CHANGELOG updated --- docs/CHANGELOG.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md index 9596886f..da7b9dce 100644 --- a/docs/CHANGELOG.md +++ b/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 @@ -13,7 +14,6 @@ - FPS system added (thanks [@mikeford3](https://github.com/mikeford3)) - `quantity_point` support added (thanks [@johelegp](https://github.com/johelegp)) - `ratio` changed to the NTTP kind - - Minimum compiler version supported changed to gcc-9.3 - **0.5.0 May 17, 2020** - Major refactoring and rewrite of the library