Re: CoC policy for package contents

gregor herrmann <[email protected]> Tue, 22 Jul 2025 00:24:06 +0200

Newsgroups	gmane.linux.debian.devel.vote
Message-ID	<[email protected]>

On Mon, 21 Jul 2025 19:22:22 +0200, Wouter Verhelst wrote:

>On Mon, Jul 21, 2025 at 04:59:32PM +0200, Iustin Pop wrote:
>> My point is here that setting a CoC for package data is just a proxy for
>> what we actually want, which I'm not sure is clear (to me; it might
>> already be to other people). If it is, then deriving the CoC for
>> packages from it should be rather straightforward.
>Honestly, what *I* want is an answer, that we all can agree with, to the
>question of whether the code of conduct applies to what we package, and
>if so whether it fully applies or only partially.

I'm feeling somewhat uneasy, and/because I think we have a logical 
problem here:
- The CoC is about interaction between people;
- what we are discussiong right now is accaptable contents of 
   packages (messages, texts).

That's categorically different; I can't be respectful, assume good 
faith, be collaborative, be concise, be open, etc. against a text (as 
I can be about other people's behaviour).

I see the point in this topic about creating rules about what texts 
we want and don't want to have in Debian. But I strongly think that 
framing this as "application of the Debian CoC for packages" is a 
logical dead end. - If we want this, we need to create some new "What 
language is acceptable in Debian" rules.

Cheers,
gregor

-- 
  .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
  : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
  `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
    `-

signature.asc (application/pgp-signature, 963 B)