aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorSilvio Rhatto <rhatto@riseup.net>2023-10-07 11:12:19 -0300
committerSilvio Rhatto <rhatto@riseup.net>2023-10-07 11:12:19 -0300
commitb5c5f1de95866baabad53ed10d13906b62747c70 (patch)
treed5189f46d45474aac73eb1d7e4e4f46e37f93be0 /docs
parentd66dced4e7fa79c1a1deff4e0fb442be5ee18329 (diff)
downloadcopyfarai-b5c5f1de95866baabad53ed10d13906b62747c70.tar.gz
copyfarai-b5c5f1de95866baabad53ed10d13906b62747c70.tar.bz2
Feat: add a page discussing the license's effectiveness
Diffstat (limited to 'docs')
-rw-r--r--docs/.pages1
-rw-r--r--docs/effectiveness/README.md19
-rw-r--r--docs/effectiveness/README.pt.md20
-rw-r--r--docs/how/README.md9
-rw-r--r--docs/how/README.pt.md10
-rw-r--r--docs/references/README.md3
-rw-r--r--docs/references/README.pt.md3
7 files changed, 44 insertions, 21 deletions
diff --git a/docs/.pages b/docs/.pages
index a9a6fb0..1ad1a91 100644
--- a/docs/.pages
+++ b/docs/.pages
@@ -2,6 +2,7 @@ nav:
- README.md
- README.pt.md
- why
+ - effectiveness
- how
- flavors
- versions
diff --git a/docs/effectiveness/README.md b/docs/effectiveness/README.md
new file mode 100644
index 0000000..5d0e709
--- /dev/null
+++ b/docs/effectiveness/README.md
@@ -0,0 +1,19 @@
+# Effectiveness
+
+## Validity
+
+In the legal stage, the validity of an "AI"-restrictive license may be settled
+on courts. Check the existing legislation each country for more information.
+
+From an ethical/moral/political standpoint, though, this license might be
+useful, regardless of the outcome for the "fair use" question or the license's
+validity in any jurisdiction.
+
+## Applicability
+
+It's a debate whether "Artificial Intelligence" operators respect such type of
+licensing, especially for closed algorithms and datasets, where audits looking
+for license violations are unfeasible.
+
+Even though, using a licensing system such as {{ config.site_name }} is a way
+to make an statement, expose the issue and make them accountable.
diff --git a/docs/effectiveness/README.pt.md b/docs/effectiveness/README.pt.md
new file mode 100644
index 0000000..13fafc4
--- /dev/null
+++ b/docs/effectiveness/README.pt.md
@@ -0,0 +1,20 @@
+# Efetividade
+
+## Validade
+
+No campo legal, a validade de uma licença restritiva às "IAs" pode ser decidida
+nos tribubais. Consulte a legislação de cada país para mais informações.
+
+De um ponto de vista ético/moral/político, no entando, esta licença pode ser
+útil, independente do de como a questão do "uso justo" for decidida nas cortes
+ou da validade da licença em quaisquer jurisdições.
+
+## Aplicabilidade
+
+É discutível o quanto operadores de "Inteligências Artificiais" respeitam
+este tipo de licenciamento, especialmente no caso de algoritmos e conjuntos
+de dados fechados, onde se torna inviável uma auditoria buscando violações
+de licenças.
+
+Ainda assim, usar um sistema de licenciamento do tipo {{ config.site_name }}
+é uma forma de marcar posição, expor o problema e responsabilizá-los.
diff --git a/docs/how/README.md b/docs/how/README.md
index 125ac14..64dde55 100644
--- a/docs/how/README.md
+++ b/docs/how/README.md
@@ -19,12 +19,3 @@
[here]: ../flavors/CC-BY-4.0-FAI.md
Some license "flavors" are ready to use, available at the "Flavors" menu item.
-
-## Effectiveness
-
-It's a debate whether "Artificial Intelligence" operators respect such type of
-licensing, especially for closed algorithms and datasets, where audits looking
-for license violations are unfeasible.
-
-Even though, using a licensing system such as {{ config.site_name }} is a way
-to make an statement, expose the issue and make them accountable.
diff --git a/docs/how/README.pt.md b/docs/how/README.pt.md
index 54ad561..6d2d9f1 100644
--- a/docs/how/README.pt.md
+++ b/docs/how/README.pt.md
@@ -22,13 +22,3 @@ para embalar outras licenças.
Alguns "sabores" de licenças já estão prontos para usar, acessíveis no item de
menu "Sabores".
-
-## Efetividade
-
-É discutível o quanto operadores de "Inteligências Artificiais" respeitam
-este tipo de licenciamento, especialmente no caso de algoritmos e conjuntos
-de dados fechados, onde se torna inviável uma auditoria buscando violações
-de licenças.
-
-Ainda assim, usar um sistema de licenciamento do tipo {{ config.site_name }}
-é uma forma de marcar posição, expor o problema e responsabilizá-los.
diff --git a/docs/references/README.md b/docs/references/README.md
index 46b84f8..1896d33 100644
--- a/docs/references/README.md
+++ b/docs/references/README.md
@@ -4,10 +4,11 @@ Some related references and discussions.
## "AI" and licensing
+* [Artificial intelligence and copyright - Wikipedia](https://en.wikipedia.org/wiki/Artificial_intelligence_and_copyright)
* [GitHub - non-ai-licenses/non-ai-licenses: This repository contains software licenses that restrict software from being used in AI training datasets or AI technologies.](https://github.com/non-ai-licenses/non-ai-licenses)
* [Is there a license that explicitly exempts AI from all conditions? - Open Source Stack Exchange](https://opensource.stackexchange.com/questions/13932/is-there-a-license-that-explicitly-exempts-ai-from-all-conditions)
* [Is there a license like MIT that explicitly forbids the use of AI? - Open Source Stack Exchange](https://opensource.stackexchange.com/questions/13920/is-there-a-license-like-mit-that-explicitly-forbids-the-use-of-ai)
-* [First Open Source Copyright Lawsuit Chal­lenges GitHub Copi­lot](https://www.infoq.com/news/2022/11/lawsuit-github-copilot/)
+* [First Open Source Copyright Lawsuit Challenges GitHub Copilot](https://www.infoq.com/news/2022/11/lawsuit-github-copilot/)
* [relicensing - How can I protect the code from being 'rephrased' by AI to avoid license limitations? - Open Source Stack Exchange](https://opensource.stackexchange.com/questions/13860/how-can-i-protect-the-code-from-being-rephrased-by-ai-to-avoid-license-limitat/13878)
## "AI" and copyright violantions
diff --git a/docs/references/README.pt.md b/docs/references/README.pt.md
index 4dd8326..fb8202e 100644
--- a/docs/references/README.pt.md
+++ b/docs/references/README.pt.md
@@ -4,10 +4,11 @@ Alguns artigos e discussões sobre o assunto.
## "IA" e licenciamento
+* [Artificial intelligence and copyright - Wikipedia](https://en.wikipedia.org/wiki/Artificial_intelligence_and_copyright)
* [GitHub - non-ai-licenses/non-ai-licenses: This repository contains software licenses that restrict software from being used in AI training datasets or AI technologies.](https://github.com/non-ai-licenses/non-ai-licenses)
* [Is there a license that explicitly exempts AI from all conditions? - Open Source Stack Exchange](https://opensource.stackexchange.com/questions/13932/is-there-a-license-that-explicitly-exempts-ai-from-all-conditions)
* [Is there a license like MIT that explicitly forbids the use of AI? - Open Source Stack Exchange](https://opensource.stackexchange.com/questions/13920/is-there-a-license-like-mit-that-explicitly-forbids-the-use-of-ai)
-* [First Open Source Copyright Lawsuit Chal­lenges GitHub Copi­lot](https://www.infoq.com/news/2022/11/lawsuit-github-copilot/)
+* [First Open Source Copyright Lawsuit Challenges GitHub Copilot](https://www.infoq.com/news/2022/11/lawsuit-github-copilot/)
* [relicensing - How can I protect the code from being 'rephrased' by AI to avoid license limitations? - Open Source Stack Exchange](https://opensource.stackexchange.com/questions/13860/how-can-i-protect-the-code-from-being-rephrased-by-ai-to-avoid-license-limitat/13878)
## "IA" e violações de copyright