Re: CoC policy for package contents

On Tue, Jul 22, 2025 at 07:37:27AM +0200, Salvo Tomaselli wrote:
> Hello,
> 
> 
> > Also, it seems to me that we're talking about an issue that isn't a
> > recurrent problem in the project, so it perhaps doesn't really need new
> > rules, a GR or another long thread in -vote.
> 
> It is a recurrent problem in the project. It's not daily but it
> certainly is recurrent.

This, exactly.

I have shown a few examples upthread. Those were only the ones *I* could
remember, so any examples that I didn't know about, or any examples that
I forgot about, were not there.

I think a clearer rule is a good idea. Right now, the release team have
chosen to take action because "Code of Conduct", but I'm not so sure
it's the right call, and I'm *also* not sure that the code of conduct
even applies to that (as others have also pointed out in this thread).

And that leaves out the question of whether the release team is really
the right team to be making this call, at all.

And honestly, if we think about this and decide as a project that
"anything is allowed except things that are obviously illegal", then
that's fine with me too. I just want us to think about this and make the
call, rather than leaving this to a team that really have a different
responsibility and will take the flak for doing something that shouldn't
even be their job but nobody else is doing it.

Do we *need* a content policy? I'm not 100% convinced we do, but clearly
there are people who do think so, and who feel that it should be
imposed. So if that's the case, then I think we should decide as a
project, rather than have one decided by a team which may or may not
have ended up with what happens to be the project's consensus.

Note that none of the above is meant as criticism to the release team.
They do a hard job under difficult circumstances, and that is
appreciated. It's just that this may not be the best use of their time
or experience.

And if we have a GR about this, that will also reduce the flak they get
for this, because then it's not their fault that the policy is what it
is.

> > Honest question: in ~30 years, how many packages have been removed from
> > our archive due to offensive content? 4? 5? How many of the removal
> > requests turned into big drama?
> 
> AFAIK, all of them.

Well, I imagine there might have been a few cases where people went "I
don't agree with this, it's sad, but meh, I don't have enough spoons to
fight this".