Sean Whitton dijo [Wed, Nov 22, 2017 at 05:18:37PM -0700]: > > So to be concrete, how about this: > > > > N. Packages with potentially offensive content > > > > As a maintainer you should make a judgement about whether the > > contents of a package is appropriate to include, whether it needs > > any kind of content warning, and whether some parts should be split > > out into a separate package (so that users who want to avoid certain > > parts can do so). In making these decisions you should take into > > account the project's views as expressed in our Diversity Statement. > > > > If you split out (potentially) offensive or disturbing material into > > a separate package, you should usually mark this in the package name > > by adding "-offensive". For example, "cowsay" vs > > "cowsay-offensive". In this situation the "-offensive" package can > > be Suggested by the core package(s), but should not be Recommended > > or Depended on, so that it is not installed by default. > > I second this patch. I suggest we add it as section 3.1.1, i.e., as a > subsection to 3.1 "The package name". > > Iain, Gunnar and Steve: could you repeat your seconding of this patch to > this debian-policy bug, please? Kindly quote the above text that you > are seconding. > > For posterity, the rest of the discussion outside of this bug may be > found here: https://lists.debian.org/debian-devel/2017/11/msg00209.html Right. I second this patch. Thanks, Sean, for doing the administrative steps!
Attachment:
signature.asc
Description: PGP signature