[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1024493: Proposed-RM: bs1770gain -- RoQA; inappropriate content



On Mon, 21 Nov 2022 13:53:43 +0100 Leon van Kammen <leonvankammen@gmail.com> wrote:
> my few cents: the problem with censorship is, once you start, the
> rabbithole is infinite.
> Whatever shitty homepage or comment it is, eventually it's just a homepage
> or comment.
> I think debian-devs should not be going down the rabbithole of scanning all
> code for 'bad' words, bad images, suspicious logos etc, as the creativity
> of humans in infinite too..
> The reactive path also plays in the hands of those activists (expect
> "debian turns out to be ran by X" youtube vids).

Cat't agree more. The offensive content has been patched out already there
is no merit to keep digging down on it more and more.
This package is actually useful as Petter already stated clearly, so removing
it just on the basis of a homepage does not seem good.

A sensible compromise maybe to remove the homepage field from d/control if that
serves the purpose. Debian was always about technology and shall always be about
that (let's not forget that at the end of the day it is an operating system).
Imposing debian values over each line of code over each package makes it no longer
fully focussed about technology. We can't and shouldn't expect each upstream's ideologies
to be same as ours, that's literally impossible.


I personally value inclusiveness, being excellent to people a lot but those things
should be applied to developers/contributors engaging in debian. Not for each and every
package's contributors that lands in debian.
I doubt if a user is going to migrate all the way through the source code,
and visit upstream homepage and get offended because _we_ vendor the software. In the
end it's our and the user's loss because a useful software would be dropped out of the bag for
reasons not related to technical aspect.

In the end, you will do what you want (i.e. maybe removing the package and I know that) but I just
wanted to speak up.
(And I see this as a different case as compared to the fortunes-off thing as this does not spit
that kind of virtiol onto user's terminal after the patch)

-- 
Best,
Nilesh

Attachment: signature.asc
Description: PGP signature


Reply to: