couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robertkowal...@apache.org
Subject [06/50] couchdb commit: updated refs/heads/asf-site to d3e3eb8
Date Mon, 11 May 2015 19:06:18 GMT
Add id attributes to headings

git-svn-id: https://svn.apache.org/repos/asf/couchdb/site@1618506 13f79535-47bb-0310-9956-ffa450edef68


Project: http://git-wip-us.apache.org/repos/asf/couchdb/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb/commit/acbe2f02
Tree: http://git-wip-us.apache.org/repos/asf/couchdb/tree/acbe2f02
Diff: http://git-wip-us.apache.org/repos/asf/couchdb/diff/acbe2f02

Branch: refs/heads/asf-site
Commit: acbe2f02a708499f7484c9f086ac7c1855e5e13b
Parents: c945ed3
Author: Noah Slater <nslater@apache.org>
Authored: Sun Aug 17 19:05:30 2014 +0000
Committer: Noah Slater <nslater@apache.org>
Committed: Sun Aug 17 19:05:30 2014 +0000

----------------------------------------------------------------------
 conduct.html | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/couchdb/blob/acbe2f02/conduct.html
----------------------------------------------------------------------
diff --git a/conduct.html b/conduct.html
index 7785ad5..6cdbb04 100644
--- a/conduct.html
+++ b/conduct.html
@@ -2,11 +2,11 @@
 
 <body>
 <p><em>This Code of Conduct and Diversity Statement has not yet been made official
by the community. This is a work in progress.</em>
-<h1>Introduction</h1>
+<h1 id="intro">Introduction</h1>
 <p>This code of conduct <u>governs how we behave</u> in any forum and whenever
we will be judged by our actions. We expect it to be honoured by everyone who participates
in the Apache CouchDB community <a href="http://formally%20recognized%20roles%20and%20responsibilities">formally</a>
or informally, or claims any affiliation with the project.
 <p>This code of conduct also <u>applies to all spaces</u> managed by the
Apache CouchDB 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.
<em><span style="color: rgb(255,0,0);">TODO: An expanded code of conduct is being
drafted for events that involve physical interaction (conferences), based on the</span>
<a href="https://www.apache.org/foundation/policies/anti-harassment.html">published
ASF anti-harassment policy</a>.</em>
 <p>This code <u>is not exhaustive or complete</u>. 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.
-<h1>Specific Guidelines</h1>
+<h1 id="guidelines">Specific Guidelines</h1>
 <p>We strive to:
 <ol>
 <li><p><strong>Be open</strong>. We invite anyone to participate
in our community. As per <a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=40511017#ProjectBylaws%28WIP%29-3.DecisionMaking">Section
3 of our Project Bylaws</a>, we preferably use public methods of communication for project-related
messages, unless discussing something sensitive. This applies to messages for help or CouchDB-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.
@@ -30,17 +30,17 @@
 <p>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.
 <p>Try to stay on topic, especially in discussions that are already fairly large.
 <li><p><strong>Step down considerately</strong>: 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.</ol>
-<h1>Diversity Statement</h1>
+<h1 id="diversity">Diversity Statement</h1>
 <p>Apache CouchDB 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.
 <p>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.
 <p>Though we welcome people fluent in all languages, Apache CouchDB development is
conducted in English.
 <p>Standards for behaviour in the Apache CouchDB 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.
 <p>If you want to help encourage a more diverse community, we encourage you to <em><span
style="color: rgb(255,0,0);">TODO: join the diversity mailing list at &lt;TBD&gt;</span></em>
-<h1>Reporting Guidelines</h1>
+<h1 id="reporting">Reporting Guidelines</h1>
 <p>While this code of conduct should be adhered to by participants, we recognize that
sometimes people may have a bad day, or be unaware of some of the guidelines in this code
of conduct. When that happens, 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 of this
code of conduct; in particular, it should not be abusive or disrespectful.
 <p>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. Assume good faith; it is more likely that participants are unaware of
their bad behaviour than that they intentionally try to degrade the quality of the discussion.
Should there be difficulties in dealing with the situation, you may report your compliance
issues in confidence to <a href="mailto:private@couchdb.apache.org">private@couchdb.apache.org</a>.
 <p>If the violation is in documentation or code, for example inappropriate pronoun
usage or word choice within official documentation, we ask that people report these privately
to the project at <a href="mailto:private@couchdb.apache.org">private@couchdb.apache.org</a>,
and, if they have sufficient ability within the project, to resolve or remove the concerning
material, being mindful of the perspective of the person originally reporting the issue.
-<h1>Endnotes</h1>
+<h1 id="endnotes">Endnotes</h1>
 <p>This Code defines <strong>empathy</strong> as "a vicarious participation
in the emotions, ideas, or opinions of others; the ability to imagine oneself in the condition
or predicament of another." <strong>Empathetic</strong> is the adjectival form
of empathy.
 <p>This statement thanks the following, on which it draws for content and inspiration:
 <ul>


Mime
View raw message