parent
5227253585
commit
7fb9a201e5
GPG Key ID:
F890265DD80E4E90
@ -0,0 +1,380 @@
|
||||
# Yzena Copyleft User License Frequently Asked Questions
|
||||
|
||||
1. **What is the [Yzena Copyleft User License (YCUL)][faq-0]?**
|
||||
|
||||
It is a permissive [copyleft][faq-copyleft] license that prohibits
|
||||
Tivoization and weaponizing software against users.
|
||||
|
||||
2. **Is the YCUL [viral][faq-viral] like the [GNU GPL][faq-gpl] and [GNU
|
||||
AGPL][faq-agpl]?**
|
||||
|
||||
No, it's explicitly *not* viral. In my opinion, virality is parasitic and
|
||||
has caused people to use closed-source software instead of FOSS alternatives
|
||||
when those alternatives were licensed under the [GPL][faq-gpl] and
|
||||
[AGPL][faq-agpl].
|
||||
|
||||
3. **Who are you? And are you a lawyer?**
|
||||
|
||||
I am [Gavin D. Howard][faq-gavinhoward], founder of [Yzena][faq-yzena].
|
||||
|
||||
No, I am not a lawyer, but most of this license is taken from the [Blue Oak
|
||||
Model License 1.0.0][faq-boml] (BOML), which *was* written by lawyers.
|
||||
|
||||
4. **Why did you choose the [BOML][faq-boml] to start with?**
|
||||
|
||||
See [here][faq-license_notices], [here][faq-chalkeaters],
|
||||
[here][faq-mit_deprecation], and [here][faq-boml_faq]. Basically, the
|
||||
[BOML][faq-boml] is supposed to be a model for how licenses should be.
|
||||
|
||||
5. **What is the list of changes you made from the [BOML][faq-boml]?**
|
||||
|
||||
These are the changes I made:
|
||||
|
||||
* Added to the [Purpose][faq-purpose] section about publishing changes.
|
||||
* Added the [Source Code][faq-source_code] section.
|
||||
* Added the [This Software][faq-this_software] section.
|
||||
* Added the [Combined Software][faq-combined_software] section.
|
||||
* Added the [Application][faq-application] section.
|
||||
* Added the [User Agency][faq-user-agency] section.
|
||||
* Added the [Compatibility][faq-compatibility] section.
|
||||
* Added the [Distribution][faq-distribution] section.
|
||||
* Made it a requirement to give users the full license in the
|
||||
[Notices][faq-notices] section.
|
||||
* Added the [Credits][faq-credits] section.
|
||||
* Added the [Trademarks][faq-trademarks] section.
|
||||
* Added the [Litigation][faq-litigation] section.
|
||||
* Added the [Non-Interference][faq-non-interference] section.
|
||||
* Added the [Respecting User Choice][faq-respecting_user_choice] section.
|
||||
* Changed the [Excuse][faq-excuse] section such that any *contributor* has
|
||||
to give notice of non-compliance, instead of *anyone*.
|
||||
* Added references to the [Distribution][faq-distribution],
|
||||
[Credits][faq-credits], [Trademarks][faq-trademarks], and
|
||||
[Litigation][faq-litigation] sections in the [Excuse][faq-excuse] section.
|
||||
* Tweaked the [Reliability][faq-reliability] section.
|
||||
|
||||
6. **If you mostly copied the [BOML][faq-boml], why shouldn't I just use that
|
||||
one?**
|
||||
|
||||
You actually should; if all you need is a typical permissive license, then
|
||||
yes, you should use the [BOML][faq-boml].
|
||||
|
||||
However, there are three clauses in the YCUL that are not in the
|
||||
[BOML][faq-boml]:
|
||||
|
||||
* [Credits][faq-credits] for giving credit,
|
||||
* [Trademarks][faq-trademarks] for protecting trademarks,
|
||||
* [Litigation][faq-litigation] for prohibiting patent litigation.
|
||||
|
||||
If you need those three things in a license, then the YCUL might work for
|
||||
you. Be sure to consult with your lawyer first.
|
||||
|
||||
In addition, this is also a [copyleft][faq-copyleft] license that requires
|
||||
respecting user agency, so if that's what you need, that is another reason
|
||||
the YCUL might work better for you. Again, be sure to consult with your
|
||||
lawyer first.
|
||||
|
||||
7. **Why do you use such vague language and don't define some of your terms?**
|
||||
|
||||
Because the [BOML][faq-boml] doesn't. See more [here][faq-license_notices]
|
||||
and [here][faq-chalkeaters]. I decided that if lawyers did it, it should be
|
||||
fine.
|
||||
|
||||
8. **Your [Credits][faq-credits] section doesn't actually require giving
|
||||
credit.**
|
||||
|
||||
No, it doesn't. But it does require providing the verbatim text of the
|
||||
`CREDITS.md` or `NOTICE.md` file, and I assumed that the contributors would
|
||||
add whatever credits they wanted in there.
|
||||
|
||||
9. **You also don't require giving a link to the original project, if someone
|
||||
makes changes and relicenses the code.**
|
||||
|
||||
No, but I also assumed that the original contributors would put that
|
||||
information in the `CREDITS.md` or `NOTICE.md`, and that text must be
|
||||
provided verbatim.
|
||||
|
||||
That assumption simplified the license, which makes things easier on
|
||||
contributors *and* users.
|
||||
|
||||
10. **Why does the [Credits][faq-credits] section require that the file be in
|
||||
the [Markdown][faq-markdown] format?**
|
||||
|
||||
It made it easier to write the license and will make it easier to comply
|
||||
with the license.
|
||||
|
||||
More concretely, the [Apache 2.0 License][faq-apache_license] uses the
|
||||
phrase "NOTICE file." I decided to avoid that awkward language.
|
||||
|
||||
And while I could have chosen any file format, [Markdown][faq-markdown] is
|
||||
text, easily readable, well-supported (with ways to convert it), and should
|
||||
have all of the features that would be needed for such a file.
|
||||
|
||||
11. **The [Credits][faq-credits] section says that it is required to provide the
|
||||
verbatim text of the `CREDITS.md` or `NOTICE.md` file. Why didn't you just
|
||||
require people to provide the file?**
|
||||
|
||||
Because if someone makes changes to the software, I wanted them to be able
|
||||
to add their own credits to the `CREDITS.md` or `NOTICE.md` file, which they
|
||||
can do by adding theirs at the bottom or the top of the original, since the
|
||||
verbatim text of the original will still be intact.
|
||||
|
||||
12. **What do you suggest putting in the `CREDITS.md` or `NOTICE.md` file?**
|
||||
|
||||
I suggest adding these things:
|
||||
|
||||
* The name of the original software.
|
||||
* The original copyrights on the software.
|
||||
* A link to the original code/repository.
|
||||
* A link to the [Yzena Copyleft User License][faq-0] to inform users that it is
|
||||
possible to get the original under this license if they wish.
|
||||
* The (preferred) names of all contributors that want credit.
|
||||
|
||||
I also suggest having a paragraph that says:
|
||||
|
||||
> All files in this repository are under the Yzena Copyleft User License, Version
|
||||
> 0.1, and all such files are considered part of the "source code" as
|
||||
> defined by that license.
|
||||
|
||||
In addition, if there are files in the repository that used to be under any
|
||||
licenses other than the YCUL, then I suggest listing all such files, along
|
||||
with their respective former licenses and copyrights, as required by their
|
||||
former licenses, but to also make clear that the files have been relicensed.
|
||||
|
||||
13. **The previous question implies that everything in a repository should be
|
||||
under the YCUL. What if there is code that is under other licenses?**
|
||||
|
||||
Such code should be relicensed, if possible. This is possible with
|
||||
permissive licenses.
|
||||
|
||||
If it is not possible, then such code should *not* be integrated into the
|
||||
repository.
|
||||
|
||||
14. **Does this mean that any code under the GPL family of licenses should not
|
||||
be integrated into a repository under the YCUL?**
|
||||
|
||||
Yes.
|
||||
|
||||
15. **Why do you care about patents and trademarks?**
|
||||
|
||||
Because I want to be able to make a business based on Open Source software,
|
||||
and I do not want to have to worry about losing trademarks or possibly
|
||||
getting sued for patent infringement.
|
||||
|
||||
Also, software patents are, in my opinion, illegal because you can't patent
|
||||
algorithms. They have also never been used for actual innovation, which
|
||||
makes them useless.
|
||||
|
||||
16. **Why did you not use a sunset clause, like [copyleft-next][faq-sunset]?
|
||||
That seems like a good idea.**
|
||||
|
||||
It *is* a good idea, since the term of copyright is [much longer than it
|
||||
should be][faq-ctea].
|
||||
|
||||
However, unlike movies or other works of art, software is constantly
|
||||
changing. So if there was such a sunset clause in YCUL, it might be ambiguous
|
||||
whether or not the clause applies to all of the software, or just those
|
||||
portions that have existed as long as the sunset term.
|
||||
|
||||
Instead, I opted to keep the [BOML][faq-boml]'s
|
||||
[Reliability][faq-reliability] clause, which should serve the same purpose.
|
||||
|
||||
17. **Why did you not use a nullification of copyright clause, like
|
||||
[copyleft-next][faq-nullification], to prevent proprietary dual licensing?**
|
||||
|
||||
While that clause is also a good idea, its purpose is also somewhat
|
||||
fulfilled by the [Reliability][faq-reliability] clause.
|
||||
|
||||
18. **What's with the weird definition for ["this
|
||||
software"][faq-this_software]?**
|
||||
|
||||
[GitHub Copilot][faq-copilot]. I want the YCUL to poison the well for machine
|
||||
learning like that.
|
||||
|
||||
The reason is that GitHub is arguing that using FOSS code in
|
||||
[Copilot][faq-copilot] is fair use because using data for training a machine
|
||||
learning algorithm has been [labelled as fair use][faq-fair_use].
|
||||
|
||||
However, even though the *training* is supposedly fair use, that doesn't
|
||||
mean that the *distribution* of the *output* of such algorithms is fair use.
|
||||
|
||||
The definition of ["this software"][faq-this_software] is crafted to exploit
|
||||
this discrepancy.
|
||||
|
||||
19. **But maybe the output of the algorithm is under fair use as well.**
|
||||
|
||||
If it is, then copyright disappears entirely from software. The reason for
|
||||
this is that we already use algorithms to transform our software. We call
|
||||
those algorithms "compilers," and their output "executables" or "libraries."
|
||||
No one claims that a source code's copyright does not apply to the binary
|
||||
forms output by a compiler.
|
||||
|
||||
20. **What if the output of a machine learning algorithm is transformative?
|
||||
Would that not be enough to defeat copyright?**
|
||||
|
||||
A compiler's output is *also* transformative, especially if it does
|
||||
optimizations. This especially applies if the compiler is doing [link-time
|
||||
optimization][faq-lto] using [inlining][faq-inlining] with code from
|
||||
different sources. In that situation, a compiler is combining multiple
|
||||
sources in non-obvious ways, just as machine learning models do.
|
||||
|
||||
A compiler can even [transform an `O(n)` algorithm into an `O(1)`
|
||||
algorithm][faq-algorithm_transform]!
|
||||
|
||||
In other words, unless [GitHub Copilot][faq-copilot] wants to throw out
|
||||
copyright on software completely, this license will apply to the output of
|
||||
its model.
|
||||
|
||||
21. **Why didn't you just add a clause protecting the output of machine
|
||||
learning?**
|
||||
|
||||
I think the definition is wonderfully broad in a way that is best for end
|
||||
users, which is my central purpose: to serve end users who are hurt most by
|
||||
proprietary software.
|
||||
|
||||
In addition, I don't know what sorts of things will be done to software in
|
||||
the future, and I want to future-proof this license as much as possible.
|
||||
|
||||
22. **Your extra restrictions make your license incompatible with the
|
||||
[GPL][faq-gpl] and [AGPL][faq-agpl].**
|
||||
|
||||
I don't think so.
|
||||
|
||||
First, they are not extra restrictions; they codify something that I believe
|
||||
already exists in the [GPL][faq-gpl] and friends.
|
||||
|
||||
Second, even if they *are* extra restrictions (which would make this license
|
||||
incompatible with the [GPL][faq-gpl]), I think I am okay with that.
|
||||
|
||||
In fact, if my licenses are not compatible with the [GPL][faq-gpl] and
|
||||
friends, then I will keep the terms I have and accept the incompatibility. I
|
||||
can do this because these licenses will mostly be used for code in a new
|
||||
language, which means that I wouldn't be able to use existing code easily
|
||||
anyway.
|
||||
|
||||
23. **Your extra restrictions make your license non-Open Source.**
|
||||
|
||||
Once again, I don't think so, and for why, see above. The new parts are not
|
||||
new restrictions; they are clarified.
|
||||
|
||||
But even if the license *is* non-Open Source, I'm not sure I care.
|
||||
|
||||
The reason is this: I believe FOSS licenses have failed. We have so many
|
||||
companies that have used the freedoms we have tried to give *users* in order
|
||||
to extract value (data or something else) unethically from those very users.
|
||||
They do this by claiming the rights of distribution that the FOSS licenses
|
||||
give them and then using those rights to distribute Open Source software to
|
||||
users in such a way that they don't realize that they are being taken
|
||||
advantage of.
|
||||
|
||||
The more I've understood that, the more I have come to realize that the
|
||||
current iteration of FOSS licenses do not work.
|
||||
|
||||
24. **But what *will* work?**
|
||||
|
||||
Remember how I said that companies claim the rights of distribution we give
|
||||
them? As it turns out, *end* users, so-called because they are at the *end*
|
||||
of a chain of distribution, don't usually use distribution rights.
|
||||
|
||||
That means that the next generation of FOSS licenses can probably more
|
||||
heavily restrict how licensed software is distributed while allowing for no
|
||||
restrictions on the other two freedoms of the [four
|
||||
freedoms][faq-four_freedoms].
|
||||
|
||||
I'm not ready to go that far yet. If I was, I'd add a clause forbidding ads
|
||||
in the software. But that is probably the sort of direction we need to go.
|
||||
|
||||
25. **Your license is actually viral, since it makes the license apply to the
|
||||
full output of algorithms.**
|
||||
|
||||
I carefully defined ["source code"][faq-source_code] to ensure that was not
|
||||
the case.
|
||||
|
||||
You see, while the license *does* apply to the entire output, the
|
||||
requirement is still to provide *only* the source code of the original.
|
||||
There is no requirement to provide the source code of the *entire* combined
|
||||
software.
|
||||
|
||||
26. **Why did you say that ["this software"][faq-this_software] only includes
|
||||
output of algorithms that is itself software?**
|
||||
|
||||
Technically, you can run software through things like [hash
|
||||
functions][faq-hash_functions], which are algorithms, and the output is
|
||||
entirely unusable as software. Saying that the license would apply to output
|
||||
like that would never work.
|
||||
|
||||
The same goes for [static analysis][faq-static_analysis] tools. They don't
|
||||
usually output something that can be considered "software"; instead, they
|
||||
output a list of problems with the software. I wouldn't want that to be
|
||||
affected by this license.
|
||||
|
||||
In other words, that little part of the definition is required from making
|
||||
the definition so broad that it becomes useless.
|
||||
|
||||
27. **Your definition of ["this software"][faq-this_software] has "this
|
||||
software" in the definition.**
|
||||
|
||||
That's because the definition is recursive. The base case is the [source
|
||||
code][faq-source_code] of the software, and then whenever the [source
|
||||
code][faq-source_code], or the result of transforming ["this
|
||||
software"][faq-this_software] is transformed by an algorithm, the definition
|
||||
recursively applies.
|
||||
|
||||
28. **Why did you [define "source code"][faq-source_code]?**
|
||||
|
||||
In order to make this license non-viral and because of the recursive
|
||||
definition of ["this software"][faq-this_software]. See the previous
|
||||
question.
|
||||
|
||||
29. **Why did you write this FAQ when nobody has asked you any questions yet?**
|
||||
|
||||
To establish intent. If these licenses have to be tested in court, then if
|
||||
my intent is clear, that can help judges and juries resolve ambiguities and
|
||||
decide if a license violation happened.
|
||||
|
||||
The [GPL][faq-gpl] and [AGPL][faq-agpl] did the same thing. However, in
|
||||
those cases, the licenses include the intent in the preambles to the
|
||||
licenses, which muddies the waters. The reason for this is because if the
|
||||
preamble conflicts with another part of the license, which part wins?
|
||||
|
||||
To stop that from happening, I set forth my intent in this FAQ, but I also
|
||||
explicitly made it a separate document (in the repository). That way, if the
|
||||
FAQ conflicts with the license, the license wins hands down.
|
||||
|
||||
[faq-0]: https://yzena.com/yzena-copyleft-user-license/
|
||||
[faq-copyleft]: https://writing.kemitchell.com/2018/10/24/How-to-Speak-Copyleft.html
|
||||
[faq-viral]: https://en.wikipedia.org/wiki/Viral_license
|
||||
[faq-gpl]: https://www.gnu.org/licenses/gpl-3.0.html
|
||||
[faq-agpl]: https://www.gnu.org/licenses/agpl-3.0.html
|
||||
[faq-gavinhoward]: https://gavinhoward.com/
|
||||
[faq-yzena]: https://yzena.com/
|
||||
[faq-boml]: https://blueoakcouncil.org/license/1.0.0
|
||||
[faq-license_notices]: https://writing.kemitchell.com/2020/12/27/War-on-License-Notices.html
|
||||
[faq-chalkeaters]: https://writing.kemitchell.com/2021/01/31/Chalkeaters-License.html
|
||||
[faq-mit_deprecation]: https://writing.kemitchell.com/2019/03/09/Deprecation-Notice.html
|
||||
[faq-boml_faq]: https://blueoakcouncil.org/license-faq
|
||||
[faq-purpose]: ./YCUL.md#purpose
|
||||
[faq-source_code]: ./YCUL.md#source-code
|
||||
[faq-this_software]: ./YCUL.md#this-software
|
||||
[faq-combined_software]: ./YCUL.md#combined-software
|
||||
[faq-application]: ./YCUL.md#application
|
||||
[faq-compatibility]: ./YCUL.md#compatibility
|
||||
[faq-distribution]: ./YCUL.md#distribution
|
||||
[faq-notices]: ./YCUL.md#notices
|
||||
[faq-credits]: ./YCUL.md#credits
|
||||
[faq-trademarks]: ./YCUL.md#trademarks
|
||||
[faq-litigation]: ./YCUL.md#litigation
|
||||
[faq-excuse]: ./YCUL.md#excuse
|
||||
[faq-reliability]: ./YCUL.md#reliability
|
||||
[faq-markdown]: https://www.markdownguide.org/getting-started
|
||||
[faq-apache_license]: https://www.apache.org/licenses/LICENSE-2.0.html
|
||||
[faq-sunset]: https://github.com/copyleft-next/copyleft-next/blob/master/Releases/copyleft-next-0.3.1#L89-L93
|
||||
[faq-ctea]: https://en.wikipedia.org/wiki/Copyright_Term_Extension_Act
|
||||
[faq-nullification]: https://github.com/copyleft-next/copyleft-next/blob/master/Releases/copyleft-next-0.3.1#L81-L87
|
||||
[faq-copilot]: https://copilot.github.com/
|
||||
[faq-fair_use]: https://valohai.com/blog/copyright-laws-and-machine-learning/#fairusedoctrineintheus
|
||||
[faq-lto]: https://en.wikipedia.org/wiki/Interprocedural_optimization#WPO_and_LTO
|
||||
[faq-inlining]: https://en.wikipedia.org/wiki/Inline_expansion
|
||||
[faq-algorithm_transform]: https://cacm.acm.org/magazines/2020/2/242347-optimizations-in-c-compilers/fulltext#body-6
|
||||
[faq-four_freedoms]: https://www.gnu.org/philosophy/free-sw.en.html
|
||||
[faq-hash_functions]: https://en.wikipedia.org/wiki/Hash_function
|
||||
[faq-static_analysis]: https://en.wikipedia.org/wiki/Static_program_analysis
|
||||
@ -0,0 +1,132 @@
|
||||
# Yzena Copyleft User License Frequently Asked Questions
|
||||
|
||||
1. **What is the [Yzena Copyleft User License (YCUL)][faq-0]?**
|
||||
|
||||
It is a permissive [copyleft][faq-copyleft] license that prohibits
|
||||
Tivoization and weaponizing software against users.
|
||||
|
||||
2.{{ viral }}
|
||||
|
||||
3.{{ who }}
|
||||
|
||||
4.{{ boml }}
|
||||
|
||||
5.{{ boml_changes }}
|
||||
|
||||
* Added to the [Purpose][faq-purpose] section about publishing changes.
|
||||
{{ boml_change_source_code }}
|
||||
{{ boml_change_this_software }}
|
||||
{{ boml_change_combined_software }}
|
||||
{{ boml_change_application }}
|
||||
{{ boml_change_user_agency }}
|
||||
{{ boml_change_compatibility }}
|
||||
{{ boml_change_distribution }}
|
||||
{{ boml_change_notices }}
|
||||
{{ boml_change_credits }}
|
||||
{{ boml_change_trademarks }}
|
||||
{{ boml_change_litigation }}
|
||||
{{ boml_change_non-interference }}
|
||||
{{ boml_change_respecting_user_choice }}
|
||||
{{ boml_change_excuse }}
|
||||
{{ boml_change_references }}
|
||||
{{ boml_change_reliability }}
|
||||
|
||||
6.{{ boml_use }}
|
||||
|
||||
In addition, this is also a [copyleft][faq-copyleft] license that requires
|
||||
respecting user agency, so if that's what you need, that is another reason
|
||||
the YCUL might work better for you. Again, be sure to consult with your
|
||||
lawyer first.
|
||||
|
||||
7.{{ vague }}
|
||||
|
||||
8.{{ credits }}
|
||||
|
||||
9.{{ link }}
|
||||
|
||||
10.{{ markdown }}
|
||||
|
||||
11.{{ verbatim }}
|
||||
|
||||
12.{{ contents }}
|
||||
|
||||
13.{{ relicense }}
|
||||
|
||||
14.{{ gpl }}
|
||||
|
||||
15.{{ patents }}
|
||||
|
||||
16.{{ sunset }}
|
||||
|
||||
17.{{ nullification }}
|
||||
|
||||
18.{{ this_software }}
|
||||
|
||||
19.{{ fair_use }}
|
||||
|
||||
20.{{ transformative }}
|
||||
|
||||
21.{{ future-proof }}
|
||||
|
||||
22.{{ incompatible }}
|
||||
|
||||
23.{{ open_source }}
|
||||
|
||||
24.{{ better_foss }}
|
||||
|
||||
25.{{ viral2 }}
|
||||
|
||||
26.{{ this_software2 }}
|
||||
|
||||
27.{{ recursive }}
|
||||
|
||||
28.{{ source_code }}
|
||||
|
||||
29.{{ user_agency }}
|
||||
|
||||
30.{{ user_agency_vague }}
|
||||
|
||||
31.{{ user_agency_consequences }}
|
||||
|
||||
32.{{ user_agency_illegal }}
|
||||
|
||||
33.{{ intent }}
|
||||
|
||||
[faq-0]: https://yzena.com/yzena-copyleft-user-license/
|
||||
{{ ref-copyleft }}
|
||||
{{ ref-viral }}
|
||||
{{ ref-gpl }}
|
||||
{{ ref-agpl }}
|
||||
{{ ref-gavinhoward }}
|
||||
{{ ref-yzena }}
|
||||
{{ ref-boml }}
|
||||
{{ ref-license_notices }}
|
||||
{{ ref-chalkeaters }}
|
||||
{{ ref-mit_deprecation }}
|
||||
{{ ref-boml_faq }}
|
||||
{{ ref-purpose }}
|
||||
{{ ref-source_code }}
|
||||
{{ ref-this_software }}
|
||||
{{ ref-combined_software }}
|
||||
{{ ref-application }}
|
||||
{{ ref-compatibility }}
|
||||
{{ ref-distribution }}
|
||||
{{ ref-notices }}
|
||||
{{ ref-credits }}
|
||||
{{ ref-trademarks }}
|
||||
{{ ref-litigation }}
|
||||
{{ ref-excuse }}
|
||||
{{ ref-reliability }}
|
||||
{{ ref-markdown }}
|
||||
{{ ref-apache_license }}
|
||||
{{ ref-sunset }}
|
||||
{{ ref-ctea }}
|
||||
{{ ref-nullification }}
|
||||
{{ ref-copilot }}
|
||||
{{ ref-fair_use }}
|
||||
{{ ref-lto }}
|
||||
{{ ref-inlining }}
|
||||
{{ ref-algorithm_transform }}
|
||||
{{ ref-four_freedoms }}
|
||||
{{ ref-hash_functions }}
|
||||
{{ ref-static_analysis }}
|
||||
@ -0,0 +1,148 @@
|
||||
# Yzena Copyleft User License
|
||||
|
||||
<https://yzena.com/yzena-copyleft-user-license>
|
||||
|
||||
Version 0.1
|
||||
|
||||
***This license is a draft. Do not use.***
|
||||
|
||||
## Purpose
|
||||
|
||||
This license gives users as much permission to work with this software as
|
||||
possible, while protecting contributors from liability and ensuring that anyone
|
||||
who distributes this software publishes their changes.
|
||||
|
||||
## Acceptance
|
||||
|
||||
In order to receive this license, you must agree to its rules. The rules of this
|
||||
license are both obligations under that agreement and conditions to your
|
||||
license. You must not do anything with this software that triggers a rule that
|
||||
you cannot or will not follow.
|
||||
|
||||
## Source Code
|
||||
|
||||
In this license, the phrase "source code" includes the original copyrighted
|
||||
material of any software.
|
||||
|
||||
## This Software
|
||||
|
||||
In this license, the phrase "this software" includes the source code licensed
|
||||
under this license. It also includes the output of any execution of any
|
||||
algorithm that uses all or part of this software as all or part of its input,
|
||||
but only if the output itself is software.
|
||||
|
||||
## Combined Software
|
||||
|
||||
In this license, the phrase "combined software" means this software alone. It
|
||||
also means any piece of software which results from combining this software with
|
||||
any part of any other software into one piece of software.
|
||||
|
||||
## Application
|
||||
|
||||
In this license, the term "application" means any system that uses any piece of
|
||||
combined software.
|
||||
|
||||
## User Agency
|
||||
|
||||
User agency is the concept that users must have the choice of what the software
|
||||
they use does for them, and that software must never disobey the user or obey
|
||||
any other entity in lieu of obeying the user.
|
||||
|
||||
## Copyright
|
||||
|
||||
Each contributor licenses you to do everything with this software that would
|
||||
otherwise infringe that contributor's copyright in it, except anything that
|
||||
would break any rule of this license.
|
||||
|
||||
## Compatibility
|
||||
|
||||
Unless any contributor says otherwise, this software can be relicensed under all
|
||||
later versions of this license, the [Yzena Network User License][0.1-ynul] 0.1
|
||||
or later, or the [Yzena Viral User License][0.1-yvul] 0.1 or later.
|
||||
|
||||
## Distribution
|
||||
|
||||
If you wish to distribute this software as part of any software, you must
|
||||
provide the source code on request and without cost, and you must do so under
|
||||
this license or any of the licenses under [Compatibility][0.1-compatibility].
|
||||
However, this rule need not apply to the rest of any software for which this
|
||||
software is only a part, including any parts of the software that this software
|
||||
needs.
|
||||
|
||||
## Notices
|
||||
|
||||
You must ensure that everyone who gets a copy of any part of this software from
|
||||
you also gets the text of this license.
|
||||
|
||||
## Credits
|
||||
|
||||
If the source code includes a file named `CREDITS.md` or `NOTICE.md`, then you
|
||||
must ensure that everyone who gets a copy of any part of this software from you,
|
||||
with or without changes, also gets the verbatim text of that file.
|
||||
|
||||
## Trademarks
|
||||
|
||||
This License does not grant you any rights to the names, trademarks, service
|
||||
marks, or logos of any contributors.
|
||||
|
||||
## Litigation
|
||||
|
||||
You cannot initiate any patent litigation claiming that this software infringes
|
||||
any patent, directly or indirectly.
|
||||
|
||||
## Non-Interference
|
||||
|
||||
You must allow, and make it possible, for anyone to modify this software and use
|
||||
the modified version, including modifying any product that this software is a
|
||||
part of. you may also not use this software as part of an application or product
|
||||
that would prevent anyone from modifying and using any other software.
|
||||
|
||||
## Respecting User Choice
|
||||
|
||||
You cannot use this software as part of, or in support of, any application or
|
||||
product that does not respect user agency and that does anything that does not
|
||||
directly accomplish a task that the end user directly requested the product or
|
||||
application to do. This software must not be used as part of, or in support of,
|
||||
any application or product that is not a faithful and obedient agent for the end
|
||||
user.
|
||||
|
||||
This section still applies if the law does not allow such applications or
|
||||
products to comply. In that case, this license prohibits the use of this
|
||||
software under such law.
|
||||
|
||||
## Excuse
|
||||
|
||||
If any contributor notifies you in writing that you have not complied with
|
||||
[Distribution][0.1-distribution], [Notices][0.1-notices],
|
||||
[Credits][0.1-credits], [Trademarks][0.1-trademarks],
|
||||
[Litigation][0.1-litigation], [Non-Interference][0.1-non-interference], and/or
|
||||
[Respecting User Choice][0.1-respecting_user_choice], you can keep your license
|
||||
by taking all practical steps to comply within 30 days after the notice. If you
|
||||
do not do so, your license ends immediately after the 30 days.
|
||||
|
||||
## Patent
|
||||
|
||||
Each contributor licenses you to do everything with this software that would
|
||||
otherwise infringe any patent claims they can license or become able to license.
|
||||
|
||||
## Reliability
|
||||
|
||||
No contributor can revoke this license from you unless you do not follow its
|
||||
rules.
|
||||
|
||||
## No Liability
|
||||
|
||||
***As far as the law allows, this software comes as is, without any warranty or
|
||||
condition, and no contributor will be liable to anyone for any damages related
|
||||
to this software or this license, under any kind of legal claim.***
|
||||
|
||||
[0.1-ynul]: https://yzena.com/yzena-network-user-license/
|
||||
[0.1-yvul]: https://yzena.com/yzena-viral-user-license/
|
||||
[0.1-compatibility]: #compatibility
|
||||
[0.1-distribution]: #distribution
|
||||
[0.1-notices]: #notices
|
||||
[0.1-credits]: #credits
|
||||
[0.1-trademarks]: #trademarks
|
||||
[0.1-litigation]: #litigation
|
||||
[0.1-non-interference]: #non-interference
|
||||
{{ ref-respecting_user_choice }}
|
||||
@ -0,0 +1,81 @@
|
||||
# Yzena Copyleft User License
|
||||
|
||||
<https://yzena.com/yzena-copyleft-user-license>
|
||||
|
||||
{{ version }}
|
||||
|
||||
{{ draft }}
|
||||
|
||||
## Purpose
|
||||
|
||||
This license gives users as much permission to work with this software as
|
||||
possible, while protecting contributors from liability and ensuring that anyone
|
||||
who distributes this software publishes their changes.
|
||||
|
||||
{{ acceptance }}
|
||||
|
||||
{{ source_code }}
|
||||
|
||||
{{ this_software }}
|
||||
|
||||
{{ combined_software }}
|
||||
|
||||
{{ application }}
|
||||
|
||||
{{ user_agency }}
|
||||
|
||||
{{ copyright }}
|
||||
|
||||
## Compatibility
|
||||
|
||||
Unless any contributor says otherwise, this software can be relicensed under all
|
||||
later versions of this license, the [Yzena Network User License][{v}-ynul] {v}
|
||||
or later, or the [Yzena Viral User License][{v}-yvul] {v} or later.
|
||||
|
||||
## Distribution
|
||||
|
||||
If you wish to distribute this software as part of any software, you must
|
||||
provide the source code on request and without cost, and you must do so under
|
||||
this license or any of the licenses under [Compatibility][{v}-compatibility].
|
||||
However, this rule need not apply to the rest of any software for which this
|
||||
software is only a part, including any parts of the software that this software
|
||||
needs.
|
||||
|
||||
{{ notices }}
|
||||
|
||||
{{ credits }}
|
||||
|
||||
{{ trademarks }}
|
||||
|
||||
{{ litigation }}
|
||||
|
||||
{{ non-interference }}
|
||||
|
||||
{{ respecting_user_choice }}
|
||||
|
||||
## Excuse
|
||||
|
||||
If any contributor notifies you in writing that you have not complied with
|
||||
[Distribution][{v}-distribution], [Notices][{v}-notices],
|
||||
[Credits][{v}-credits], [Trademarks][{v}-trademarks],
|
||||
[Litigation][{v}-litigation], [Non-Interference][{v}-non-interference], and/or
|
||||
[Respecting User Choice][{v}-respecting_user_choice], you can keep your license
|
||||
by taking all practical steps to comply within 30 days after the notice. If you
|
||||
do not do so, your license ends immediately after the 30 days.
|
||||
|
||||
{{ patent }}
|
||||
|
||||
{{ reliability }}
|
||||
|
||||
{{ no_liability }}
|
||||
|
||||
{{ ref-ynul }}
|
||||
{{ ref-yvul }}
|
||||
{{ ref-compatibility }}
|
||||
{{ ref-distribution }}
|
||||
{{ ref-notices }}
|
||||
{{ ref-credits }}
|
||||
{{ ref-trademarks }}
|
||||
{{ ref-litigation }}
|
||||
{{ ref-non-interference }}
|
||||
{{ ref-respecting_user_choice }}
|
||||
@ -0,0 +1,138 @@
|
||||
# Yzena Network User License Frequently Asked Questions
|
||||
|
||||
1. **What is the [Yzena Network User License (YNUL)][faq-0]?**
|
||||
|
||||
It is a permissive network [copyleft][faq-copyleft] license that prohibits
|
||||
Tivoization and weaponizing software against users.
|
||||
|
||||
2.{{ viral }}
|
||||
|
||||
3.{{ who }}
|
||||
|
||||
4.{{ boml }}
|
||||
|
||||
5.{{ boml_changes }}
|
||||
|
||||
* Added to the [Purpose][faq-purpose] section about publishing changes for
|
||||
any public use.
|
||||
{{ boml_change_source_code }}
|
||||
{{ boml_change_this_software }}
|
||||
{{ boml_change_combined_software }}
|
||||
{{ boml_change_application }}
|
||||
{{ boml_change_user_agency }}
|
||||
{{ boml_change_compatibility }}
|
||||
{{ boml_change_distribution }}
|
||||
{{ boml_change_notices }}
|
||||
{{ boml_change_credits }}
|
||||
{{ boml_change_trademarks }}
|
||||
{{ boml_change_litigation }}
|
||||
{{ boml_change_non-interference }}
|
||||
{{ boml_change_respecting_user_choice }}
|
||||
{{ boml_change_excuse }}
|
||||
{{ boml_change_references }}
|
||||
{{ boml_change_reliability }}
|
||||
|
||||
6.{{ boml_use }}
|
||||
|
||||
In addition, this is also a network [copyleft][faq-copyleft] license that
|
||||
requires respecting user agency, so if that's what you need, that is another
|
||||
reason the YNUL might work better for you. Again, be sure to consult with
|
||||
your lawyer first.
|
||||
|
||||
7.{{ vague }}
|
||||
|
||||
8.{{ credits }}
|
||||
|
||||
9.{{ link }}
|
||||
|
||||
10.{{ markdown }}
|
||||
|
||||
11.{{ verbatim }}
|
||||
|
||||
12.{{ contents }}
|
||||
|
||||
13.{{ relicense }}
|
||||
|
||||
14.{{ gpl }}
|
||||
|
||||
15.{{ patents }}
|
||||
|
||||
16.{{ sunset }}
|
||||
|
||||
17.{{ nullification }}
|
||||
|
||||
18.{{ public_use }}
|
||||
|
||||
19.{{ public_use_line }}
|
||||
|
||||
20.{{ this_software }}
|
||||
|
||||
21.{{ fair_use }}
|
||||
|
||||
22.{{ transformative }}
|
||||
|
||||
23.{{ future-proof }}
|
||||
|
||||
24.{{ incompatible }}
|
||||
|
||||
25.{{ open_source }}
|
||||
|
||||
26.{{ better_foss }}
|
||||
|
||||
27.{{ viral2 }}
|
||||
|
||||
28.{{ this_software2 }}
|
||||
|
||||
29.{{ recursive }}
|
||||
|
||||
30.{{ source_code }}
|
||||
|
||||
31.{{ user_agency }}
|
||||
|
||||
32.{{ user_agency_vague }}
|
||||
|
||||
33.{{ user_agency_consequences }}
|
||||
|
||||
34.{{ user_agency_illegal }}
|
||||
|
||||
35.{{ intent }}
|
||||
|
||||
[faq-0]: https://yzena.com/yzena-network-user-license/
|
||||
{{ ref-copyleft }}
|
||||
{{ ref-viral }}
|
||||
{{ ref-gpl }}
|
||||
{{ ref-agpl }}
|
||||
{{ ref-gavinhoward }}
|
||||
{{ ref-yzena }}
|
||||
{{ ref-boml }}
|
||||
{{ ref-license_notices }}
|
||||
{{ ref-chalkeaters }}
|
||||
{{ ref-mit_deprecation }}
|
||||
{{ ref-boml_faq }}
|
||||
{{ ref-purpose }}
|
||||
{{ ref-source_code }}
|
||||
{{ ref-this_software }}
|
||||
{{ ref-combined_software }}
|
||||
{{ ref-application }}
|
||||
{{ ref-compatibility }}
|
||||
{{ ref-distribution }}
|
||||
{{ ref-notices }}
|
||||
{{ ref-credits }}
|
||||
{{ ref-trademarks }}
|
||||
{{ ref-litigation }}
|
||||
{{ ref-excuse }}
|
||||
{{ ref-reliability }}
|
||||
{{ ref-markdown }}
|
||||
{{ ref-apache_license }}
|
||||
{{ ref-sunset }}
|
||||
{{ ref-ctea }}
|
||||
{{ ref-nullification }}
|
||||
{{ ref-copilot }}
|
||||
{{ ref-fair_use }}
|
||||
{{ ref-lto }}
|
||||
{{ ref-inlining }}
|
||||
{{ ref-algorithm_transform }}
|
||||
{{ ref-four_freedoms }}
|
||||
{{ ref-hash_functions }}
|
||||
{{ ref-static_analysis }}
|
||||
{{ ref-professionalism }}
|
||||
@ -0,0 +1,148 @@
|
||||
# Yzena Network User License
|
||||
|
||||
<https://yzena.com/yzena-network-user-license>
|
||||
|
||||
Version 0.1
|
||||
|
||||
***This license is a draft. Do not use.***
|
||||
|
||||
## Purpose
|
||||
|
||||
This license gives users as much permission to work with this software as
|
||||
possible, while protecting contributors from liability and ensuring that anyone
|
||||
who makes this software part of any software available for public use publishes
|
||||
their changes.
|
||||
|
||||
## Acceptance
|
||||
|
||||
In order to receive this license, you must agree to its rules. The rules of this
|
||||
license are both obligations under that agreement and conditions to your
|
||||
license. You must not do anything with this software that triggers a rule that
|
||||
you cannot or will not follow.
|
||||
|
||||
## Source Code
|
||||
|
||||
In this license, the phrase "source code" includes the original copyrighted
|
||||
material of any software.
|
||||
|
||||
## This Software
|
||||
|
||||
In this license, the phrase "this software" includes the source code licensed
|
||||
under this license. It also includes the output of any execution of any
|
||||
algorithm that uses all or part of this software as all or part of its input,
|
||||
but only if the output itself is software.
|
||||
|
||||
## Combined Software
|
||||
|
||||
In this license, the phrase "combined software" means this software alone. It
|
||||
also means any piece of software which results from combining this software with
|
||||
any part of any other software into one piece of software.
|
||||
|
||||
## Application
|
||||
|
||||
In this license, the term "application" means any system that uses any piece of
|
||||
combined software.
|
||||
|
||||
## User Agency
|
||||
|
||||
User agency is the concept that users must have the choice of what the software
|
||||
they use does for them, and that software must never disobey the user or obey
|
||||
any other entity in lieu of obeying the user.
|
||||
|
||||
## Copyright
|
||||
|
||||
Each contributor licenses you to do everything with this software that would
|
||||
otherwise infringe that contributor's copyright in it, except anything that
|
||||
would break any rule of this license.
|
||||
|
||||
## Compatibility
|
||||
|
||||
Unless any contributor says otherwise, this software can be relicensed under all
|
||||
later versions of this license or the [Yzena Viral User License][0.1-yvl] 0.1 or
|
||||
later.
|
||||
|
||||
## Distribution
|
||||
|
||||
If you wish to make any part of this software part of any software that is
|
||||
available for public use, and if you made any changes to the source code, you
|
||||
must provide the source code, and you must do so under this license or any of
|
||||
the licenses under [Compatibility][0.1-compatibility]. However, this rule need
|
||||
not apply to the rest of any software for which this software is only a part,
|
||||
including any parts of the software that this software needs.
|
||||
|
||||
## Notices
|
||||
|
||||
You must ensure that everyone who gets a copy of any part of this software from
|
||||
you also gets the text of this license.
|
||||
|
||||
## Credits
|
||||
|
||||
If the source code includes a file named `CREDITS.md` or `NOTICE.md`, then you
|
||||
must ensure that everyone who gets a copy of any part of this software from you,
|
||||
with or without changes, also gets the verbatim text of that file.
|
||||
|
||||
## Trademarks
|
||||
|
||||
This License does not grant you any rights to the names, trademarks, service
|
||||
marks, or logos of any contributors.
|
||||
|
||||
## Litigation
|
||||
|
||||
You cannot initiate any patent litigation claiming that this software infringes
|
||||
any patent, directly or indirectly.
|
||||
|
||||
## Non-Interference
|
||||
|
||||
You must allow, and make it possible, for anyone to modify this software and use
|
||||
the modified version, including modifying any product that this software is a
|
||||
part of. you may also not use this software as part of an application or product
|
||||
that would prevent anyone from modifying and using any other software.
|
||||
|
||||
## Respecting User Choice
|
||||
|
||||
You cannot use this software as part of, or in support of, any application or
|
||||
product that does not respect user agency and that does anything that does not
|
||||
directly accomplish a task that the end user directly requested the product or
|
||||
application to do. This software must not be used as part of, or in support of,
|
||||
any application or product that is not a faithful and obedient agent for the end
|
||||
user.
|
||||
|
||||
This section still applies if the law does not allow such applications or
|
||||
products to comply. In that case, this license prohibits the use of this
|
||||
software under such law.
|
||||
|
||||
## Excuse
|
||||
|
||||
If any contributor notifies you in writing that you have not complied with
|
||||
[Distribution][0.1-distribution], [Notices][0.1-notices],
|
||||
[Credits][0.1-credits], [Trademarks][0.1-trademarks],
|
||||
[Litigation][0.1-litigation], [Non-Interference][0.1-non-interference], and/or
|
||||
[Respecting User Choice][0.1-respecting_user_choice], you can keep your license
|
||||
by taking all practical steps to comply within 30 days after the notice. If you
|
||||
do not do so, your license ends immediately after the 30 days.
|
||||
|
||||
## Patent
|
||||
|
||||
Each contributor licenses you to do everything with this software that would
|
||||
otherwise infringe any patent claims they can license or become able to license.
|
||||
|
||||
## Reliability
|
||||
|
||||
No contributor can revoke this license from you unless you do not follow its
|
||||
rules.
|
||||
|
||||
## No Liability
|
||||
|
||||
***As far as the law allows, this software comes as is, without any warranty or
|
||||
condition, and no contributor will be liable to anyone for any damages related
|
||||
to this software or this license, under any kind of legal claim.***
|
||||
|
||||
[0.1-yvul]: https://yzena.com/yzena-viral-user-license/
|
||||
[0.1-compatibility]: #compatibility
|
||||
[0.1-distribution]: #distribution
|
||||
[0.1-notices]: #notices
|
||||
[0.1-credits]: #credits
|
||||
[0.1-trademarks]: #trademarks
|
||||
[0.1-litigation]: #litigation
|
||||
[0.1-non-interference]: #non-interference
|
||||
{{ ref-respecting_user_choice }}
|
||||
@ -0,0 +1,81 @@
|
||||
# Yzena Network User License
|
||||
|
||||
<https://yzena.com/yzena-network-user-license>
|
||||
|
||||
{{ version }}
|
||||
|
||||
{{ draft }}
|
||||
|
||||
## Purpose
|
||||
|
||||
This license gives users as much permission to work with this software as
|
||||
possible, while protecting contributors from liability and ensuring that anyone
|
||||
who makes this software part of any software available for public use publishes
|
||||
their changes.
|
||||
|
||||
{{ acceptance }}
|
||||
|
||||
{{ source_code }}
|
||||
|
||||
{{ this_software }}
|
||||
|
||||
{{ combined_software }}
|
||||
|
||||
{{ application }}
|
||||
|
||||
{{ user_agency }}
|
||||
|
||||
{{ copyright }}
|
||||
|
||||
## Compatibility
|
||||
|
||||
Unless any contributor says otherwise, this software can be relicensed under all
|
||||
later versions of this license or the [Yzena Viral User License][{v}-yvl] {v} or
|
||||
later.
|
||||
|
||||
## Distribution
|
||||
|
||||
If you wish to make any part of this software part of any software that is
|
||||
available for public use, and if you made any changes to the source code, you
|
||||
must provide the source code, and you must do so under this license or any of
|
||||
the licenses under [Compatibility][{v}-compatibility]. However, this rule need
|
||||
not apply to the rest of any software for which this software is only a part,
|
||||
including any parts of the software that this software needs.
|
||||
|
||||
{{ notices }}
|
||||
|
||||
{{ credits }}
|
||||
|
||||
{{ trademarks }}
|
||||
|
||||
{{ litigation }}
|
||||
|
||||
{{ non-interference }}
|
||||
|
||||
{{ respecting_user_choice }}
|
||||
|
||||
## Excuse
|
||||
|
||||
If any contributor notifies you in writing that you have not complied with
|
||||
[Distribution][{v}-distribution], [Notices][{v}-notices],
|
||||
[Credits][{v}-credits], [Trademarks][{v}-trademarks],
|
||||
[Litigation][{v}-litigation], [Non-Interference][{v}-non-interference], and/or
|
||||
[Respecting User Choice][{v}-respecting_user_choice], you can keep your license
|
||||
by taking all practical steps to comply within 30 days after the notice. If you
|
||||
do not do so, your license ends immediately after the 30 days.
|
||||
|
||||
{{ patent }}
|
||||
|
||||
{{ reliability }}
|
||||
|
||||
{{ no_liability }}
|
||||
|
||||
{{ ref-yvul }}
|
||||
{{ ref-compatibility }}
|
||||
{{ ref-distribution }}
|
||||
{{ ref-notices }}
|
||||
{{ ref-credits }}
|
||||
{{ ref-trademarks }}
|
||||
{{ ref-litigation }}
|
||||
{{ ref-non-interference }}
|
||||
{{ ref-respecting_user_choice }}
|
||||
@ -0,0 +1,430 @@
|
||||
# Yzena Viral User License Frequently Asked Questions
|
||||
|
||||
1. **What is the [Yzena Viral User License (YVUL)][faq-0]?**
|
||||
|
||||
It is a permissive, [viral][faq-viral] network [copyleft][faq-copyleft]
|
||||
license that prohibits Tivoization and weaponizing software against users.
|
||||
|
||||
2. **Is the YVUL [viral][faq-viral] like the [GNU GPL][faq-gpl] and [GNU
|
||||
AGPL][faq-agpl]?**
|
||||
|
||||
No, it's explicitly *not* viral. In my opinion, virality is parasitic and
|
||||
has caused people to use closed-source software instead of FOSS alternatives
|
||||
when those alternatives were licensed under the [GPL][faq-gpl] and
|
||||
[AGPL][faq-agpl].
|
||||
|
||||
3. **Who are you? And are you a lawyer?**
|
||||
|
||||
I am [Gavin D. Howard][faq-gavinhoward], founder of [Yzena][faq-yzena].
|
||||
|
||||
No, I am not a lawyer, but most of this license is taken from the [Blue Oak
|
||||
Model License 1.0.0][faq-boml] (BOML), which *was* written by lawyers.
|
||||
|
||||
4. **Why did you choose the [BOML][faq-boml] to start with?**
|
||||
|
||||
See [here][faq-license_notices], [here][faq-chalkeaters],
|
||||
[here][faq-mit_deprecation], and [here][faq-boml_faq]. Basically, the
|
||||
[BOML][faq-boml] is supposed to be a model for how licenses should be.
|
||||
|
||||
5. **What is the list of changes you made from the [BOML][faq-boml]?**
|
||||
|
||||
These are the changes I made:
|
||||
|
||||
* Added to the [Purpose][faq-purpose] section about publishing changes for
|
||||
any public use.
|
||||
* Added the [Source Code][faq-source_code] section.
|
||||
* Added the [This Software][faq-this_software] section.
|
||||
* Added the [Combined Software][faq-combined_software] section.
|
||||
* Added the [Application][faq-application] section.
|
||||
* Added the [User Agency][faq-user-agency] section.
|
||||
* Added the [Compatibility][faq-compatibility] section.
|
||||
* Added the [Distribution][faq-distribution] section.
|
||||
* Made it a requirement to give users the full license in the
|
||||
[Notices][faq-notices] section.
|
||||
* Added the [Credits][faq-credits] section.
|
||||
* Added the [Trademarks][faq-trademarks] section.
|
||||
* Added the [Litigation][faq-litigation] section.
|
||||
* Added the [Non-Interference][faq-non-interference] section.
|
||||
* Added the [Respecting User Choice][faq-respecting_user_choice] section.
|
||||
* Changed the [Excuse][faq-excuse] section such that any *contributor* has
|
||||
to give notice of non-compliance, instead of *anyone*.
|
||||
* Added references to the [Distribution][faq-distribution],
|
||||
[Credits][faq-credits], [Trademarks][faq-trademarks], and
|
||||
[Litigation][faq-litigation] sections in the [Excuse][faq-excuse] section.
|
||||
* Tweaked the [Reliability][faq-reliability] section.
|
||||
|
||||
6. **If you mostly copied the [BOML][faq-boml], why shouldn't I just use that
|
||||
one?**
|
||||
|
||||
You actually should; if all you need is a typical permissive license, then
|
||||
yes, you should use the [BOML][faq-boml].
|
||||
|
||||
However, there are three clauses in the YVUL that are not in the
|
||||
[BOML][faq-boml]:
|
||||
|
||||
* [Credits][faq-credits] for giving credit,
|
||||
* [Trademarks][faq-trademarks] for protecting trademarks,
|
||||
* [Litigation][faq-litigation] for prohibiting patent litigation.
|
||||
|
||||
If you need those three things in a license, then the YVUL might work for
|
||||
you. Be sure to consult with your lawyer first.
|
||||
|
||||
In addition, this is also a viral network [copyleft][faq-copyleft] license
|
||||
that requires respecting user agency, so if that's what you need, that is
|
||||
another reason the YVUL might work better for you. Again, be sure to consult
|
||||
with your lawyer first.
|
||||
|
||||
In addition, this is also a [viral][faq-viral] network
|
||||
[copyleft][faq-copyleft] license that prohibits Tivoization and using
|
||||
software under this license to do anything that does not serve end users, so
|
||||
if that's what you need, that is another reason the YNUL might work better
|
||||
for you. Again, be sure to consult with your lawyer first.
|
||||
|
||||
7. **Why do you use such vague language and don't define some of your terms?**
|
||||
|
||||
Because the [BOML][faq-boml] doesn't. See more [here][faq-license_notices]
|
||||
and [here][faq-chalkeaters]. I decided that if lawyers did it, it should be
|
||||
fine.
|
||||
|
||||
8. **Your [Credits][faq-credits] section doesn't actually require giving
|
||||
credit.**
|
||||
|
||||
No, it doesn't. But it does require providing the verbatim text of the
|
||||
`CREDITS.md` or `NOTICE.md` file, and I assumed that the contributors would
|
||||
add whatever credits they wanted in there.
|
||||
|
||||
9. **You also don't require giving a link to the original project, if someone
|
||||
makes changes and relicenses the code.**
|
||||
|
||||
No, but I also assumed that the original contributors would put that
|
||||
information in the `CREDITS.md` or `NOTICE.md`, and that text must be
|
||||
provided verbatim.
|
||||
|
||||
That assumption simplified the license, which makes things easier on
|
||||
contributors *and* users.
|
||||
|
||||
10. **Why does the [Credits][faq-credits] section require that the file be in
|
||||
the [Markdown][faq-markdown] format?**
|
||||
|
||||
It made it easier to write the license and will make it easier to comply
|
||||
with the license.
|
||||
|
||||
More concretely, the [Apache 2.0 License][faq-apache_license] uses the
|
||||
phrase "NOTICE file." I decided to avoid that awkward language.
|
||||
|
||||
And while I could have chosen any file format, [Markdown][faq-markdown] is
|
||||
text, easily readable, well-supported (with ways to convert it), and should
|
||||
have all of the features that would be needed for such a file.
|
||||
|
||||
11. **The [Credits][faq-credits] section says that it is required to provide the
|
||||
verbatim text of the `CREDITS.md` or `NOTICE.md` file. Why didn't you just
|
||||
require people to provide the file?**
|
||||
|
||||
Because if someone makes changes to the software, I wanted them to be able
|
||||
to add their own credits to the `CREDITS.md` or `NOTICE.md` file, which they
|
||||
can do by adding theirs at the bottom or the top of the original, since the
|
||||
verbatim text of the original will still be intact.
|
||||
|
||||
12. **What do you suggest putting in the `CREDITS.md` or `NOTICE.md` file?**
|
||||
|
||||
I suggest adding these things:
|
||||
|
||||
* The name of the original software.
|
||||
* The original copyrights on the software.
|
||||
* A link to the original code/repository.
|
||||
* A link to the [Yzena Viral User License][faq-0] to inform users that it is
|
||||
possible to get the original under this license if they wish.
|
||||
* The (preferred) names of all contributors that want credit.
|
||||
|
||||
I also suggest having a paragraph that says:
|
||||
|
||||
> All files in this repository are under the Yzena Viral User License, Version
|
||||
> 0.1, and all such files are considered part of the "source code" as
|
||||
> defined by that license.
|
||||
|
||||
In addition, if there are files in the repository that used to be under any
|
||||
licenses other than the YVUL, then I suggest listing all such files, along
|
||||
with their respective former licenses and copyrights, as required by their
|
||||
former licenses, but to also make clear that the files have been relicensed.
|
||||
|
||||
13. **The previous question implies that everything in a repository should be
|
||||
under the YVUL. What if there is code that is under other licenses?**
|
||||
|
||||
Such code should be relicensed, if possible. This is possible with
|
||||
permissive licenses.
|
||||
|
||||
If it is not possible, then such code should *not* be integrated into the
|
||||
repository.
|
||||
|
||||
14. **Does this mean that any code under the GPL family of licenses should not
|
||||
be integrated into a repository under the YVUL?**
|
||||
|
||||
Yes.
|
||||
|
||||
15. **Why do you care about patents and trademarks?**
|
||||
|
||||
Because I want to be able to make a business based on Open Source software,
|
||||
and I do not want to have to worry about losing trademarks or possibly
|
||||
getting sued for patent infringement.
|
||||
|
||||
Also, software patents are, in my opinion, illegal because you can't patent
|
||||
algorithms. They have also never been used for actual innovation, which
|
||||
makes them useless.
|
||||
|
||||
16. **Why did you not use a sunset clause, like [copyleft-next][faq-sunset]?
|
||||
That seems like a good idea.**
|
||||
|
||||
It *is* a good idea, since the term of copyright is [much longer than it
|
||||
should be][faq-ctea].
|
||||
|
||||
However, unlike movies or other works of art, software is constantly
|
||||
changing. So if there was such a sunset clause in YVUL, it might be ambiguous
|
||||
whether or not the clause applies to all of the software, or just those
|
||||
portions that have existed as long as the sunset term.
|
||||
|
||||
Instead, I opted to keep the [BOML][faq-boml]'s
|
||||
[Reliability][faq-reliability] clause, which should serve the same purpose.
|
||||
|
||||
17. **Why did you not use a nullification of copyright clause, like
|
||||
[copyleft-next][faq-nullification], to prevent proprietary dual licensing?**
|
||||
|
||||
While that clause is also a good idea, its purpose is also somewhat
|
||||
fulfilled by the [Reliability][faq-reliability] clause.
|
||||
|
||||
18. **Why did you use the vague phrase "make...this software...part of any
|
||||
application that is available for public use"?**
|
||||