roman/gyroflow
1
0
Fork 0
mirror of https://github.com/gyroflow/gyroflow.git synced 2026-07-04 15:06:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add contributing and code of conduct guides

Browse Source
This commit is contained in:
AdrianEddy
2023-02-24 17:58:14 +01:00
parent b58ade8799
commit 876f942d71
3 changed files with 200 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CODE_OF_CONDUCT.md
+70
View File
@@ -0,0 +1,70 @@
# Code of Conduct - Gyroflow
## Our Pledge
In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to make 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 a positive environment for our
community include:
* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience
* Focusing on what is best not just for us as individuals, but for the
overall community
Examples of unacceptable behavior include:
* The use of sexualized language or imagery, and sexual attention or
advances
* Trolling, insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email
address, without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting
## Our Responsibilities
Project maintainers are responsible for clarifying and enforcing our standards of
acceptable behavior and will 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 within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official e-mail address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.
## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at <devteam@gyroflow.xyz>.
All complaints will be reviewed and investigated promptly and fairly.
All community leaders are obligated to respect the privacy and security of the
reporter of any incident.
## Attribution
This Code of Conduct is adapted from the [Contributor Covenant](https://contributor-covenant.org/), version
[1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct/code_of_conduct.md) and
[2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct/code_of_conduct.md),
and was generated by [contributing-gen](https://github.com/bttger/contributing-gen).
CONTRIBUTING.md
+120
View File
@@ -0,0 +1,120 @@
<!-- omit in toc -->
# Contributing to Gyroflow
First off, thanks for taking the time to contribute! ❤️
All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
> And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
> - Star the project
> - Tweet about it
> - Refer this project in your project's readme
> - Mention the project at local meetups and tell your friends/colleagues
<!-- omit in toc -->
## Table of Contents
- [Code of Conduct](#code-of-conduct)
- [I Have a Question](#i-have-a-question)
- [I Want To Contribute](#i-want-to-contribute)
- [Reporting Bugs](#reporting-bugs)
- [Suggesting Enhancements](#suggesting-enhancements)
- [Your First Code Contribution](#your-first-code-contribution)
- [Improving The Documentation](#improving-the-documentation)
## Code of Conduct
This project and everyone participating in it is governed by the
[Gyroflow Code of Conduct](https://github.com/gyroflow/gyroflow/blob/master/CODE_OF_CONDUCT.md).
By participating, you are expected to uphold this code.
## I Have a Question
> If you want to ask a question, we assume that you have read the available [Documentation](https://docs.gyroflow.xyz).
Before you ask a question, it is best to search for existing [Issues](https://github.com/gyroflow/gyroflow/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
The best place to ask questions is the [Discord server](https://discord.com/invite/BBJ2UVAr2D).
If you don't want to use Discord, you can also use the issue tracker, however Discord is encouraged.
- Open an [Issue](https://github.com/gyroflow/gyroflow/issues/new).
- Provide as much context as you can about what you're running into.
- Provide project and platform versions, depending on what seems relevant.
We will then take care of the issue as soon as possible.
## I Want To Contribute
<!-- omit in toc -->
### Legal Notice
When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
### Reporting Bugs
<!-- omit in toc -->
#### Before Submitting a Bug Report
A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
- Make sure that you are using the latest version.
- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://docs.gyroflow.xyz). If you are looking for support, you might want to check [this section](#i-have-a-question)).
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/gyroflow/gyroflowissues?q=label%3Abug).
- Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
- Collect information about the bug:
- Stack trace (Traceback)
- OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
- Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
- Possibly your input and the output
- Can you reliably reproduce the issue? And can you also reproduce it with older versions?
<!-- omit in toc -->
#### How Do I Submit a Good Bug Report?
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
- Open an [Issue](https://github.com/gyroflow/gyroflow/issues/new).
- Explain the behavior you would expect and the actual behavior.
- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own.
- Provide the information you collected in the previous section.
### Suggesting Enhancements
This section guides you through submitting an enhancement suggestion for Gyroflow, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
<!-- omit in toc -->
#### Before Submitting an Enhancement
- Make sure that you are using the [latest dev version](https://gyroflow.xyz/devbuild/?autodownload).
- Read the [documentation](https://docs.gyroflow.xyz) carefully and find out if the functionality is already covered.
- Perform a [search](https://github.com/gyroflow/gyroflow/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
<!-- omit in toc -->
#### How Do I Submit a Good Enhancement Suggestion?
Enhancement suggestions are tracked as [GitHub issues](https://github.com/gyroflow/gyroflow/issues).
- Use a **clear and descriptive title** for the issue to identify the suggestion.
- Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
- **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you.
- You may want to **include screenshots and animated GIFs** which help you demonstrate the steps or point out the part which the suggestion is related to.
- **Explain why this enhancement would be useful** to most Gyroflow users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
### Your First Code Contribution
- First you'll need to build Gyroflow locally, you can follow the steps in README or in the [documentation](https://docs.gyroflow.xyz/app/technical-details/building-from-source).
- You can then proceed to implementing your changes.
- Once you are confident your change is working well and is useful for others, open a [Pull Request](https://github.com/gyroflow/gyroflow/pulls)
- Someone from the team will review your PR and hopefully it will be merged to upstream project.
### Improving The Documentation
The documentation is hosted at https://github.com/gyroflow/docs.gyroflow.xyz. Feel free to submit a PR there in order to improve the documentation.
<!-- omit in toc -->
## Attribution
This guide is based on the **contributing-gen**. [Make your own](https://github.com/bttger/contributing-gen)!
LICENSE
+10 -9
View File
@@ -1,12 +1,3 @@
**Gyroflow Core - Additional Permissions:**
As additional permission under section 7, you are allowed to distribute
[`gyroflow_core`](https://github.com/gyroflow/gyroflow/tree/master/src/core) through an app store, even if that store has restrictive
terms and conditions that are incompatible with the GPL, provided that
the source is also available under the GPL with or without this permission
through a channel without those restrictive terms and conditions.
---
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
@@ -681,3 +672,13 @@ may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License. But first, please read
<https://www.gnu.org/licenses/why-not-lgpl.html>.
---
**Additional terms:**
As an additional permission under section 7, you are allowed to distribute
Gyroflow and [`gyroflow_core`](https://github.com/gyroflow/gyroflow/tree/master/src/core)
through an app store, even if that store has restrictive terms and conditions
that are incompatible with the GPLv3 license, provided that
the source is also available under the GPLv3 with or without this permission
through a channel without those restrictive terms and conditions.