unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Catonano <catonano@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>, Joshua Branson <jbranso@fastmail.com>
Subject: Re: my latest blog post
Date: Sat, 09 Jun 2018 14:24:50 +0200	[thread overview]
Message-ID: <877en8171p.fsf@elephly.net> (raw)
In-Reply-To: <CAJ98PDx=Uh=EhjthnVmBrTPbXXcPZjbjNWMuVSeZa3k5_yaCpQ@mail.gmail.com>


Catonano <catonano@gmail.com> writes:

>> Andy’s time is still limited.  What other people can do is discuss
>> *specific* cases on guile-devel and work towards a solution.  But please
>> do not demand of others to explain everything in detail.  (I’m directing
>> this at everyone who heeds my advice to go to guile-devel, not at any
>> one person in particular.)  In order to have a positive impact you also
>> need to learn enough about the state of the art to ensure that the
>> discussions can be productive.
>>
>
> I think I demonstrated I am ready to put some effort into this
>
> And I think this remark is unfair

I wrote this:

   But please do not demand of others to explain everything in detail.
   (I’m directing this at everyone who heeds my advice to go to
   guile-devel, not at any one person in particular.)

Rephrasing: I’d like to point this out to people who take this
opportunity to bemoan the lack of other features or who disagree with
what they think are different priorities.  You do not feel addressed if
you know you’ve made efforts in this area.

> And saying I should come on guile-dev and actually provide what I thin is
> useful, nowing that I can't (not immediately is not a fair answer either
>
> Because it's equivalent to a "fuck you"

Wow.  No.

I think that’s an *extremely* uncharitable reading of what I wrote.  I
will refrain from further comments in this thread lest what I write will
be misconstrued in a similar fashion.

>> With regards to the shouting match on #guile that you linked in your
>> blog post, I can only say that I would have likely stepped in had this
>> happened when I was around.  Textual communication certainly should not
>> reach these levels of apparent aggression.
>>
>
> What do you mean with "apparent" ?

I’m pretty bad at gauging emotion in textual communication and it’s
generally not easy to infer the intended tone in short text messages.
That said, the exchange you linked to appeared to me to be of an
aggressive nature.  That’s what I mean by “apparent”.

--
Ricardo

  reply	other threads:[~2018-06-10 12:11 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07 15:25 my latest blog post Catonano
2018-06-07 16:28 ` Joshua Branson
2018-06-08  4:24   ` Christopher Lemmer Webber
2018-06-08  6:18     ` Fis Trivial
2018-06-08 14:02       ` Ricardo Wurmus
2018-06-08  8:25     ` Catonano
2018-06-08 13:51       ` Fis Trivial
2018-06-08 14:25       ` Ricardo Wurmus
2018-06-09  7:47         ` Catonano
2018-06-09 12:24           ` Ricardo Wurmus [this message]
2018-06-09 13:07             ` Catonano
2018-06-09 15:29               ` Christopher Lemmer Webber
2018-06-09 13:51             ` Christopher Lemmer Webber
2018-06-07 17:03 ` Mark H Weaver
2018-06-07 19:40   ` Catonano
2018-06-08  9:39     ` Nils Gillmann
2018-06-08  9:45       ` Catonano
2018-06-08 18:05     ` Mark H Weaver
2018-06-09  7:00       ` Catonano
2018-06-09 10:39         ` Ricardo Wurmus
2018-06-09 10:52           ` Catonano
2018-06-09 12:14             ` Ricardo Wurmus
2018-06-09 13:03               ` Catonano
2018-06-10 10:53         ` Mark H Weaver
2018-06-07 18:11 ` Thorsten Wilms
2018-06-07 21:45 ` Alex Vong
2018-06-08  9:15 ` Julien Lepiller
2018-06-08  9:34   ` Clément Lassieur
2018-06-08  9:45     ` Julien Lepiller
2018-06-08 13:50   ` Widen info Oleg Pykhalov
2018-06-08 13:59     ` Julien Lepiller
2018-06-08 13:49 ` my latest blog post Ludovic Courtès
2018-06-09  5:59   ` Catonano
2018-06-09 22:49 ` myglc2
2018-06-10  0:51   ` Mark H Weaver
2018-06-10  6:55     ` Pjotr Prins
2018-06-10  9:07       ` Catonano
2018-06-10  9:29         ` Ricardo Wurmus
2018-06-10  9:30           ` Catonano
2018-06-10 10:37             ` Ricardo Wurmus
2018-06-10 10:45         ` Mark H Weaver
2018-06-10 12:06         ` Pjotr Prins
2018-06-10  7:58     ` Catonano
2018-06-10  9:26       ` Ricardo Wurmus
2018-06-10  9:27         ` Catonano
2018-06-10 19:13           ` Ludovic Courtès
2018-06-10  8:07   ` Catonano
2018-06-10 19:23     ` Ludovic Courtès
2018-06-10  8:17 ` my latest blog post [everyone, please take a cooldown break] Nils Gillmann
2018-06-10 13:33   ` Christopher Lemmer Webber
2018-06-10 14:18     ` Gábor Boskovits
2018-06-10 14:37       ` Kei Kebreau
2018-06-11  6:01         ` swedebugia

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=877en8171p.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=catonano@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=jbranso@fastmail.com \
    /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).