From e1a5f9f7b4eb8609f219e6ff22761d7e150f3ed3 Mon Sep 17 00:00:00 2001 From: Daniel Selvan D Date: Sat, 19 Oct 2019 14:23:05 +0530 Subject: [PATCH 1/4] Created CONTRIBUTING.md --- CONTRIBUTING.md | 80 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..adf5039 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,80 @@ +# Contributing + +When contributing to this repository, it is advised to discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change. + +Please note we have a **code of conduct**, please follow it in all your interactions with the project. + +## Pull Request Process + +1. Ensure any install or build dependencies are removed before the end of the layer when doing a + build. +2. Update the README.md with details of changes to the interface, this includes new variables, exposed ports, useful file locations. +3. Increase the version numbers in any examples files and the README.md to the new version that this *Pull Request* would represent. +4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you. + +## 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, 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. From 7ddb1ca3fac292c5684af78d5b035d312a386ad6 Mon Sep 17 00:00:00 2001 From: Daniel Selvan D Date: Sat, 19 Oct 2019 14:49:37 +0530 Subject: [PATCH 2/4] Updated README --- README | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/README b/README index 1e4a1cc..3a8bc59 100644 --- a/README +++ b/README @@ -1,5 +1,10 @@ +STM32 Based Random projects +=== -Projects provided "as-is" with no warranty. -I release my work under CC-BY-SA 3.0 licence. -http://creativecommons.org/licenses/by-sa/3.0/ + +## LICENSE: + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + +I release my work under [CC-BY-SA 3.0 licence](http://creativecommons.org/licenses/by-sa/3.0/). From 0aac884288a844a4b8592667a48de4da7e9d0d44 Mon Sep 17 00:00:00 2001 From: Daniel Selvan D Date: Sat, 19 Oct 2019 14:54:40 +0530 Subject: [PATCH 3/4] README update Added link for Cortex-M3 for further reference --- README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README b/README index 3a8bc59..dac8c07 100644 --- a/README +++ b/README @@ -1,7 +1,7 @@ STM32 Based Random projects === - +Various [Cortex-M3](https://developer.arm.com/ip-products/processors/cortex-m/cortex-m3) projects ## LICENSE: From c0cbd594db3ba1782ae0decc44a866dcb98d473c Mon Sep 17 00:00:00 2001 From: Daniel Selvan D Date: Sat, 19 Oct 2019 14:56:01 +0530 Subject: [PATCH 4/4] Rename README to README.md Added github flavored markdown support --- README => README.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename README => README.md (100%) diff --git a/README b/README.md similarity index 100% rename from README rename to README.md