From: elais@fastmail.com
To: guix-devel@gnu.org, Thorsten Wilms <t_w_@freenet.de>
Subject: Re: Update CoC adapted from upstream 2.1 (instead of 1.4)
Date: Sat, 26 Feb 2022 11:17:47 -0700 [thread overview]
Message-ID: <83206437-fbbb-465d-8e19-25c854a38cd9@Spark> (raw)
In-Reply-To: <20220226100856.770778c0bb0eb051f8fd6481@freenet.de>
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
> This is very twisted and unfair to Taylan.
Is it though? Arguably all of this blew up because of how twisted and unfair Taylan is about this issue generally, given the wiki they run and the fact that they’ve been banned from at least one site for this fixation.
Everyone who has commented for the most part have already agreed that they’re ok with updating the CoC to match the upstream so why don’t we let this one go and change the CoC.
-- Elais Player
[-- Attachment #2: Type: text/html, Size: 914 bytes --]
next prev parent reply other threads:[~2022-02-26 18:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 0:05 Update CoC adapted from upstream 2.1 (instead of 1.4) zimoun
2022-02-25 0:09 ` Tobias Geerinckx-Rice
2022-02-25 7:47 ` Tissevert
2022-02-25 8:26 ` zimoun
2022-02-25 9:38 ` Thorsten Wilms
2022-02-25 8:16 ` Jonathan McHugh
2022-02-25 16:59 ` Taylan Kammer
2022-02-25 20:38 ` Philip McGrath
2022-02-25 20:50 ` Taylan Kammer
2022-02-25 22:05 ` Apology and proposal withdraw zimoun
2022-02-26 0:48 ` Update CoC adapted from upstream 2.1 (instead of 1.4) Liliana Marie Prikler
2022-02-26 1:20 ` Tobias Geerinckx-Rice
2022-02-26 9:08 ` Thorsten Wilms
2022-02-26 18:17 ` elais [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-25 15:18 Blake Shaw
2022-02-25 17:29 ` Taylan Kammer
2022-02-25 19:29 ` Ryan Sundberg via Development of GNU Guix and the GNU System distribution.
2022-02-25 22:20 Blake Shaw
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83206437-fbbb-465d-8e19-25c854a38cd9@Spark \
--to=elais@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=t_w_@freenet.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.