search

asciidoctor / asciidoctor.org

:globe_with_meridians: Asciidoctor project site. Composed in AsciiDoc. Baked with Awestruct.
https://asciidoctor.org
Other
322 stars 807 forks source link

Call for acceptance of license upgrade #978

Closed mojavelinux closed 3 years ago

mojavelinux commented 3 years ago

The portion of the Asciidoctor user manual that covers the AsciiDoc language has been split off and proposed as an initial contribution for the AsciiDoc Language project. The goal of the AsciiDoc Language project is to create a specification for AsciiDoc.

As part of this submission, we've been asked to upgrade the license from CC-BY-3.0 to CC BY 4.0. In order for this contribution to pass legal, we need each person named in the initial contribution to confirm acceptance of this license upgrade.

The contributors to the portion of the documentation that was included in the initial contribution proposal are as follows:

To accept this license upgrade, please reply to this thread with the following comment:

I acknowledge that my contribution to the Asciidoctor documentation was licensed under a CC-BY-3.0 license. I agree for my contribution to the Asciidoctor documentation to be licensed under a CC BY 4.0 license.

Note that this change is only being made to the initial contribution and not the Asciidoctor documentation as a whole. (We'll deal with that separately).

mojavelinux commented 3 years ago

I acknowledge that my contribution to the Asciidoctor documentation was licensed under a CC-BY-3.0 license. I agree for my contribution to the Asciidoctor documentation to be licensed under a CC BY 4.0 license.

ggrossetie commented 3 years ago

I acknowledge that my contribution to the Asciidoctor documentation was licensed under a CC-BY-3.0 license. I agree for my contribution to the Asciidoctor documentation to be licensed under a CC BY 4.0 license.

danyill commented 3 years ago

I acknowledge that my contribution to the Asciidoctor documentation was licensed under a CC-BY-3.0 license. I agree for my contribution to the Asciidoctor documentation to be licensed under a CC BY 4.0 license.

On Mon, Nov 30, 2020 at 9:26 PM Guillaume Grossetie < notifications@github.com> wrote:

I acknowledge that my contribution to the Asciidoctor documentation was licensed under a CC-BY-3.0 license. I agree for my contribution to the Asciidoctor documentation to be licensed under a CC BY 4.0 license.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/asciidoctor/asciidoctor.org/issues/978#issuecomment-735634943, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFEXX5XE322SVASRPQJZR3SSNJMTANCNFSM4UHHLWAA .

--

-- Private or confidential message? Public Key available here https://pgp.mit.edu/pks/lookup?search=dan.mulholland%40gmail.com&op=index :

jaredmorgs commented 3 years ago

I acknowledge that my contribution to the Asciidoctor documentation was licensed under a CC-BY-3.0 license. I agree for my contribution to the Asciidoctor documentation to be licensed under a CC BY 4.0 license.

On Mon, 30 Nov 2020, 18:24 Dan Allen, notifications@github.com wrote:

The portion of the Asciidoctor user manual that covers the AsciiDoc language has been split off https://github.com/asciidoctor/asciidoc-docs/tree/ic and proposed as an initial contribution for the AsciiDoc Language project https://projects.eclipse.org/projects/technology.asciidoc. The goal of the AsciiDoc Language project is to create a specification for AsciiDoc.

As part of this submission, we've been asked to upgrade the license from CC-BY-3.0 https://creativecommons.org/licenses/by/3.0/ to CC BY 4.0 https://creativecommons.org/licenses/by/4.0/. In order for this contribution to pass legal, we need each person named in the initial contribution to confirm acceptance of this license upgrade.

The contributors to the portion of the documentation that was included in the initial contribution proposal are as follows:

To accept this license upgrade, please reply to this thread with the following comment:

I acknowledge that my contribution to the Asciidoctor documentation was licensed under a CC-BY-3.0 license. I agree for my contribution to the Asciidoctor documentation to be licensed under a CC BY 4.0 license.

Note that this change is only being made to the initial contribution and not the Asciidoctor documentation as a whole. (We'll deal with that separately).

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/asciidoctor/asciidoctor.org/issues/978, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHITWMPH6L2TD4V66LLM5LSSNJDVANCNFSM4UHHLWAA .

andrewcarver commented 3 years ago

I acknowledge that my contribution to the Asciidoctor documentation was licensed under a CC-BY-3.0 license. I agree for my contribution to the Asciidoctor documentation to be licensed under a CC BY 4.0 license.

graphitefriction commented 3 years ago

I acknowledge that my contribution to the Asciidoctor documentation was licensed under a CC-BY-3.0 license. I agree for my contribution to the Asciidoctor documentation to be licensed under a CC BY 4.0 license.

mojavelinux commented 3 years ago

Thanks to all who have replied and accepted!

ping @bk2204 and @rockyallen.

bk2204 commented 3 years ago

I rather prefer the 3.0 versions of the CC licenses over the 4.0 versions, but not enough to block the upgrade. So:

I acknowledge that my contribution to the Asciidoctor documentation was licensed under a CC-BY-3.0 license. I agree for my contribution to the Asciidoctor documentation to be licensed under a CC BY 4.0 license.

mojavelinux commented 3 years ago

Thanks @bk2204!

Out of curiosity, I'd definitely be interested to know why you prefer the 3.0 versions. I find these kinds of preferences to be of great interest to me. Feel free to e-mail me if you'd like to share your thoughts in private.

bk2204 commented 3 years ago

Sure.

To explain a little more in detail, I think the CC 4.0 license reinstatement provisions can be read in a way where a user can repeatedly violate the license, and as long as they fix the violation each time they're notified of it, the license is reinstated. My concern is that it disincentivizes license compliance and means that large organizations can mostly ignore licensing, provide a token response to satisfy the individual licensor if caught, willfully ignore licensing for similar works or licensors (so as not to discover the violation), and mostly escape consequences. I agree the intention of the clauses is good, but I feel they have some practical problems as written, and I'm pretty sure that there are folks taking advantage of those problems.

So since I haven't found a reinstatement clause that I'm really comfortable with, I prefer the CC 3.0 licenses and GPLv2 over the CC 4.0 licenses and GPLv3. I don't think that should hold up the creation of an AsciiDoc spec, though, and my contributions to the documentation have been relatively minor, so I don't want to be an impediment to having things which I strongly support get done. That's why I made the decision to relicense here.

rockyallen commented 3 years ago

Sorry-I thought I had already done this.

"I acknowledge that my contribution to the Asciidoctor documentation was licensed under a CC-BY-3.0 license. I agree for my contribution to the Asciidoctor documentation to be licensed under a CC BY 4.0 license."

If it helps, I am happy to transfer all my rights(?) contributions(?) to the asciidoctor project or to Dan.

mojavelinux commented 3 years ago

Thanks to all! We appreciate both your contributions and your cooperation to help this to move forward.

mojavelinux commented 3 years ago

@bk2204 Thank you so much for sharing that insight. That really helps me understand the differences between these license versions and to understand how the new version fits with my personal values / goals. I have passed on your comment to the legal team for review and consideration.

One thing to keep in mind is that the spec itself will be licensed under the EPLv2. The CC 4.0 BY is for the user-oriented guide, which is both the initial contribution and an ongoing companion doc to the spec.