This is an automated email from the ASF dual-hosted git repository.
jan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pouchdb.git
The following commit(s) were added to refs/heads/master by this push:
new e4ea51c93 Delete CODE_OF_CONDUCT.md
e4ea51c93 is described below
commit e4ea51c937ff1d61f006eb2feb85f422d4c922e9
Author: PJ Fanning <[email protected]>
AuthorDate: Mon Nov 17 18:28:49 2025 +0100
Delete CODE_OF_CONDUCT.md
---
CODE_OF_CONDUCT.md | 79 ------------------------------------------------------
1 file changed, 79 deletions(-)
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
deleted file mode 100644
index 8fe87c5a2..000000000
--- a/CODE_OF_CONDUCT.md
+++ /dev/null
@@ -1,79 +0,0 @@
-Code of Conduct
----------------
-
-Introduction
-------------
-
-This code of conduct *governs how we behave* in any forum and whenever we will
be judged by our actions. We expect it to be honoured by everyone who
participates in the PouchDB community formally or informally, or claims any
affiliation with the project.
-
-This code of conduct also *applies to all spaces* managed by the PouchDB
project, including IRC, all public and private mailing lists, the issue
tracker, the wiki, the blogs, Twitter, and any other forum which the community
uses for communication.
-
-This code is not *exhaustive or complete*. It serves to distill our common
understanding of a collaborative, shared environment and goals. We expect it to
be followed in spirit as much as in the letter, so that it can enrich all of us
and the technical communities in which we participate.
-
-Specific Guidelines
--------------------
-
-We strive to:
-
- 1. **Be open**. We invite anyone to participate in our community, we
preferably use public methods of communication for project-related messages,
unless discussing something sensitive. This applies to messages for help or
PouchDB-related support, too; not only is a public support request much more
likely to result in an answer to a question, it also makes sure that any
inadvertent mistakes made by people answering will be more easily detected and
corrected.
-
- 2. **Be empathetic**, welcoming, friendly, and patient: We work together to
resolve conflict, assume good intentions, and do our best to act in an
empathetic fashion. We may all experience some frustration from time to time,
but we do not allow frustration to turn into a personal attack. A community
where people feel uncomfortable or threatened is not a productive one. We
should be respectful when dealing with other community members as well as with
people outside our community.
-
- 3. **Be collaborative**. Our work will be used by other people, and in turn
we will depend on the work of others. When we make something for the benefit of
the project, we are willing to explain to others how it works, so that they can
build on the work to make it even better. Any decision we make will affect
users and colleagues, and we take those consequences seriously when making
decisions.
-
- 4. **Be inquisitive**. Nobody knows everything! Asking questions early
avoids many problems later, so questions are encouraged, though they may be
directed to the appropriate forum. Those who are asked should be responsive and
helpful, within the context of our shared goal of improving PouchDB.
-
- 5. **Be careful in the words that we choose**. Whether we are participating
as professionals or volunteers, we value professionalism in all interactions,
and take responsibility for our own speech. Be kind to others. Do not insult or
put down other participants. Harassment and other exclusionary behaviour are
not acceptable. This includes, but is not limited to:
- Violent threats or language directed against another person.
- Sexist, racist, or otherwise discriminatory jokes and language.
- Posting sexually explicit or violent material.
- Posting (or threatening to post) other people's personally identifying
information ("doxing").
- Sharing private content, such as emails sent privately or non-publicly, or
unlogged forums such as IRC channel history.
- Personal insults, especially those using racist or sexist terms.
- Unwelcome sexual attention.
- Excessive or unnecessary profanity.
- Repeated harassment of others. In general, if someone asks you to stop,
then stop.
- Advocating for, or encouraging, any of the above behaviour.
-
- 6. **Be concise**. Keep in mind that what you write once will be read by
hundreds of persons. Writing a short email means people can understand the
conversation as efficiently as possible. Short emails should always strive to
be empathetic, welcoming, friendly and patient. When a long explanation is
necessary, consider adding a summary.
-
- Try to bring new ideas to a conversation so that each mail adds something
unique to the thread, keeping in mind that the rest of the thread still
contains the other messages with arguments that have already been made.
-
- Try to stay on topic, especially in discussions that are already fairly
large.
-
- 7. **Step down considerately**: Members of every project come and go. When
somebody leaves or disengages from the project they should tell people they are
leaving and take the proper steps to ensure that others can pick up where they
left off. In doing so, they should remain respectful of those who continue to
participate in the project and should not misrepresent the project's goals or
achievements. Likewise, community members should respect any individual's
choice to leave the project.
-
-Diversity Statement
--------------------
-
-PouchDB welcomes and encourages participation by everyone. We are committed to
being a community that everyone feels good about joining. Although we may not
be able to satisfy everyone, we will always work to treat everyone well.
-
-No matter how you identify yourself or how others perceive you: we welcome
you. Though no list can hope to be comprehensive, we explicitly honour
diversity in: age, culture, ethnicity, genotype, gender identity or expression,
language, national origin, neurotype, phenotype, political beliefs, profession,
race, religion, sexual orientation, socioeconomic status, subculture and
technical ability.
-
-Though we welcome people fluent in all languages, PouchDB development is
conducted in English.
-
-Standards for behaviour in the PouchDB community are detailed in the Code of
Conduct above. We expect participants in our community to meet these standards
in all their interactions and to help others to do so as well.
-
-
-Reporting Guidelines
---------------------
-
-PouchDB maintainers have the primary responsibility to ensure this code of
conduct is adhered to however all in the community are invited to participate
in cultivating a respectful atmosphere. If you believe someone is violating
this code of conduct, 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, regardless of whether the message is public or not, it should still
adhere to the relevant parts o [...]
-
-Anyone violating the code of conduct will be notified and asked to stop, if
anyone repeatedly violates the code of conduct then the actions may include but
not be limited to closing problematic bugs, temporary or permanent exclusion
from GitHub, mailing lists or other PouchDB controlled communities.
-
-Endnotes
---------
-
-This Code defines empathy as "a vicarious participation in the emotions,
ideas, or opinions of others; the ability to imagine oneself in the condition
or predicament of another." Empathetic is the adjectival form of empathy.
-
-This document was derived primarily from the [Apache CouchDB Code of
Conduct](http://couchdb.apache.org/conduct.html) with thanks. The Apache
CouchDB thanks the following documents on which it draws for content and
inspiration:
-
- * [Fedora Project Code of Conduct](http://fedoraproject.org/code-of-conduct)
- * [Speak Up! Code of Conduct](http://speakup.io/coc.html)
- * [Django Code of Conduct](https://www.djangoproject.com/conduct/)
- * [Debian Code of Conduct](http://www.debian.org/vote/2014/vote_002)
- * [Twitter Open Source Code of
Conduct](https://github.com/twitter/code-of-conduct/blob/master/code-of-conduct.md)
- * [Mozilla Code of
Conduct/Draft](https://wiki.mozilla.org/Code_of_Conduct/Draft#Conflicts_of_Interest)
- * [Python Diversity Appendix](https://www.python.org/community/diversity/)
- * [Python Mentors Home Page](http://pythonmentors.com/)
