mirror of
https://github.com/superseriousbusiness/gotosocial.git
synced 2024-07-03 20:35:47 +00:00
fc3741365c
* Add Swagger spec test script * Fix Swagger spec errors not related to statuses with polls * Add API tests that post a status with a poll * Fix creating a status with a poll from form params * Fix Swagger spec errors related to statuses with polls (this is the last error) * Fix Swagger spec warnings not related to unused definitions * Suppress a duplicate list update params definition that was somehow causing wrong param names * Add Swagger test to CI - updates Drone config - vendorizes go-swagger - fixes a file extension issue that caused the test script to generate JSON instead of YAML with the vendorized version * Put `Sample: ` on its own line everywhere * Remove unused id param from emojiCategoriesGet * Add 5 more pairs of profile fields to account update API Swagger * Remove Swagger prefix from dummy fields It makes the generated code look weird * Manually annotate params for statusCreate operation * Fix all remaining Swagger spec warnings - Change some models into operation parameters - Ignore models that already correspond to manually documented operation parameters but can't be trivially changed (those with file fields) * Documented that creating a status with scheduled_at isn't implemented yet * sign drone.yml * Fix filter API Swagger errors * fixup! Fix filter API Swagger errors --------- Co-authored-by: tobi <tobi.smethurst@protonmail.com>
75 lines
3.2 KiB
Markdown
75 lines
3.2 KiB
Markdown
# 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, 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 ivan+abuse@flanders.co.nz. 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 [http://contributor-covenant.org/version/1/4][version]
|
|
|
|
[homepage]: http://contributor-covenant.org
|
|
[version]: http://contributor-covenant.org/version/1/4/
|