-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I believe this proposal, at its core, has good value and is based on sound logic. My concern, however, is that despite the title "code of conduct" being used on both instances, the Mailing List Code of Conduct (CoC) presents a number of specific scenarios which are relevant to mailing lists but wouldn't make sense if included in the Debian Code of Conduct. In order to maintain the contextual difference between the CoCs, I suggest the following: - - Refine the Mailing List CoC as to remove any redundancies with the Debian CoC. - - Potentially rename the Mailing List CoC as to further reduce confusion. - I believe "mailing list etiquette" is a viable candidate. Sergio Moraes Data Management Analyst Content & Knowledge Management Specialist On Mon, Nov 23, 2020 at 12:23 PM Andrew M.A. Cater <amacater@einval.com> wrote: Folks, We currently have a minimal Debian mailing list code of conduct at https://www.debian.org/MailingLists which is, essentially, primarily tips on how to format email. At the same time, we have the main Debian Code of Conduct at https://www.debian.org/code_of_conduct} which is also referenced on the mailing lists page. This has the potential to be confusing and certainly the intent of the text overlaps in large part: is it now sensible to drop the mailing list code of conduct per se and refer only to the main Debian code of conduct in the future? The fewer resources we have to direct people to, have to keep up to date and to copy across various platforms then potentially the better. Note: For the avoidance of doubt: this is not an attempt to lessen the good effect of the mailing list code of conduct, which has been in effect for a long time, nor is it an excuse for another flame war as to whether/why we should have any code of conduct at all. The main Debian Code of Conduct, applicable to all Debian mailing lists, forums and public media is probably enough for all purposes, works well and was passed into effect by a GR: in some sense, that's not negotiable. This is merely an attempt to simplify things a little particularly for folk new to Debian. Your thoughts on this would be very much appreciated With all the very best wishes to all, as ever, Andy Cater [Speaking on behalf of the Debian Community team: this content of this email has also been reviewed by other members of the team] - -- Sergio Moraes Data Governance | Data Quality Analyst Metadata Analyst Phone: (734) 262-9830 -----BEGIN PGP SIGNATURE----- Version: FlowCrypt Email Encryption 8.0.0 Comment: Seamlessly send and receive encrypted email wsBzBAEBCgAGBQJfvDJPACEJEH/Duip6zfYJFiEEff7tjTXfP9APQvHWf8O6 KnrN9gmn2wgAgh59wGrE6m5agHt3/ZHozQgIqbuKvAu1QRLR/yNqUT1dufo/ gQgIYa80wZFz9PknP5UIc/9enfFbtH0AI53ghK8cUYqyPxX/Xgg5B3ccF1XH JI3Vw5KGmWVSMTN6v1tzoTsi6xfQy1ZkiKtUnDZ9v6F0Fp9hYXH5yVZj7mGB tDkZjpkrOmTe1CMoO10NWeGqRBFrsothgnulAqvF3e88z7v5N60bOeuZmn/u dZSPGMywHZAgFq97SlDTzF4S3NPhU/7so5vY6z0ukGuahQ5Yr7aOBwvH5bfV etMlUx2cpgQLT1J/NlDHKOotbAav/FmBMy/s5XPTfkp9nY1schAq4w== =PAqm -----END PGP SIGNATURE-----
Attachment:
0x80C27CCBD8ECA9D2.asc
Description: application/pgp-keys