From 19c8e1355f508a993fd8dd8dff509b817e5a745c Mon Sep 17 00:00:00 2001 From: bill-auger Date: Thu, 7 Feb 2019 06:43:47 -0500 Subject: add BR ref to qt5-webengine entries --- README | 52 ++++++++++++++++++++++++++++++++-------------------- 1 file changed, 32 insertions(+), 20 deletions(-) (limited to 'README') diff --git a/README b/README index aa60b51..0a3a35e 100644 --- a/README +++ b/README @@ -10,31 +10,43 @@ your-freedom_emu-blacklist.txt or both if they endanger privacy or only exist for the sake of using nonfree software; respectively. see [3] and [4] for more info. -## Preferred method (blacklisting the package) - * if you don't have [5]git access: - * ask for it, or - * send a patch produced using `git format-patch` to dev@lists.parabola.nu - * if you do: - 1. if possible, start by making a [6]replacement available for all - the affected architectures (packages in - your-freedom_emu-blacklist.txt are not meant to have a - replacement), or [7]report a bug if the package could be - changed to be free (read next section) - 2. pull [8]blacklist.git - 3. add package according to the SYNTAX file - 4. push changes - 5. ssh into repo.parabola.nu and run db-check-nonfree - 6. pull [9]abslibre.git and make a new release of the - corresponding blacklist package (e.g. your-freedom) +## Reporting a freedom bug -## Alternative method (reporting an issue) + Every blacklisted package should have an associated bug report + for the purpose of documentation. This can be a bug report on the + debian, savannah, fedora, or parabola bug trackers, or en entry on the + libreplanet 'List_of_software_that_does_not_respect_the_FSDG" wiki page. + This should be referenced in the blacklist entry, as explained in the SYNTAX file, - * file a bug report on the [3]Parabola Issue Tracker + Ideally the bug report should detail the precise nature of the freedom issues, + the liberation procedure if one is known, or some alternate replacement, if any, + that can be used if there is no viable liberation procedure. + + If no such bug report yet exists: + + * file a bug report on the [7]Parabola Issue Tracker * choose the project responsible for it, nearly always "Packages" * choose the "Freedom issue" type and priority - * report separate issues for appropriate projects if the package is - included with installation media. + + +## Preferred method (blacklisting the package) + + 1. Start by trying to liberate the package in whatever way possible + in order to make it useful in freedom. If that is not possible or is + too much work or will be too high-maintenance relative to the program's + usefulness, try finding some alternate replacement program + that accomplishes the same task. If that turns out to be is similarly + unfruitful, simply continue blacklisting the package with no replacement. + (NOTE: your-freedom_emu-blacklist packages are not meant to have replacements) + 2. pull [8]blacklist.git + 3. add an entry for the package according to the SYNTAX file + 4. if you have [5]git write access, push changes + if not, send a patch produced using `git format-patch` to dev@lists.parabola.nu + 5. if you have shell access, ssh into repo.parabola.nu and run db-check-nonfree + 6. if you have shell access, pull [9]abslibre.git and make a new release of the + corresponding blacklist package (e.g. your-freedom) + ## References: -- cgit v1.2.2