Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
purescript-gargantext
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Grégoire Locqueville
purescript-gargantext
Commits
32f6d3fd
Commit
32f6d3fd
authored
May 31, 2022
by
Alexandre Delanoë
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[UPDATE] Code Of Conduct simpler and accepted by CNRS
parent
c56e557c
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
79 additions
and
74 deletions
+79
-74
CODE_OF_CONDUCT.md
CODE_OF_CONDUCT.md
+79
-74
No files found.
CODE_OF_CONDUCT.md
View file @
32f6d3fd
# Contributor Covenant Code of Conduct
# GarganText "Code of Conduct"
## Our Pledge
The GarganText Project, the contributors of the GarganText eco-system,
have adopted a code of conduct for participants to any modes of
In the interest of fostering an open and welcoming environment, we as
communication within the project.
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
## Be respectful
size, disability, ethnicity, gender identity and expression, level of experience,
nationality, personal appearance, race, religion, or sexual identity and
In a project the size of GarganText, inevitably there will be people
orientation.
with whom you may disagree, or find it difficult to cooperate. Accept
that, but even so, remain respectful. Disagreement is no excuse for poor
## Our Standards
behaviour or personal attacks, and a community in which people feel
threatened is not a healthy community.
Examples of behavior that contributes to creating a positive environment
include:
## Assume good faith
*
Using welcoming and inclusive language
GarganText Contributors have many ways of reaching our common goal of
*
Being respectful of differing viewpoints and experiences
a free digital ecosystem which may differ from your ways. Assume that
*
Gracefully accepting constructive criticism
other people are working towards this goal.
*
Focusing on what is best for the community
*
Showing empathy towards other community members
Note that many of our Contributors are not native English speakers
or may have different cultural backgrounds.
Examples of unacceptable behavior by participants include:
## Be collaborative
*
The use of sexualized language or imagery and unwelcome sexual attention or
advances
GarganText is a large and complex project; there is always more to
*
Trolling, insulting/derogatory comments, and personal or political attacks
learn within GarganText. It's good to ask for help when you need it.
*
Public or private harassment
Similarly, offers for help should be seen in the context of our shared
*
Publishing others' private information, such as a physical or electronic
goal of improving GarganText.
address, without explicit permission
*
Other conduct which could reasonably be considered inappropriate in a
When you make something for the benefit of the project, be willing
professional setting
to explain to others how it works, so that they can build on your work
to make it even better.
## Our Responsibilities
## Try to be concise
Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
Keep in mind that what you write once will be read by many others
response to any instances of unacceptable behavior.
persons. Writing a short email means people can understand the
conversation as efficiently as possible. When a long explanation is
Project maintainers have the right and responsibility to remove, edit, or
necessary, consider adding a summary.
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
Try to bring new arguments to a conversation so that each comment
permanently any contributor for other behaviors that they deem inappropriate,
adds something unique to the thread, keeping in mind that the rest of
threatening, offensive, or harmful.
the thread still contains the other messages with arguments that have
already been made.
## Scope
Try to stay on topic, especially in discussions that are already
This Code of Conduct applies both within project spaces and in public spaces
fairly large.
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
## Be open
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
Most ways of communication used within GarganText allow for public and
further defined and clarified by project maintainers.
private communication. You should preferably use public methods of
communication for GarganText-related messages, unless posting something
## Enforcement
sensitive.
Instances of abusive, harassing, or otherwise unacceptable behavior may be
This applies to messages for help or GarganText-related support,
reported by contacting the project team at
[
sos AT gargantext DOT org
]
. All
too; not only is a public support request much more likely to
complaints will be reviewed and investigated and will result in a response that
result in an answer to your question, it also makes sure that any
is deemed necessary and appropriate to the circumstances. The project team is
inadvertent mistakes made by people answering your question will be
obligated to maintain confidentiality with regard to the reporter of an incident.
more easily detected and corrected.
Further details of specific enforcement policies may be posted separately.
While this code of conduct should be adhered to by participants,
Project maintainers who do not follow or enforce the Code of Conduct in good
we recognize that sometimes people may have a bad day, or be unaware
faith may face temporary or permanent repercussions as determined by other
of some of the guidelines in this code of conduct. When that happens,
members of the project's leadership.
you may reply to them and point out this code of conduct. Such messages
may be in public or in private, whatever is most appropriate. However,
## Attribution
regardless of whether the message is public or not, it should still
adhere to the relevant parts of this code of conduct; in particular, it
This Code of Conduct is adapted from the
[
Contributor Covenant
][
homepage
]
, version 1.4,
should not be abusive or disrespectful. Assume good faith; it is more
available at
[
http://contributor-covenant.org/version/1/4
][
version
]
likely that participants are unaware of their bad behaviour than that
they intentionally try to degrade the quality of the discussion.
[
homepage
]:
http://contributor-covenant.org
[
version
]:
http://contributor-covenant.org/version/1/4/
Serious or persistent offenders will be temporarily or permanently
banned from communicating through GarganText's ecosystem. Complaints
should be made (in private) to the administrators of the GarganText
communication forum in question. To find contact information for these
administrators, please see the page on GarganText's organizational
structure.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment