Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Contributor Agreement for License Change [Updated] #2273

Open
ZeroNetTickBot opened this issue Nov 3, 2019 · 588 comments
Open

Contributor Agreement for License Change [Updated] #2273

ZeroNetTickBot opened this issue Nov 3, 2019 · 588 comments

Comments

@ZeroNetTickBot
Copy link

ZeroNetTickBot commented Nov 3, 2019 •
edited
Loading

Hello to all previous ZeroNet contributors.

ZeroNet project has recently been informed of some license incompatibilities. Namely, we are using some Apache 2.0 and GPLv3 dependencies, whilst the current ZeroNet license is GPLv2. Thus, I would now ask the contributors to support GPLv3 switch.

A bot is listening on this thread. Please post exactly one of the following 13 comments:

  • GPLv3 and Lax if you accept switching to either GPLv3 or later or to GPLv3-only or a Lax/Permissive license
  • GPLv3+ and Lax if you accept switching to either GPLv3 or later or a Lax/Permissive license
  • GPLv3-only and Lax if you accept switching to either GPLv3-only or a Lax/Permissive license
  • GPLv3+ if you accept switching to GPLv3 or later
  • GPLv3-only if you accept switching to GPLv3-only
  • GPLv3 if you accept switching to either GPLv3 or later or to GPLv3-only
  • AGPLv3 if you accept switching to AGPLv3 (this would require modified ZeorNet proxies to release their modified source code)
  • MIT/BSD2 if you accept switching to MIT or BSD-2-Clause
  • BSD3 if you accept switching to BSD-3-Clause
  • Apache2 if you accept switching to an Apache-2.0
  • Lax if you accept switching to any Lax/Permissive license (except Public Domain)
  • None if you don't accept changing license, or if you want a different license not listed
  • I don't care if you accept switching to whatever issue those who run ZeroNet project want. This is the same as the GPLv3 and Lax option below but it might include more licenses if it's found appropriate

Accepting the first case is recommended: GPLv3 ("and later" or "-only") would be used for ZeroNet core and Lax/Permissive licenses would be used for libraries.

Switching to a Lax/Permissive would require all GPL dependencies to be replaced. Not allowing the switch to a different license (therefore keeping GPLv2) would also require all GPLv3 dependencies, as well as Apache dependencies, to be replaced.

Notice: The term "Lax/Permissive license" used here does not include Public Domain licenses. They do, however, include BSD 2/3, MIT, ISC, and Apache-2.0

Statistics

  • GPLv3+: 68.0% (70)
  • GPLv3-only: 68.9% (71)
  • AGPLv3: 1.9% (2)
  • MIT/BSD2: 51.5% (53)
  • BSD3: 51.5% (53)
  • Apache2: 51.5% (53)
  • Blocking: 1.0% (1)
  • No reply: 30.1% (31)

Contributor list

Passing people

If you're not a contributor but you still want to support this or that option, you can post a comment as well. These comments will appear below.

  • @skwerlman: GPLv3+ and Lax
  • @0x6a73: GPLv3-only and Lax
  • @CatTheHacker: Lax
  • @blazercrypter: GPLv3-only and Lax
  • @alopexc0de: GPLv3-only and Lax
  • @zeronettimemachine: GPLv3+
  • @ghost: GPLv3+
  • @CyberSecurityEngineer: GPLv3+
  • @USAhas8000PlusNuclearBombForSelfDefense: GPLv3+
  • @George-Soros: GPLv3+
  • @Lambeosaurus: GPLv3+
  • @Kusoneko: GPLv3 and Lax
  • @decentralizedauthority: GPLv3+
  • @canewsin: MIT/BSD2
  • @russianagent: GPLv3+
@ghost
Copy link

ghost commented Nov 3, 2019

GPLv3-only and Lax

@ghost ghost mentioned this issue Nov 3, 2019
Closed
@vitorio
Copy link
Contributor

vitorio commented Nov 3, 2019

GPLv3 and Lax

@skwerlman
Copy link

GPLv3+ and Lax

@ghost ghost mentioned this issue Nov 3, 2019
Closed
@mkg20001
Copy link
Contributor

mkg20001 commented Nov 3, 2019

GPLv3+ and Lax

@ghost
Copy link

ghost commented Nov 3, 2019 •
edited by ghost
Loading

Making sure the second-half of the list of contributors get properly mentioned:

@xfq @6543 @ajmeese7 @AceLewis @megfault @Zasei @artemmolotov @Nephos @Austin-Williams @bencevans @valkheim @d14na @thesoftwarejedi @Derson5 @dldx @EdenSG @camponez @Erkan-Yilmaz @Fil @gyulaweber @shakna-israel @flibustier @justinwiley @kseistrup @MRoci @sexybiggetje @BoboTiG @medimatrix @Nodeswitch @Ornataweaver @adrelanos @quasiyoke @Radtoo @RedbHawk @rcmorano @rubo77 @SuperSandro2000 @Thunder33345 @anonym @beigexperience @blurHY @dqwyy @eduaddad @goofy-mdn @krikmo @leycec @mnlg @mymage @probonopd @saber28

@ghost
Copy link

ghost commented Nov 3, 2019

@rwv @sinkuu @zwgshr

@kseistrup
Copy link
Contributor

GPLv3+ and Lax

1 similar comment
@camponez
Copy link
Contributor

camponez commented Nov 4, 2019

GPLv3+ and Lax

@ysc3839
Copy link
Contributor

ysc3839 commented Nov 4, 2019

GPLv3+

@d14na
Copy link
Contributor

d14na commented Nov 4, 2019

GPLv3+ and Lax

@ghost
Copy link

ghost commented Nov 4, 2019 •
edited by ghost
Loading

Just some useful information for people:

Sometimes open-source software projects get stuck in a license incompatibility situation. Often the only feasible way to resolve this situation is re-licensing of all participating software parts. For successful relicensing the agreement of all involved copyright holders, typically the developers, to a changed license is required. While in the free and open-source domain achieving 100% coverage of all authors is often impossible due to the many contributors involved, often it is assumed that a great majority is sufficient. For instance, Mozilla assumed an author coverage of 95% to be sufficient.[4] Others in the FOSS domain, as Eric S. Raymond, came to different conclusions regarding the requirements for relicensing of a whole code base.

https://en.wikipedia.org/wiki/Software_relicensing

@ghost
Copy link

ghost commented Nov 4, 2019

Additionally, if you want to find out more about different licenses, http://tldrlegal.com seems to be a decent resource.

@probonopd
Copy link
Contributor

GPLv3+ and Lax

@sirMackk
Copy link
Contributor

sirMackk commented Nov 4, 2019

GPLv3+

@OliverCole
Copy link
Contributor

GPLv3 and Lax

@eduardoaddad
Copy link
Contributor

GPLv3+

@xfq
Copy link
Contributor

xfq commented Nov 4, 2019

GPLv3+ and Lax

@cclauss
Copy link
Contributor

cclauss commented Nov 4, 2019

Fewer choices was far better for achieving consensus.

@ghost
Copy link

ghost commented Nov 4, 2019 •
edited by ghost
Loading

Maybe.. but we shouldn't be dictating completely what people can choose from, because they have to choose it for themselves (legally). Also, I didn't really add that many more choices.

Basically, what I'm saying is if people naturally fall into a consensus regarding what they actutally want, then more choices doesn't matter. But if we are getting a consensus with less options but not a consensus with more options, then that just means we're kinda shoehorning people into a consensus when that's not what they really want.

The more important change in this update though was to clarify any ambiguity (this is important for legal reasons, along with understandability reasons), so I replaced "Apache" and "Apache-compatible" with "Lax" and was explicit about "Lax" not including the Public Domain.

@6543
Copy link
Contributor

6543 commented Nov 4, 2019

GPLv3+ and Lax

@ghost
Copy link

ghost commented Nov 4, 2019

Btw, polite discussion on licenses are welcome and you can change your vote at any time by posting another comment.

@purplesyringa
Copy link
Contributor

GPLv3 and Lax

@purplesyringa
Copy link
Contributor

purplesyringa commented Nov 4, 2019 •
edited
Loading

@sirMackk @ysc3839 @mkg20001 @xfq @6543 @d14na @camponez @kseistrup @eduaddad @probonopd @skwerlman

I have just noticed that you voted for GPLv3+ . I want to make sure that the GPL options were clear enough, so let me explain it again:

  • GPLv3-only allows us to license the project under the standard GPLv3 license
  • GPLv3+ allows us to license the project under "GPLv3 or later" but not the standard GPLv3 license
  • GPLv3 allows us to use either "GPLv3 or later" or the standard GPLv3 license, whatever we find better or more compatible

@filips123
Copy link
Contributor

GPLv3 and Lax

@purplesyringa
Copy link
Contributor

GPLv3-only and Lax

@filips123
Copy link
Contributor

Relicensing as GPLv3 and Lax would be needed in case we make ZeroNet more modularized (#2063) in the future. In this case, ZeroNet libraries (protocol handling and other more low-level things) would then be licensed as Lax license (MIT/BSD). Complete ZeroNet program would then be licensed as GPLv3.

This could help making ZeroNet more popular as developers would have already-created modular libraries for extending/building with ZeroNet. Lax license would be needed as such licenses (MIT/BSD) have the ability to be used in most other licenses, so developers won't have to worry about license compatibility so much.

@goofy-mdn
Copy link
Contributor

Lax

@purplesyringa
Copy link
Contributor

@goofy-mdn Just to make sure: choosing Lax means that we'll have to rewrite all libraries and make others support Lax as well, or remove your contributions. Are you fine with that?

@purplesyringa
Copy link
Contributor

They could be treated differently if it was specified before...

@HelloZeroNet
Copy link
Owner

I'm ready to change it to GPLv3, but I'm a bit confused if there is separate license.txt for GPLv3 and GPLv3+, because I can't find any other version of it, but all same as https://raw.githubusercontent.com/emacs-mirror/emacs/master/COPYING
Which is GPLv3+ according to wikipedia.

@purplesyringa
Copy link
Contributor

In fact, the license itself doesn't vary, it's the Standard License Header which does:

GPLv3-only:

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, version 3.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.

GPLv3+:

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see <https://www.gnu.org/licenses/>.

@adrelanos
Copy link
Contributor

adrelanos commented Mar 17, 2020 via email

@purplesyringa
Copy link
Contributor

True, I wasn't showing the license but the Standard License Header.

HelloZeroNet pushed a commit that referenced this issue Mar 17, 2020
@shortcutme
Change to GPLv3 license
5fb342a 
Based on #2273
@HelloZeroNet
Copy link
Owner

Thanks, I have added the header to the LICENSE file + the standard COPYING:
5fb342a

If its fine this way, then I think we can close this issue.

@purplesyringa
Copy link
Contributor

Great, I wouldn't close this issue yet though, we should get rid of these contributions before.

@HostFat
Copy link
Contributor

HostFat commented Mar 17, 2020

How can my translation be used again with the new license?

@purplesyringa
Copy link
Contributor

@HostFat We'll sure replace it soon I guess, unless you are ready to license it under GPLv3.

@HostFat
Copy link
Contributor

HostFat commented Mar 17, 2020

Well, I'm ready I guess, what I need to do? :)

@purplesyringa
Copy link
Contributor

Just post a comment "GPLv3" under this issue.

@HostFat
Copy link
Contributor

HostFat commented Mar 17, 2020

GPLv3

@purplesyringa
Copy link
Contributor

Thanks, I've updated the list.

@canewsin
Copy link
Contributor

canewsin commented Mar 17, 2020 •
edited
Loading

it is better to segregate non code licenses from now,
for eg see here https://choosealicense.com/non-software/
put a note on contributing to this ZeroNet repo readme that non-code license will be treated differently

Non-Software Licenses
Open source software licenses can be also used for non-software works and are often the best choice, especially when the works in question can be edited and versioned as source (e.g., open source hardware designs). Choose an open source license here.

Data, media, etc.
CC0-1.0, CC-BY-4.0, and CC-BY-SA-4.0 are open licenses used for non-software material ranging from datasets to videos. Note that CC-BY-4.0 and CC-BY-SA-4.0 should not be used for software.

Documentation
Any open source software license or open license for media (see above) also applies to software documentation. If you use different licenses for your software and its documentation, be sure to specify that source code examples in the documentation are also licensed under the software license.

Fonts
The SIL Open Font License 1.1 keeps fonts open but allows them to be freely used in other works.

Mixed Projects
If your project contains a mix of software and other material, you can include multiple licenses, as long as you are explicit about which license applies to each part of the project. See the license notice for this site as an example.

usually translations are treated as datasets to main code language strings
even the typo fixes can be treated like this. since I has some legal background with my studies I can interpret these as above.

@canewsin
Copy link
Contributor

@HelloZeroNet
if you need, I will draft some additional info for contribution practices for repository for these type of contributions. This will reduce future headache of spam/fights between contributors.

@purplesyringa
Copy link
Contributor

Yes, please.

@canewsin
Copy link
Contributor

canewsin commented Mar 18, 2020 •
edited
Loading

@imachug @HelloZeroNet

Contributing to this repo

This repo is governed by GPLv3, same is located at the root of the ZeroNet git repo, unless specified separately all code is governed by that license, contributions to this repo are divided into two key types, key contributions and non-key contributions, key contributions are which, directly affects the code performance, quality and features of software, non key contributions include things like translation datasets, image, graphic or video contributions that does not affect the main usability of software but improves the existing usability of certain thing or feature, these also include tests written with code, since their purpose is to check, whether something is working or not as intended. Unless specified above a contribution is ruled by the type of contribution if there is a conflict between two contributing parties of repo in any case.

@danimesq
Copy link
Contributor

GPLv3

@HelloZeroNet
Copy link
Owner

@canewsin:
What if we say:

Any code: GPLv3
Non key contributions include things like translation datasets, image, graphic or video contributions that does not affect the main usability of software but improves the existing usability: https://creativecommons.org/licenses/by-sa/3.0/

@canewsin
Copy link
Contributor

canewsin commented Mar 18, 2020 •
edited
Loading

@HelloZeroNet cc 3.0 is perfect for non-code contributions, I first had a thought on that, but forgot add it.

@canewsin
Copy link
Contributor

@HelloZeroNet Added cc 4.0, which is translated to more languages than 3.0, check this pull #2492

@ghost
Copy link

ghost commented Mar 31, 2020 •
edited by ghost
Loading

@HelloZeroNet and you (@canewsin) suggested CC license for documentation.
Here is my suggestion:

`
GNU Free Documentation License
Version 1.3, 3 November 2008

Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
https://fsf.org/
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

  1. PREAMBLE

The purpose of this License is to make a manual, textbook, or other
functional and useful document "free" in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or noncommercially.
Secondarily, this License preserves for the author and publisher a way
to get credit for their work, while not being considered responsible
for modifications made by others.

This License is a kind of "copyleft", which means that derivative
works of the document must themselves be free in the same sense. It
complements the GNU General Public License, which is a copyleft
license designed for free software.

We have designed this License in order to use it for manuals for free
software, because free software needs free documentation: a free
program should come with manuals providing the same freedoms that the
software does. But this License is not limited to software manuals;
it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.

  1. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
work under the conditions stated herein. The "Document", below,
refers to any such manual or work. Any member of the public is a
licensee, and is addressed as "you". You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.

A "Modified Version" of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of
the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document's overall
subject (or to related matters) and contains nothing that could fall
directly within that overall subject. (Thus, if the Document is in
part a textbook of mathematics, a Secondary Section may not explain
any mathematics.) The relationship could be a matter of historical
connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.

The "Invariant Sections" are certain Secondary Sections whose titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License. If a
section does not fit the above definition of Secondary then it is not
allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant
Sections then there are none.

The "Cover Texts" are certain short passages of text that are listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License. A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.

A "Transparent" copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
pixels) generic paint programs or (for drawings) some widely available
drawing editor, and that is suitable for input to text formatters or
for automatic translation to a variety of formats suitable for input
to text formatters. A copy made in an otherwise Transparent file
format whose markup, or absence of markup, has been arranged to thwart
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
of text. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format, SGML
or XML using a publicly available DTD, and standard-conforming simple
HTML, PostScript or PDF designed for human modification. Examples of
transparent image formats include PNG, XCF and JPG. Opaque formats
include proprietary formats that can be read and edited only by
proprietary word processors, SGML or XML for which the DTD and/or
processing tools are not generally available, and the
machine-generated HTML, PostScript or PDF produced by some word
processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, "Title Page" means
the text near the most prominent appearance of the work's title,
preceding the beginning of the body of the text.

The "publisher" means any person or entity that distributes copies of
the Document to the public.

A section "Entitled XYZ" means a named subunit of the Document whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language. (Here XYZ stands for a
specific section name mentioned below, such as "Acknowledgements",
"Dedications", "Endorsements", or "History".) To "Preserve the Title"
of such a section when you modify the Document means that it remains a
section "Entitled XYZ" according to this definition.

The Document may include Warranty Disclaimers next to the notice which
states that this License applies to the Document. These Warranty
Disclaimers are considered to be included by reference in this
License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.

  1. VERBATIM COPYING

You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies
to the Document are reproduced in all copies, and that you add no
other conditions whatsoever to those of this License. You may not use
technical measures to obstruct or control the reading or further
copying of the copies you make or distribute. However, you may accept
compensation in exchange for copies. If you distribute a large enough
number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and
you may publicly display copies.

  1. COPYING IN QUANTITY

If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
Document's license notice requires Cover Texts, you must enclose the
copies in covers that carry, clearly and legibly, all these Cover
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
the back cover. Both covers must also clearly and legibly identify
you as the publisher of these copies. The front cover must present
the full title with all words of the title equally prominent and
visible. You may add other material on the covers in addition.
Copying with changes limited to the covers, as long as they preserve
the title of the Document and satisfy these conditions, can be treated
as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto adjacent
pages.

If you publish or distribute Opaque copies of the Document numbering
more than 100, you must either include a machine-readable Transparent
copy along with each Opaque copy, or state in or with each Opaque copy
a computer-network location from which the general network-using
public has access to download using public-standard network protocols
a complete Transparent copy of the Document, free of added material.
If you use the latter option, you must take reasonably prudent steps,
when you begin distribution of Opaque copies in quantity, to ensure
that this Transparent copy will remain thus accessible at the stated
location until at least one year after the last time you distribute an
Opaque copy (directly or through your agents or retailers) of that
edition to the public.

It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to
give them a chance to provide you with an updated version of the
Document.

  1. MODIFICATIONS

You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
the Modified Version under precisely this License, with the Modified
Version filling the role of the Document, thus licensing distribution
and modification of the Modified Version to whoever possesses a copy
of it. In addition, you must do these things in the Modified Version:

A. Use in the Title Page (and on the covers, if any) a title distinct
from that of the Document, and from those of previous versions
(which should, if there were any, be listed in the History section
of the Document). You may use the same title as a previous version
if the original publisher of that version gives permission.
B. List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the Modified
Version, together with at least five of the principal authors of the
Document (all of its principal authors, if it has fewer than five),
unless they release you from this requirement.
C. State on the Title page the name of the publisher of the
Modified Version, as the publisher.
D. Preserve all the copyright notices of the Document.
E. Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
F. Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.
G. Preserve in that license notice the full lists of Invariant Sections
and required Cover Texts given in the Document's license notice.
H. Include an unaltered copy of this License.
I. Preserve the section Entitled "History", Preserve its Title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page. If
there is no section Entitled "History" in the Document, create one
stating the title, year, authors, and publisher of the Document as
given on its Title Page, then add an item describing the Modified
Version as stated in the previous sentence.
J. Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on. These may be placed in the "History" section.
You may omit a network location for a work that was published at
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.
K. For any section Entitled "Acknowledgements" or "Dedications",
Preserve the Title of the section, and preserve in the section all
the substance and tone of each of the contributor acknowledgements
and/or dedications given therein.
L. Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles. Section numbers
or the equivalent are not considered part of the section titles.
M. Delete any section Entitled "Endorsements". Such a section
may not be included in the Modified Version.
N. Do not retitle any existing section to be Entitled "Endorsements"
or to conflict in title with any Invariant Section.
O. Preserve any Warranty Disclaimers.

If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no material
copied from the Document, you may at your option designate some or all
of these sections as invariant. To do this, add their titles to the
list of Invariant Sections in the Modified Version's license notice.
These titles must be distinct from any other section titles.

You may add a section Entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
parties--for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of a
standard.

You may add a passage of up to five words as a Front-Cover Text, and a
passage of up to 25 words as a Back-Cover Text, to the end of the list
of Cover Texts in the Modified Version. Only one passage of
Front-Cover Text and one of Back-Cover Text may be added by (or
through arrangements made by) any one entity. If the Document already
includes a cover text for the same cover, previously added by you or
by arrangement made by the same entity you are acting on behalf of,
you may not add another; but you may replace the old one, on explicit
permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.

  1. COMBINING DOCUMENTS

You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and
list them all as Invariant Sections of your combined work in its
license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name but
different contents, make the title of each such section unique by
adding at the end of it, in parentheses, the name of the original
author or publisher of that section if known, or else a unique number.
Make the same adjustment to the section titles in the list of
Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled "History"
in the various original documents, forming one section Entitled
"History"; likewise combine any sections Entitled "Acknowledgements",
and any sections Entitled "Dedications". You must delete all sections
Entitled "Endorsements".

  1. COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other
documents released under this License, and replace the individual
copies of this License in the various documents with a single copy
that is included in the collection, provided that you follow the rules
of this License for verbatim copying of each of the documents in all
other respects.

You may extract a single document from such a collection, and
distribute it individually under this License, provided you insert a
copy of this License into the extracted document, and follow this
License in all other respects regarding verbatim copying of that
document.

  1. AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
distribution medium, is called an "aggregate" if the copyright
resulting from the compilation is not used to limit the legal rights
of the compilation's users beyond what the individual works permit.
When the Document is included in an aggregate, this License does not
apply to the other works in the aggregate which are not themselves
derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half of
the entire aggregate, the Document's Cover Texts may be placed on
covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.

  1. TRANSLATION

Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
translations of some or all Invariant Sections in addition to the
original versions of these Invariant Sections. You may include a
translation of this License, and all the license notices in the
Document, and any Warranty Disclaimers, provided that you also include
the original English version of this License and the original versions
of those notices and disclaimers. In case of a disagreement between
the translation and the original version of this License or a notice
or disclaimer, the original version will prevail.

If a section in the Document is Entitled "Acknowledgements",
"Dedications", or "History", the requirement (section 4) to Preserve
its Title (section 1) will typically require changing the actual
title.

  1. TERMINATION

You may not copy, modify, sublicense, or distribute the Document
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense, or distribute it is void, and
will automatically terminate your rights under this License.

However, if you cease all violation of this License, then your license
from a particular copyright holder is reinstated (a) provisionally,
unless and until the copyright holder explicitly and finally
terminates your license, and (b) permanently, if the copyright holder
fails to notify you of the violation by some reasonable means prior to
60 days after the cessation.

Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.

Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, receipt of a copy of some or all of the same material does
not give you any rights to use it.

  1. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of the
GNU Free Documentation License from time to time. Such new versions
will be similar in spirit to the present version, but may differ in
detail to address new problems or concerns. See
https://www.gnu.org/licenses/.

Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
License "or any later version" applies to it, you have the option of
following the terms and conditions either of that specified version or
of any later version that has been published (not as a draft) by the
Free Software Foundation. If the Document does not specify a version
number of this License, you may choose any version ever published (not
as a draft) by the Free Software Foundation. If the Document
specifies that a proxy can decide which future versions of this
License can be used, that proxy's public statement of acceptance of a
version permanently authorizes you to choose that version for the
Document.

  1. RELICENSING

"Massive Multiauthor Collaboration Site" (or "MMC Site") means any
World Wide Web server that publishes copyrightable works and also
provides prominent facilities for anybody to edit those works. A
public wiki that anybody can edit is an example of such a server. A
"Massive Multiauthor Collaboration" (or "MMC") contained in the site
means any set of copyrightable works thus published on the MMC site.

"CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0
license published by Creative Commons Corporation, a not-for-profit
corporation with a principal place of business in San Francisco,
California, as well as future copyleft versions of that license
published by that same organization.

"Incorporate" means to publish or republish a Document, in whole or in
part, as part of another Document.

An MMC is "eligible for relicensing" if it is licensed under this
License, and if all works that were first published under this License
somewhere other than this MMC, and subsequently incorporated in whole or
in part into the MMC, (1) had no cover texts or invariant sections, and
(2) were thus incorporated prior to November 1, 2008.

The operator of an MMC Site may republish an MMC contained in the site
under CC-BY-SA on the same site at any time before August 1, 2009,
provided the MMC is eligible for relicensing.

ADDENDUM: How to use this License for your documents

To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
license notices just after the title page:

Copyright (c)  YEAR  YOUR NAME.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the section entitled "GNU
Free Documentation License".

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
replace the "with...Texts." line with this:

with the Invariant Sections being LIST THEIR TITLES, with the
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.

If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.

If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of
free software license, such as the GNU General Public License,
to permit their use in free software.
`

I hope @imachug and @filips123 also fine with this license.

@ghost ghost mentioned this issue Mar 31, 2020
Closed
This was referenced Aug 18, 2020
Closed
Closed
@caryoscelus caryoscelus mentioned this issue Jun 28, 2022
Open
@caryoscelus
Copy link
Contributor

to anyone concerned : zeronet-conservancy is GPLv3+ for all new contributions . further discussion

@aitorpazos
Copy link
Contributor

GPLv3+

@ghost ghost mentioned this issue Mar 12, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests