Hi, On Thu, 3 Aug 2023 07:15:07 -0400 bill-auger <bill-auger@peers.community> wrote:
> == Commitment to Correct Mistakes == > > The FSDG work-group, with the oversight of the FSF, shall maintain a > list of software with known FSDG issues, and their commonly accepted > remedies. Distros shall, at all times, heed the current > recommendations on that list. In the case of contention, the issue > may be reintroduced into the work-group discussions, for the purpose > of re-assessment, and possibly a revision of the current > recommendation. Do you have something like that in mind for that list?: https://libreplanet.org/wiki/List_of_software_that_does_not_respect_the_Free_System_Distribution_Guidelines > Distros should refrain from introducing software into their > repositories, for which there are known contentions regarding it's > FSDG-fitness, until the issue is raised and thoroughly discussed > publicly among the work-group. Once the facts and arguments are > presented as clearly as possible, and people have had adequate time > in which to express their opinions, the FSF agent in charge of FSDG > over-sight may be consulted for an official recommendation. Do you have current examples or a current list of software like that? Do you have something like the list above in mind? > Pending an official recommendation, the standing consensus of the > work-group should be taken as the general recommendation, with > respect to that particular software; and each endorsed distro should > promptly apply that recommendation to their software. Once an > official recommendation is determined, it shall be added to the list > of common remedies for future reference. Here again if all that becomes mandatory, the issue is to find the resources to do all that. The FSF probably cannot make new money magically appear to hire more staff but I'll let the FSF comment on that. Distributions also don't participate, probably due to the lack of time. So if we want to go this route we would need to find ways to be more efficient in dealing with that to enable people to easily participate. We could have discussions in at least 2 phases with summary at the end of each phases to make sure that people can just read the summary and start participating if they need to. Given that with ScummVM, a lot more things were discussed along the way (and the discussion isn't even finished yet), I've tried again to update the List of software that does not respect the FSDG with way more simple cases to see if we can manage to update the list without spending too much time on that. The question here is also how it would affect distributions of operating systems other than GNU/Linux as the software stack is different. Since there is only 1 FSDG compliant Android distribution having that list for Replicant is probably overkill. And if a list is required for Android and that for some reasons people participate in it, not many people knows the Android source code well enough to be able to maintain it. Also some entries in the list of software that does not respect the FSDG don't have any recommended fix. That would also need to be fixed if we use this list for that. Would you like to look into it and send mails to this mailing list to propose fixes for the entries that lack any recommended fix? Denis.
pgpVateINwKkI.pgp
Description: OpenPGP digital signature
