mirror of
https://github.com/SpartanJ/eepp.git
synced 2026-09-22 13:01:05 +03:00
10a5d7effc
Added Code of Conduct and Contributing documents. Added templates for bug reports and feature requests.
75 lines
3.3 KiB
Markdown
75 lines
3.3 KiB
Markdown
# Code of Conduct
|
|
|
|
## Our expectations
|
|
|
|
Everyone is welcome to participate. We value good-faith questions, reports,
|
|
ideas, and contributions from people of all backgrounds and experience levels.
|
|
|
|
This project is maintained in limited time. Participation must be respectful,
|
|
constructive, and mindful of that time.
|
|
|
|
Acceptable behavior includes communicating respectfully, following the
|
|
repository guidelines, providing requested technical information, making a
|
|
good-faith effort to help investigate reported problems, and respecting
|
|
maintainers' final decisions while remaining free to disagree constructively.
|
|
|
|
Unacceptable behavior includes:
|
|
|
|
* Insults, threats, harassment, discrimination, sexualized attention, or
|
|
personal attacks.
|
|
* Demanding work, repeatedly arguing after a decision has been made, or treating
|
|
maintainers and contributors as a support service.
|
|
* Spam, deliberate disruption, off-topic posts, or opening multiple low-quality
|
|
reports or feature requests in a short period of time.
|
|
* Repeatedly ignoring issue templates, contribution guidelines, moderator
|
|
instructions, or requests for information.
|
|
* Impersonation, coordinated abuse, or using alternate accounts to evade a
|
|
warning, block, interaction limit, or other moderation action.
|
|
* Publishing another person's private information without permission.
|
|
|
|
Criticism of the software and technical decisions is welcome. Hostility toward
|
|
people is not.
|
|
|
|
## Scope
|
|
|
|
This Code of Conduct applies to all project spaces, including Issues, Pull
|
|
Requests, Discussions, and other communication associated with the project. It
|
|
also applies when someone publicly represents the project or its community.
|
|
|
|
Issue-tracker participation must also follow [CONTRIBUTING.md](CONTRIBUTING.md).
|
|
Questions and early-stage ideas belong in GitHub Discussions, not Issues.
|
|
|
|
## Enforcement
|
|
|
|
Maintainers may edit, hide, lock, or remove content; close or limit
|
|
interactions; and temporarily or permanently block participants when behavior
|
|
is inappropriate, disruptive, or contrary to these rules.
|
|
|
|
When practical, maintainers will first explain the problem and give the
|
|
participant an opportunity to correct it. A warning is not guaranteed for
|
|
serious abuse, obvious spam, threats, harassment, impersonation, or moderation
|
|
evasion.
|
|
|
|
Account age and history may be considered as anti-abuse signals when deciding
|
|
whether additional verification or moderation is necessary. Rules are based on
|
|
behavior, not on nationality, ethnicity, age, language, or any other personal
|
|
identity. Creating or rotating accounts to evade controls may result in an
|
|
immediate block of all associated accounts.
|
|
|
|
Possible responses include a correction request, a warning, a temporary
|
|
restriction, or a permanent restriction. Maintainers may choose the response
|
|
appropriate to the behavior and its history; these steps do not have to be
|
|
applied in order.
|
|
|
|
## Reporting conduct problems
|
|
|
|
Report conduct problems privately to the maintainer using the contact details
|
|
on the maintainer's GitHub profile. Include links, screenshots, or other
|
|
relevant context when possible. Reports will be handled as confidentially as
|
|
reasonably possible. Do not open a public Issue to report a Code of Conduct
|
|
violation.
|
|
|
|
Maintainers are responsible for clarifying and enforcing these standards. They
|
|
must apply them in good faith and may recuse themselves when they cannot review
|
|
a matter impartially.
|