The preceding paragraph clarifies that HBR infractions are not “read
into” this Covenant as violations.
However, a tangential problem is addressed herein: this Covenant must
operate independently of HBR, and when in conflict, the Covenant
supersedes.
The HBR is a guideline but not a specific code of conduct or covenant
from contributors. However, we should note this here for avoidance
of any doubt, as many may already see HBR as the CoC of copyleft-next
— even though it was never intended to be.
While `(visual-line-mode 1)` is definitely not my style, the file
came to us with long lines, and maintaining diffs might work better
if we leave it in place by default.
In my experience, there is some confusion in the community about how
CC-By-SA-4.0 works. For example, some consider it plagiarism to
repurpose works as permitted by the license. Since my experiences
with such accusations, I always take great care to carefully list out
the methods by which a modified/adapted CC-BY-SA-4.0 work complies
with §3(a)(A). I do that first and maintain it thereafter.
After all, bare minimum adherence to Free licenses is not what we in
the copyleft-next project seek — we seek exuberant adherence that
goes above and beyond to make adaptation, modification, and
improvement as easy as possible for downstream.
This commit should match the commit
`bc20cd864e3094fff55fd56ec702fe101861c3a3` which was made to the
upstream contributor_covenant repository here:
bc20cd864e
This commit is placed here to give a potentially clean merge base
should the copyleft-next project wish to merge in future changes to
the upstream CoC.
Generally, Git repositories prefer not to to have text files with trailing
whitespace characters in them. As such, this commit is applied, even though
it changes the checksum of the canonical license text as downloaded from:
http://creativecommons.org/licenses/by-sa/4.0/legalcode.txt
However, this appears to be the right thing to do here.
The 'main' branch in this repository keeps the detailed log of any
updates, changes, or other information related to our selection and
development of the copyleft-next's project Code of Conduct.
The repository stands by itself with only files related to the Code
of Conduct for easier review of the changes made to the Code of
Conduct over time.
When a new version of the Code of Conduct is made official for the
copyleft-next project, a squash commit of the changes to the code of
conduct document are brought to the main branch of the copyleft-next
repository.
