Change reuse-tool URLs to Codeberg (#5488)
All checks were successful
continuous-integration/drone/push Build is passing
All checks were successful
continuous-integration/drone/push Build is passing
Related to https://github.com/fsfe/reuse-tool/issues/865 DO NOT MERGE until the migration is done. I will ping in this PR. Reviewed-on: https://git.fsfe.org/FSFE/fsfe-website/pulls/5488 Reviewed-by: tobiasd <tobiasd@fsfe.org> Co-authored-by: Carmen Bianca BAKKER <carmenbianca@fsfe.org> Co-committed-by: Carmen Bianca BAKKER <carmenbianca@fsfe.org>
This commit was merged in pull request #5488.
This commit is contained in:
@@ -78,7 +78,7 @@
|
||||
</figure>
|
||||
<p class="question"><strong>In which steps and with which tools did you reach complete REUSE compliance in the KDE frameworks? </strong></p>
|
||||
|
||||
<div class="answer"><p>The main tool we use for our conversion is <a href="https://invent.kde.org/sdk/licensedigger">licensedigger</a>. This is a self-crafted tool that I started with the only purpose of converting traditional license headers, with all their quirks and funny different statements, to well-formed REUSE compatible license headers. It also assists with the initial conversion of a code repository by adding the required license text files and reporting an overview of the used licenses. For the conversion we use a dedicated tool because we wanted to enforce a very strict license detection mechanism, and it allows to focus on reviewing the reference license texts that are added to the tool instead of reviewing every single license header when it gets replaced. As soon as a repository is converted to being REUSE compatible, we switch to use <a href="https://github.com/fsfe/reuse-tool">the REUSE tool</a> to do quality assurance.</p>
|
||||
<div class="answer"><p>The main tool we use for our conversion is <a href="https://invent.kde.org/sdk/licensedigger">licensedigger</a>. This is a self-crafted tool that I started with the only purpose of converting traditional license headers, with all their quirks and funny different statements, to well-formed REUSE compatible license headers. It also assists with the initial conversion of a code repository by adding the required license text files and reporting an overview of the used licenses. For the conversion we use a dedicated tool because we wanted to enforce a very strict license detection mechanism, and it allows to focus on reviewing the reference license texts that are added to the tool instead of reviewing every single license header when it gets replaced. As soon as a repository is converted to being REUSE compatible, we switch to use <a href="https://codeberg.org/fsfe/reuse-tool">the REUSE tool</a> to do quality assurance.</p>
|
||||
|
||||
<p>Another, still emerging tool, is a CMake build system plugin I created to instrument the REUSE tool together with the build system information, in particular which source file is compiled into which artifact. This allows to generate license consistency checks as simple unit tests, which warn the developer if accidentally incompatible licenses are combined.</p></div>
|
||||
|
||||
|
||||
@@ -74,7 +74,7 @@
|
||||
</figure>
|
||||
<p class="question"><strong>Con quali passaggi e con quali strumenti siete riusciti a raggiungere una completa conformità a REUSE nei framework KDE? </strong></p>
|
||||
|
||||
<div class="answer"><p>Lo strumenti principale che abbiamo utilizzato per la conversione è <a href="https://invent.kde.org/sdk/licensedigger">licensedigger</a>. È un strumento che abbiamo sviluppato internamente con il solo scopo di convertire le intestazioni tradizionali delle licenze - con tutte le loro bizzarre e fantasiose diverse dichiarazioni - alle ben strutturate intestazioni di licenza compatibili con REUSE. È anche servito per la conversione iniziale del repository del codice, nel quale è stato necessario aggiungere i file di testo delle licenze e fare un resoconto delle licenze utilizzate. Per la conversione abbiamo utilizzato uno strumento dedicato perché abbiamo voluto imporre un meccanismo di rilevamento della licenza molto stringente, e questo ci ha permesso di focalizzarci nell'analisi dei testi di licenza aggiunti dello strumento anziché verificare ogni singola intestazione di licenza che veniva sostituita. Appena tutto il repository è stato convertito per essere conforme a REUSE, siamo passati al <a href="https://github.com/fsfe/reuse-tool">REUSE tool</a> per assicurarci una conformità di qualità.</p>
|
||||
<div class="answer"><p>Lo strumenti principale che abbiamo utilizzato per la conversione è <a href="https://invent.kde.org/sdk/licensedigger">licensedigger</a>. È un strumento che abbiamo sviluppato internamente con il solo scopo di convertire le intestazioni tradizionali delle licenze - con tutte le loro bizzarre e fantasiose diverse dichiarazioni - alle ben strutturate intestazioni di licenza compatibili con REUSE. È anche servito per la conversione iniziale del repository del codice, nel quale è stato necessario aggiungere i file di testo delle licenze e fare un resoconto delle licenze utilizzate. Per la conversione abbiamo utilizzato uno strumento dedicato perché abbiamo voluto imporre un meccanismo di rilevamento della licenza molto stringente, e questo ci ha permesso di focalizzarci nell'analisi dei testi di licenza aggiunti dello strumento anziché verificare ogni singola intestazione di licenza che veniva sostituita. Appena tutto il repository è stato convertito per essere conforme a REUSE, siamo passati al <a href="https://codeberg.org/fsfe/reuse-tool">REUSE tool</a> per assicurarci una conformità di qualità.</p>
|
||||
|
||||
<p>Un altro strumento, ancora in sviluppo, è un plugin del sistema CMake che ho creato per far lavorare il REUSE tool insieme alle informazioni del sistema di compilazione, in particolare quale file sorgente è compilato per quale libreria o programma. Questo permette di creare i controlli di consistenza delle licenze come semplici unità di test, che allertano lo sviluppatore se vengono accidentalmente combinate licenze incompatibili.</p></div>
|
||||
|
||||
|
||||
@@ -73,7 +73,7 @@
|
||||
</figure>
|
||||
<p class="question"><strong>Met welke stappen en gereedschappen bereikte u complete REUSE-naleving in de KDE-raamwerken? </strong></p>
|
||||
|
||||
<div class="answer"><p>Het belangrijkste gereedschap dat we voor onze conversie gebruiken is <a href="https://invent.kde.org/sdk/licensedigger">licensedigger</a>. Dit is een zelfgemaakt gereedschap waarmee ik ben begonnen om slechts traditionele licentie-headers, met al hun eigenaardigheden en grappige verschillende verklaringen, te converteren naar goed opgestelde REUSE-compatibele licentie-headers. Het helpt ook bij de initiële conversie van een code-pakketbron bij het willen afdwingen van een erg strikt licentiedetectiemechanisme en het maakt mogelijk om de aandacht te richten op het beoordelen van referentie-licentieteksten die door het gereedschap zijn toegevoegd in plaats van het beoordelen van iedere afzonderlijke licentie-header wanneer die wordt vervangen. Zodra een pakketbron wordt geconverteerd naar REUSE-compatibiliteit stappen we voor kwaliteitscontrole over op <a href="https://github.com/fsfe/reuse-tool">het REUSE-gereedschap</a>.</p>
|
||||
<div class="answer"><p>Het belangrijkste gereedschap dat we voor onze conversie gebruiken is <a href="https://invent.kde.org/sdk/licensedigger">licensedigger</a>. Dit is een zelfgemaakt gereedschap waarmee ik ben begonnen om slechts traditionele licentie-headers, met al hun eigenaardigheden en grappige verschillende verklaringen, te converteren naar goed opgestelde REUSE-compatibele licentie-headers. Het helpt ook bij de initiële conversie van een code-pakketbron bij het willen afdwingen van een erg strikt licentiedetectiemechanisme en het maakt mogelijk om de aandacht te richten op het beoordelen van referentie-licentieteksten die door het gereedschap zijn toegevoegd in plaats van het beoordelen van iedere afzonderlijke licentie-header wanneer die wordt vervangen. Zodra een pakketbron wordt geconverteerd naar REUSE-compatibiliteit stappen we voor kwaliteitscontrole over op <a href="https://codeberg.org/fsfe/reuse-tool">het REUSE-gereedschap</a>.</p>
|
||||
|
||||
<p>Een ander gereedschap, nog in opkomst, is een 'CMake build system plugin' die ik creëerde om het REUSE-gereedschap samen met de bouvsysteeminformatie voor te bereiden, in het bijzonder voor het bepalen van welk bronbestand gecompileerd is in welk historisch document. Dit stelt in staat om licentieconsistentiecontroles zo eenvoudig als enkelvoudige testen te genereren, die de ontwikkelaar waarschuwen als per ongeluk incompatibele licenties worden gecombineerd.</p></div>
|
||||
|
||||
|
||||
@@ -66,7 +66,7 @@
|
||||
<h2 id="what-have-we-done-inside-and-outside-the-fsfe">What have we done? Inside and outside the FSFE</h2>
|
||||
|
||||
<ul>
|
||||
<li>Our REUSE campaign is taking off. Some weeks ago KDE adopted the REUSE guidelines and <a href="https://github.com/fsfe/reuse-tool#user-content-example-demo">a new screencast has been produced</a> to show how to make a repository REUSE compliant. Also the German Corona Warn App's iOS version <a href="https://github.com/corona-warn-app/cwa-app-ios">is REUSE compliant now</a> and we helped almost a hundred projects so far that are supported by the FSFE's help in <a href="/news/2019/news-20191022-01.html#ngi0">the NGI0 project</a> to do likewise.</li>
|
||||
<li>Our REUSE campaign is taking off. Some weeks ago KDE adopted the REUSE guidelines and <a href="https://codeberg.org/fsfe/reuse-tool#example-demo">a new screencast has been produced</a> to show how to make a repository REUSE compliant. Also the German Corona Warn App's iOS version <a href="https://github.com/corona-warn-app/cwa-app-ios">is REUSE compliant now</a> and we helped almost a hundred projects so far that are supported by the FSFE's help in <a href="/news/2019/news-20191022-01.html#ngi0">the NGI0 project</a> to do likewise.</li>
|
||||
<figure>
|
||||
<a href="https://download.fsfe.org/videos/reuse/screencasts/reuse-tool.gif"><img src="https://download.fsfe.org/videos/reuse/screencasts/reuse-tool.gif" alt=""/></a>
|
||||
</figure>
|
||||
|
||||
@@ -80,7 +80,7 @@ material informativo, nuestras redes, o incluso financieramente. Participar es t
|
||||
|
||||
<p>
|
||||
Nuestra campaña REUSE está despegando. Hace algunas semanas KDE
|
||||
adoptó las directrices REUSE y <a href="https://github.com/fsfe/reuse-tool#user-content-example-demo">se ha producido una nueva screencast</a>
|
||||
adoptó las directrices REUSE y <a href="https://codeberg.org/fsfe/reuse-tool#example-demo">se ha producido una nueva screencast</a>
|
||||
|
||||
|
||||
para enseñar cómo se hace para que un repositorio cumpla con REUSE. También es compatible. Además, la versión alemana de la app de aviso de coronavirus para iOS <a href="https://github.com/corona-warn-app/cwa-app-ios">es conforme a REUSE desde ahora</a> y ayudamos a casi cien proyectos hasta ahora que son respaldados por la ayuda de la FSFE en <a href="/news/2019/news-20191022-01.html#ngi0">el proyecto NGI0</a> para hacerlo de esta manera.</p></li>
|
||||
|
||||
@@ -66,7 +66,7 @@
|
||||
<h2 id="what-have-we-done-inside-and-outside-the-fsfe">Qu'avons-nous fait ? En interne et en dehors de la FSFE</h2>
|
||||
|
||||
<ul>
|
||||
<li>Notre campagne REUSE décolle. Il y a quelques semaines, KDE a adopté les lignes de REUSE et <a href="https://github.com/fsfe/reuse-tool#user-content-example-demo">un nouveau screencast a été produit</a> pour montrer comment rendre un dépôt conforme à REUSE. De plus, la version iOS de l'application Corona Warn App Allemande <a href="https://github.com/corona-warn-app/cwa-app-ios">est maintenant conforme aux spécifications de REUSE</a> et près de cent projets ont reçu l'aide du <a href="/news/2019/news-20191022-01.html#ngi0">projet NGI0</a> de la FSFE pour en faire autant.</li>
|
||||
<li>Notre campagne REUSE décolle. Il y a quelques semaines, KDE a adopté les lignes de REUSE et <a href="https://codeberg.org/fsfe/reuse-tool#example-demo">un nouveau screencast a été produit</a> pour montrer comment rendre un dépôt conforme à REUSE. De plus, la version iOS de l'application Corona Warn App Allemande <a href="https://github.com/corona-warn-app/cwa-app-ios">est maintenant conforme aux spécifications de REUSE</a> et près de cent projets ont reçu l'aide du <a href="/news/2019/news-20191022-01.html#ngi0">projet NGI0</a> de la FSFE pour en faire autant.</li>
|
||||
<figure>
|
||||
<a href="https://download.fsfe.org/videos/reuse/screencasts/reuse-tool.gif"><img src="https://download.fsfe.org/videos/reuse/screencasts/reuse-tool.gif" alt=""/></a>
|
||||
</figure>
|
||||
|
||||
@@ -67,7 +67,7 @@
|
||||
<h2 id="what-have-we-done-inside-and-outside-the-fsfe">Cosa abbiamo fatto? Dentro e fuori la FSFE</h2>
|
||||
|
||||
<ul>
|
||||
<li><div>La nostra campagna REUSE sta decollando. Alcune settimane fa KDE ha adottato le linee guida REUSE ed <a href="https://github.com/fsfe/reuse-tool#user-content-example-demo">è stato prodotto un nuovo screencast</a> per mostrare come rendere conforme a REUSE un repository. Anche l'app di tracciamento del Coronavirus tedesca per iOS <a href="https://github.com/corona-warn-app/cwa-app-ios">è diventata conforme a REUSE</a> e abbiamo aiutato ad oggi quasi un centinaio di progetti che la FSFE supporta nel <a href="/news/2019/news-20191022-01.html#ngi0">progetto NGI0</a> a fare altrettanto.</div></li>
|
||||
<li><div>La nostra campagna REUSE sta decollando. Alcune settimane fa KDE ha adottato le linee guida REUSE ed <a href="https://codeberg.org/fsfe/reuse-tool#example-demo">è stato prodotto un nuovo screencast</a> per mostrare come rendere conforme a REUSE un repository. Anche l'app di tracciamento del Coronavirus tedesca per iOS <a href="https://github.com/corona-warn-app/cwa-app-ios">è diventata conforme a REUSE</a> e abbiamo aiutato ad oggi quasi un centinaio di progetti che la FSFE supporta nel <a href="/news/2019/news-20191022-01.html#ngi0">progetto NGI0</a> a fare altrettanto.</div></li>
|
||||
<figure>
|
||||
<a href="https://download.fsfe.org/videos/reuse/screencasts/reuse-tool.gif"><img src="https://download.fsfe.org/videos/reuse/screencasts/reuse-tool.gif" alt=""/></a>
|
||||
</figure>
|
||||
|
||||
@@ -66,7 +66,7 @@
|
||||
<h2 id="what-have-we-done-inside-and-outside-the-fsfe">Wat hebben we gedaan? Binnen en buiten de FSFE</h2>
|
||||
|
||||
<ul>
|
||||
<li>Onze REUSE-campagne slaat aan. Enkele weken geleden heeft KDE de REUSE-richtlijnen aangenomen en <a href="https://github.com/fsfe/reuse-tool#user-content-example-demo">er is een nieuwe screencast geproduceerd</a> om te laten zien hoe u voor een software-pakketbron de REUSE-richtlijnen kunt naleven. Ook is de iOS-versie van de Duitse Corona Waarschuwings-app <a href="https://github.com/corona-warn-app/cwa-app-ios">nu in overeenstemming met REUSE</a> en we hielpen tot nu toe bijna honderd projecten die worden gesteund door FSFE's hulp in <a href="/news/2019/news-20191022-01.html#ngi0">het NGI0-project</a> om hetzelfde te doen.</li>
|
||||
<li>Onze REUSE-campagne slaat aan. Enkele weken geleden heeft KDE de REUSE-richtlijnen aangenomen en <a href="https://codeberg.org/fsfe/reuse-tool#example-demo">er is een nieuwe screencast geproduceerd</a> om te laten zien hoe u voor een software-pakketbron de REUSE-richtlijnen kunt naleven. Ook is de iOS-versie van de Duitse Corona Waarschuwings-app <a href="https://github.com/corona-warn-app/cwa-app-ios">nu in overeenstemming met REUSE</a> en we hielpen tot nu toe bijna honderd projecten die worden gesteund door FSFE's hulp in <a href="/news/2019/news-20191022-01.html#ngi0">het NGI0-project</a> om hetzelfde te doen.</li>
|
||||
<figure>
|
||||
<a href="https://download.fsfe.org/videos/reuse/screencasts/reuse-tool.gif"><img src="https://download.fsfe.org/videos/reuse/screencasts/reuse-tool.gif" alt=""/></a>
|
||||
</figure>
|
||||
|
||||
@@ -74,7 +74,7 @@ upcoming European Elections next week. </p>
|
||||
<p>The REUSE tool v3.1.0a1 has just been released! This is an alpha
|
||||
release that includes the new REUSE.toml functionality that replaces
|
||||
.reuse/dep5 (which is being soft-deprecated). The main purpose of
|
||||
REUSE.toml is to resolve .reuse/dep5 scenarios as described in <a href="https://github.com/fsfe/reuse-tool/issues/779">https://github.com/fsfe/reuse-tool/issues/779</a>:
|
||||
REUSE.toml is to resolve .reuse/dep5 scenarios as described in <a href="https://codeberg.org/fsfe/reuse-tool/issues/779">https://codeberg.org/fsfe/reuse-tool/issues/779</a>:
|
||||
if a file has a header
|
||||
and is also covered by .reuse/dep5, and the two sources of information
|
||||
disagree about the licence, which licence applies?</p>
|
||||
|
||||
@@ -78,7 +78,7 @@ recta final de las inminentes elecciones europeas de la próxima semana.
|
||||
edición alfa que incluye la nueva funcionalidad REUSE.toml que
|
||||
reemplaza .reuse/dep5 (que está desactualizada). La principal
|
||||
función de REUSE.toml es resolver los escenarios de .reuse/dep5 como se
|
||||
describe en <a href="https://github.com/fsfe/reuse-tool/issues/779">https://github.com/fsfe/reuse-tool/issues/779</a>:
|
||||
describe en <a href="https://codeberg.org/fsfe/reuse-tool/issues/779">https://codeberg.org/fsfe/reuse-tool/issues/779</a>:
|
||||
si un archivo tiene una cabecera y está además cubierta por .reuse/dep5,
|
||||
y las dos fuentes de información no se ponen de acuerdo sobre la
|
||||
licencia, ¿qué licencia le corresponde?</p>
|
||||
|
||||
@@ -77,7 +77,7 @@ fine settimana.</p>
|
||||
tratta di una versione alfa che include la nuova funzionalità REUSE.toml
|
||||
che rimpiazza
|
||||
.reuse/dep5 (che è stato dichiarato deprecato). Lo scopo principale di
|
||||
REUSE.toml è di risolvere gli scenari .reuse/dep5 come descritto in <a href="https://github.com/fsfe/reuse-tool/issues/779">https://github.com/fsfe/reuse-tool/issues/779</a>:
|
||||
REUSE.toml è di risolvere gli scenari .reuse/dep5 come descritto in <a href="https://codeberg.org/fsfe/reuse-tool/issues/779">https://codeberg.org/fsfe/reuse-tool/issues/779</a>:
|
||||
se un file ha un'intestazione che è anche riportata in .reuse/dep5, e
|
||||
l'informazione sulla licenza delle due sorgenti non combacia, quale
|
||||
licenza si applica?</p>
|
||||
|
||||
@@ -76,7 +76,7 @@ de komende verkiezingen voor het Europese Parlement.</p>
|
||||
een alfa-publicatie die de nieuwe REUSE.toml-functionaliteit bevat, die
|
||||
.reuse/dep5 vervangt (en zacht wordt afgeschreven). Het belangrijkste
|
||||
doel van REUSE.toml is om .reuse/dep5-scenario's op te lossen, zoals
|
||||
beschreven in <a href="https://github.com/fsfe/reuse-tool/issues/779">https://github.com/fsfe/reuse-tool/issues/779</a>:
|
||||
beschreven in <a href="https://codeberg.org/fsfe/reuse-tool/issues/779">https://codeberg.org/fsfe/reuse-tool/issues/779</a>:
|
||||
als een bestand een header heeft, ook aan bod komt in .reuse/dep5 en de
|
||||
twee informatie-bronnen zijn het niet eens over de licentie, welke
|
||||
licentie is dan van toepassing?</p>
|
||||
|
||||
@@ -24,7 +24,7 @@ In the monthly Software Freedom Podcast we talk with people who have inspiring i
|
||||
<ul>
|
||||
<li><a href="https://reuse.software/">REUSE</a></li>
|
||||
<li><a href="https://git.fsfe.org/reuse/">REUSE Git repositories</a></li>
|
||||
<li><a href="https://github.com/fsfe/reuse-tool">REUSE-tool</a></li>
|
||||
<li><a href="https://codeberg.org/fsfe/reuse-tool">REUSE-tool</a></li>
|
||||
<li><a href="/freesoftware/basics/4freedoms.html">The four freedoms of Free Software</a></li>
|
||||
<li><a href="/freesoftware/freesoftware">What is Free Software?</a></li>
|
||||
</ul>
|
||||
|
||||
@@ -21,7 +21,7 @@
|
||||
<ul>
|
||||
<li><a href="https://reuse.software/">REUSE</a></li>
|
||||
<li><a href="https://git.fsfe.org/reuse/">Git repository di REUSE<br/></a></li>
|
||||
<li><a href="https://github.com/fsfe/reuse-tool">REUSE-tool</a></li>
|
||||
<li><a href="https://codeberg.org/fsfe/reuse-tool">REUSE-tool</a></li>
|
||||
<li><a href="/freesoftware/basics/4freedoms.html">Le quattro libertà del Software Libero</a></li>
|
||||
<li><a href="/freesoftware/freesoftware">Cos'è il Software Libero?</a></li>
|
||||
</ul>
|
||||
|
||||
@@ -24,7 +24,7 @@
|
||||
<ul>
|
||||
<li><a href="https://reuse.software/">REUSE</a></li>
|
||||
<li><a href="https://git.fsfe.org/reuse/">REUSE Git pakketbronnen</a></li>
|
||||
<li><a href="https://github.com/fsfe/reuse-tool">REUSE-gereedschap</a></li>
|
||||
<li><a href="https://codeberg.org/fsfe/reuse-tool">REUSE-gereedschap</a></li>
|
||||
<li><a href="/freesoftware/basics/4freedoms.html">De vier vrijheden van Vrije Software</a></li>
|
||||
<li><a href="/freesoftware/freesoftware">Wat is Vrije Software?</a></li>
|
||||
</ul>
|
||||
|
||||
@@ -24,7 +24,7 @@
|
||||
<li><a href="https://reuse.software/">REUSE</a></li>
|
||||
<li><a href="https://git.fsfe.org/reuse/">REUSE Git
|
||||
repositories</a></li>
|
||||
<li><a href="https://github.com/fsfe/reuse-tool">REUSE helper tool</a></li>
|
||||
<li><a href="https://codeberg.org/fsfe/reuse-tool">REUSE helper tool</a></li>
|
||||
<li><a href="/activities/ln/">The Legal Network</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@
|
||||
<li><a href="https://www.gnu.org/licenses/gpl-violation.html">Violazioni delle licenze GNU</a></li>
|
||||
<li><a href="https://reuse.software/">REUSE</a></li>
|
||||
<li><a href="https://git.fsfe.org/reuse/">Git repository di REUSE</a></li>
|
||||
<li><a href="https://github.com/fsfe/reuse-tool">Strumento per applicare REUSE</a></li>
|
||||
<li><a href="https://codeberg.org/fsfe/reuse-tool">Strumento per applicare REUSE</a></li>
|
||||
<li><a href="/activities/ln/">Il network legale</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@
|
||||
<li><a href="https://reuse.software/">REUSE</a></li>
|
||||
<li><a href="https://git.fsfe.org/reuse/">REUSE Git
|
||||
repositories</a></li>
|
||||
<li><a href="https://github.com/fsfe/reuse-tool">REUSE helper tool</a></li>
|
||||
<li><a href="https://codeberg.org/fsfe/reuse-tool">REUSE helper tool</a></li>
|
||||
<li><a href="/activities/ln/">Het juridische netwerk</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user