From: Christopher Allan Webber <cwebber@dustycloud.org>
To: "Niels Möller" <nisse@lysator.liu.se>
Cc: Guix-devel <Guix-devel@gnu.org>,
"Torbjörn Granlund" <tg@gmplib.org>,
gmp-bugs@gmplib.org
Subject: Re: On being welcoming
Date: Fri, 18 Dec 2015 10:53:26 -0600 [thread overview]
Message-ID: <87a8p7lmna.fsf@dustycloud.org> (raw)
In-Reply-To: <nnlh8shy7c.fsf@armitage.lysator.liu.se>
Niels Möller writes:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> I dare say that technical expertise does not excuse disdain and
>> contempt. This behavior is actively harmful to GMP and GNU.
>
> Some developers may be more polite than others, but you really need to
> follow the bug reporting instructions. If it is a bug in gmp, we'd like
> to fix it, of course. Or if it's a configuration error, we'd like to
> resolve that too, but then we still need to start with the proper bug
> reporting information.
Certainly that's true, though of course a "please file this upstream in
GMP, we'd really like to handle it there" would be a nice way to handle
things. And of course hashing out what's happening locally is not
unusual behavior; Debian does much work to determine whether a bug is a
Debian-local issue or if it is an upstream issue, and if so (hopefully)
file and resolve upstream. It is not always a perfect process, but Guix
is also a distribution, and it's unsurprising that some conversation
would likely happen here first.
I doubt that Ludovic would have been opposed to filing upstream if the
upstream developers encouraged that... I don't think that was the issue
here.
>> It also illustrates why codes of conduct are more than a cosmetic
>> gimmick.
>
> I'd prefer not to not have the general code-of-conduct-debate on the
> gmp-bugs list.
Sure, though this conversation was on the Guix list.
> If you are disappointed about any individual's behaviour, I suspect it's
> usually more productive to start by trying to solve it off list (maybe
> you did? I wouldn't know of course). Mailing list discussons about
> personal issues tend to overheat too easily.
Sometimes that's true, and I agree, contacting an individual off-list is
usually the first line to handle, especially for smaller issues. In
general, I think this is the best approach to get good community
interaction. I don't know if it happened or not.
Though sometimes it is good to give a reply on-list, even in the first
instance, so that it can be clear to a community what behavior is and
isn't okay.
> (And it has taken me more than 30 minutes to formulate this reply, which
> I hope is sufficiently polite and respectful. I really hope that was time
> well spent).
I thought it was very polite and respectful, thank you!
- Chris
> Best regards,
> /Niels
next prev parent reply other threads:[~2015-12-18 16:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 11:29 GMP 6.1.0 without assembly lacks ‘__gmpn_invert_lib’ on ARM Ludovic Courtès
2015-12-16 13:02 ` Torbjörn Granlund
2015-12-16 22:39 ` Ludovic Courtès
2015-12-17 1:07 ` Torbjörn Granlund
2015-12-17 21:45 ` Christopher Allan Webber
2015-12-17 21:48 ` On being welcoming Ludovic Courtès
2015-12-18 4:25 ` Mike Mohr
2015-12-18 15:51 ` Niels Möller
2015-12-18 19:04 ` Torbjörn Granlund
2015-12-19 17:21 ` Mike Mohr
[not found] ` <nn1tajiwlk.fsf@armitage.lysator.liu.se>
2015-12-18 19:09 ` Christopher Allan Webber
2015-12-18 10:01 ` Niels Möller
[not found] ` <nnlh8shy7c.fsf@armitage.lysator.liu.se>
2015-12-18 14:45 ` Ludovic Courtès
[not found] ` <87mvt7lsrm.fsf@gnu.org>
2015-12-18 15:29 ` Niels Möller
2015-12-18 16:53 ` Christopher Allan Webber [this message]
2015-12-18 23:14 ` GMP 6.1.0 without assembly lacks ‘__gmpn_invert_lib’ on ARM Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8p7lmna.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=Guix-devel@gnu.org \
--cc=gmp-bugs@gmplib.org \
--cc=nisse@lysator.liu.se \
--cc=tg@gmplib.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).