chore(release): release version 0.7.1

.github/workflows/pr-commitlint.yml

@@ -18,4 +18,7 @@ jobs:
           last_commit=HEAD^2 # don't lint the merge commit
           npx commitlint --from $first_commit~1 --to $last_commit -V
       - name: Lint Pull Request
-        run: echo "${{ github.event.pull_request.title }}"$'\n\n'"${{ github.event.pull_request.body }}" | npx commitlint -V
+        env:
+          TITLE: ${{ github.event.pull_request.title }}
+          BODY: ${{ github.event.pull_request.body }}
+        run: export NL=; printenv TITLE NL BODY | npx commitlint -V

.gitignore

@@ -12,3 +12,4 @@ mayastor/local-write_verify-0-verify.state
 test-yamls/*
 /package-lock.json
 /node_modules
+artifacts/

CODE_OF_CONDUCT.md

@@ -0,0 +1,59 @@
+## CNCF Community Code of Conduct v1.0
+
+Other languages available:
+- [Chinese/中文](https://raw.githubusercontent.com/cncf/foundation/master/code-of-conduct-languages/zh.md)
+- [Czech/Česky](https://raw.githubusercontent.com/cncf/foundation/master/code-of-conduct-languages/cs.md)
+- [German/Deutsch](https://raw.githubusercontent.com/cncf/foundation/master/code-of-conduct-languages/de.md)
+- [Spanish/Español](https://raw.githubusercontent.com/cncf/foundation/master/code-of-conduct-languages/es.md)
+- [French/Français](https://raw.githubusercontent.com/cncf/foundation/master/code-of-conduct-languages/fr.md)
+- [Italian/Italiano](https://raw.githubusercontent.com/cncf/foundation/master/code-of-conduct-languages/it.md)
+- [Japanese/日本語](https://raw.githubusercontent.com/cncf/foundation/master/code-of-conduct-languages/jp.md)
+- [Korean/한국어](https://raw.githubusercontent.com/cncf/foundation/master/code-of-conduct-languages/ko.md)
+- [Ukrainian/Українська](https://raw.githubusercontent.com/cncf/foundation/master/code-of-conduct-languages/uk.md)
+- [Russian/Русский](https://raw.githubusercontent.com/cncf/foundation/master/code-of-conduct-languages/ru.md)
+- [Portuguese/Português](https://raw.githubusercontent.com/cncf/foundation/master/code-of-conduct-languages/pt.md)
+- [Arabic/العربية](https://raw.githubusercontent.com/cncf/foundation/master/code-of-conduct-languages/ar.md)
+- [Polish/Polski](https://raw.githubusercontent.com/cncf/foundation/master/code-of-conduct-languages/pl.md)
+- [Indonesian/Bahasa Indonesia](https://raw.githubusercontent.com/cncf/foundation/master/code-of-conduct-languages/id.md)
+
+### Contributor Code of Conduct
+
+As contributors and maintainers of this project, and in the interest of fostering
+an open and welcoming community, we pledge to respect all people who contribute
+through reporting issues, posting feature requests, updating documentation,
+submitting pull requests or patches, and other activities.
+
+We are committed to making participation in this project a harassment-free experience for
+everyone, regardless of level of experience, gender, gender identity and expression,
+sexual orientation, disability, personal appearance, body size, race, ethnicity, age,
+religion, or nationality.
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery
+* Personal attacks
+* Trolling or insulting/derogatory comments
+* Public or private harassment
+* Publishing others' private information, such as physical or electronic addresses,
+ without explicit permission
+* Other unethical or unprofessional conduct.
+
+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. By adopting this Code of Conduct, project maintainers
+commit themselves to fairly and consistently applying these principles to every aspect
+of managing this project. Project maintainers who do not follow or enforce the Code of
+Conduct may be permanently removed from the project team.
+
+This code of conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior in Kubernetes may be reported by contacting the [Kubernetes Code of Conduct Committee](https://git.k8s.io/community/committee-code-of-conduct) via <[email protected]>. For other projects, please contact a CNCF project maintainer or our mediator, Mishi Choudhary <[email protected]>.
+
+This Code of Conduct is adapted from the Contributor Covenant
+(http://contributor-covenant.org), version 1.2.0, available at
+http://contributor-covenant.org/version/1/2/0/
+
+### CNCF Events Code of Conduct
+
+CNCF events are governed by the Linux Foundation [Code of Conduct](https://events.linuxfoundation.org/code-of-conduct/) available on the event page. This is designed to be compatible with the above policy and also includes more details on responding to incidents.

CONTRIBUTING.md

@@ -0,0 +1,140 @@
+# Contributing to MayaStor
+
+We're excited to have you interested in contributing to MayaStor!
+
+> *Disclaimer:* MayaStor is a **beta** project, and contributors at this stage of the project
+> lifecycle may experience minor hurdles to contribution.
+>
+> **We want to overcome these. Please report them.**
+
+If you have any questions, our ecosystem can be connected with over [Discord][mayastor-discord]
+(for development) and [Slack][mayastor-slack] ([invite][mayastor-slack-inviter], for support).
+
+Our interactions here are governed by the [CNCF Code of Conduct](CODE-OF_CONDUCT.md).
+
+## Development Environment
+
+Consult the [`doc/build.md`](doc/build.md) for a complete guide to getting started contributing
+to MayaStor.
+
+## Issues & Pull Requests
+
+### Reporting Bugs
+
+You would be **the best** if you reported complete, well described, reproducable bugs to us. If
+you can't, that's ok. Do your best.
+
+Our [Bug Report][issue-bug-report] template includes instructions to get the the information we
+need from you.
+
+### Requesting new features
+
+You are invited to open *complete, well described* issues proposing new features. While MayaStor
+has no formal RFC process at this time, the [Rust RFC template][rust-rfc-template] is an
+excellent place to derive your issue description from.
+
+**You should indicate if you are able to complete and support features you propose.**
+
+### Committing
+
+Start work off the `develop` branch. **Not `master`.**
+
+[bors][bors] will merge your commits. We do not do [*squash merges*][squash-merges].
+
+Each commit message must adhere to [Conventional Commits][conventional-commits]. You can use
+[`convco`][tools-convco] if you would prefer a tool to help.
+
+It is absolutely fine to force push your branch if you need. Feel free to rewrite commit history
+of your pull requests.
+
+### Reviews
+
+The review process is governed by [bors][bors].
+
+Pull requests require at least 1 approval from maintainer or SIG member.
+
+Once review is given, Maintainers and SIG members may indicate merge readiness with the comment
+`bors merge`.
+
+**Please do not hit the 'Update Branch' button.** The commit message is not conventional,
+[bors][bors] will yell at you. Let [bors][bors] handle it, or rebase it yourself.
+
+## Organization
+
+Our maintainers are:
+
+* [@gila][members-gila] - [@mayadata-io][maya-data]
+* [@jkryl][members-jkryl] - [@mayadata-io][maya-data]
+* [@GlennBullingham][members-GlennBullingham] - [@mayadata-io][maya-data]
+
+Our Special Interest Groups (SIGs) are:
+
+* Dataplane
+  + [@hoverbear][members-hoverbear] - [@mayadata-io][maya-data] &
+    [@Hoverbear-Consulting](https://github.com/Hoverbear-Consulting)
+  + [@mtzaurus][members-mtzaurus] - [@mayadata-io][maya-data]
+  + [@jonathan-teh][members-jonathan-teh] - [@mayadata-io][maya-data]
+* e2e-testing
+  + [@chriswldenyer][members-chriswldenyer] - [@mayadata-io][maya-data]
+  + [@blaisedias][members-blaisedias] - [@mayadata-io][maya-data]
+* Control Plane
+  + [@tiagolobocastro][members-tiagolobocastro] - [@mayadata-io][maya-data]
+  + [@paulyoong][members-paulyoong] - [@mayadata-io][maya-data]
+
+Former SIGs (and their members) are:
+
+* None, yet!
+
+### Organization FAQs
+
+* **What is a *Maintainer*?**
+
+  Maintainers are the project architects. They have the final say on what features get accepted,
+  what code gets merged, when releases are cut, and how the project evolves.
+
+  Maintainers **must** make decisions unanimously, no majorities, no votes.
+
+* **What is a *Special Interest Group (SIG)*?**
+
+  SIGs are small ephemeral teams (max 7) working on a general topic.
+
+  They may change at any time, and have no strict definition.
+
+  SIGs may be created, empowered, and destroyed by the maintainers at any time.
+
+* **Are there other levels/roles/organization structure?**
+
+  No. We want to focus on building MayaStor.
+
+  It's preferable that we flow like water as opposed to become a rue goldberg machine of rules.
+
+* **May I join a SIG? Become a maintainer?**
+
+  Of course, we'd love that!
+
+  Once you have a bit of contribution history with the project you will probably already find
+  yourself working with a SIG, so ask, and they'll include you.
+
+  Once you have acted as part of multiple SIGs, contributed at least one major feature, and
+  resolved multiple bug reports, our maintainers may choose to include you in their midst.
+
+[maya-data]: https://github.com/mayadata-io/
+[mayastor-discord]: https://discord.gg/nhpyMeJCHE
+[mayastor-slack]: https://kubernetes.slack.com/messages/openebs
+[mayastor-slack-inviter]: https://slack.k8s.io/
+[members-gila]: https://github.com/gila
+[members-jkryl]: https://github.com/jkryl
+[members-GlennBullingham]: https://github.com/GlennBullingham
+[members-hoverbear]: https://github.com/hoverbear
+[members-tiagolobocastro]: https://github.com/tiagolobocastro
+[members-mtzaurus]: https://github.com/mtzaurus
+[members-jonathan-teh]: https://github.com/jonathan-teh
+[members-paulyoong]: https://github.com/paulyoong
+[members-chriswldenyer]: https://github.com/chriswldenyer
+[members-blaisedias]: https://github.com/blaisedias
+[rust-rfc-template]: https://github.com/rust-lang/rfcs/blob/master/0000-template.md
+[issue-bug-report]: https://github.com/openebs/Mayastor/issues/new?labels=new&template=bug_report.md
+[bors]: https://bors.tech/
+[squash-merges]: https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges#squash-and-merge-your-pull-request-commits
+[conventional-commits]: https://www.conventionalcommits.org/en/v1.0.0/
+[tools-convco]: https://convco.github.io/