unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: zimoun <zimon.toutoune@gmail.com>, guix-devel@gnu.org
Subject: Re: Security patching and the branching workflow: a new security-updates branch
Date: Thu, 01 Apr 2021 14:44:07 +0200	[thread overview]
Message-ID: <cebede06565fb76981670484db8fe3d55d2aa76e.camel@zaclys.net> (raw)
In-Reply-To: <87lfa33tbo.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2644 bytes --]

Hello Ludo,

On Wed, 2021-03-31 at 23:29 +0200, Ludovic Courtès wrote:
> It’s unacceptable to call someone “obsessed” just because you
> disagree
> and calling Simon’s comments “harassment” is equally inappropriate.

I really do feel harassed by their comments, it's not just because I
disagree, it's that I feel they have been following me around in
several of my contributions repeating the same issues, I have heard
their criticism and I do disagree but I don't feel like bringing it up
over and over and over following me around is a great thing to do at
all!

I did not try to go and yell all around after for example 'guix pull'
was broken after some changes to substitutes handling that were pushed
for example. I just trust people to do the best. I know people want the
best for GNU Guix. I also want the best for GNU Guix. I am not trying
to somehow deliberately break GNU Guix.

> We’re all passionate about the project, and each one of us looks at
> it
> from a different angle.
> 
> You’re new to the project.  I think we’re all glad you joined; that
> has
> already boosted security work and the POWER9 port.  But we also have
> expectations: that you follow written rules (the code of conduct, the
> “Commit Access” section of the manual), and the unwritten rule that,
> as
> a newcomer, you would humbly listen to suggestions made by more
> experienced contributors.

I try to listen, and I think I have listened to criticism from many
different people. I think we've reached a point where I could not
listen anymore from Zimoun because I felt we were going in circles.
There's different opinions from different places it seems, where some
people agree with my way of doing and some others do not, and I felt
like I had more approval from other people and that while Zimoun's
criticism has been heard I have not acted upon all of their criticism.
Is it possible to do that?

> The unresolved issues Simon points out are not just technical
> problems;
> they’re a hindrance to our cooperation and to our well-being as a
> group.
> It’s completely okay to make mistakes, but it’s not okay to break the
> community rules and to dismiss the opinion of others as unimportant.

I do not dismiss other's opinion as not important, I disagree, what do
you want me to do? We have different way of doing things, if I do them 
I do them my way, if they do them they do it their way, what else can
we do here?

> 
> Please adjust accordingly.

I don't feel like that's entirely fair but I always strive to self-
improve.

> Thanks,
> Ludo’.

Léo

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-04-01 12:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26 20:10 Security patching and the branching workflow: a new security-updates branch Léo Le Bouter
2021-03-26 22:13 ` Christopher Baines
2021-03-26 22:30   ` Léo Le Bouter
2021-03-27  8:56     ` Christopher Baines
2021-03-27 12:29 ` zimoun
2021-03-27 12:42   ` Léo Le Bouter
2021-03-27 13:56     ` zimoun
2021-03-27 14:14       ` Léo Le Bouter
2021-03-30 11:48         ` zimoun
2021-03-31  0:01           ` Léo Le Bouter
2021-03-31 21:29             ` Ludovic Courtès
2021-04-01 12:44               ` Léo Le Bouter [this message]
2021-04-01 14:58                 ` Ricardo Wurmus
2021-04-01 15:10                   ` Léo Le Bouter
2021-04-01 15:42                   ` Léo Le Bouter

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=cebede06565fb76981670484db8fe3d55d2aa76e.camel@zaclys.net \
    --to=lle-bout@zaclys.net \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=zimon.toutoune@gmail.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).