unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: zx spectrumgomas <spectrumgomas@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Stepping back up as a co-maintainer
Date: Fri, 18 Oct 2019 11:51:52 +0200	[thread overview]
Message-ID: <CAFCvokBW_esS8x41rrQ-7-wFyR_Pz8cNfx4Fzt3TfEFgRSo6Lw@mail.gmail.com> (raw)
In-Reply-To: <875zkm1k1j.fsf@netris.org>

Yes, it clarifies things. I don't agree with you, but you have a noble
heart. I hope you all come to an agreement.Thanks.

On Fri, Oct 18, 2019 at 11:27 AM Mark H Weaver <mhw@netris.org> wrote:

> zx spectrumgomas <spectrumgomas@gmail.com> writes:
>
> > Of your words: “RMS has not yet appointed me as a co-maintainer.” , the
> > word “yet” I guess that means if he would have had his permission then
> you
> > wouldn't have needed it of the current maintainers, as I also deduce from
> > here:
> > “Frankly, it should not be your decision to make.”
> > https://lists.gnu.org/archive/html/guile-devel/2019-10/msg00021.html
>
> Yes, and I stand by that statement.  I made my case clearly in the
> message cited above.
>
> That said, I agree that it would have been improper for RMS to appoint
> me without first consulting the existing maintainers.  In fact,
> discussions are currently ongoing with Andy and Ludovic to resolve the
> situation, and I'm hopeful that we'll reach a mutually acceptable
> resolution.
>
> Regarding my phrase "In light of recent events", which I cited as the
> reason for my decision to return, I should now be clear what I meant by
> that:
>
> GNU is far more fragile than I had supposed.  It's like if your mother
> has a heart attack, and you suddenly realize that although you've always
> taken her presence in your life for granted, her mortality has now
> become real to you in a way that it wasn't before.
>
> I realize now that I took GNU's continued existence and integrity for
> granted, like a steady rock that I naively assumed would be there and
> stay strong regardless of whether I was a part of it or not.  Now I see
> that it will depend on all of us who care about software freedom to do
> what we can to keep GNU strong.
>
> I'm not interested in dividing the Guile community.  That would
> obviously be disastrous.  I fully support Andy's work, and I recognize
> that he is the main driver in core Guile development.  His continued
> participation is crucial.  Still, we must guard against Guile becoming a
> one-man show if it can possibly be avoided.  Keeping GNU strong means,
> among other things, resolving our differences peacefully and working
> together to make Guile better.  That's what I intend to do.
>
> I hope that clarifies things.
>
>       Thanks,
>         Mark
>


  parent reply	other threads:[~2019-10-18  9:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16  5:41 Stepping back up as a co-maintainer Mark H Weaver
2019-10-16  8:30 ` Vladimir Zhbanov
2019-10-16 13:38 ` sirgazil
2019-10-16 18:28 ` Jean Louis
2019-10-17  9:27 ` zx spectrumgomas
2019-10-17 10:24   ` Mikael Djurfeldt
2019-10-17 10:33     ` tomas
2019-10-17 13:03       ` Eli Zaretskii
2019-10-17 10:52     ` zx spectrumgomas
2019-10-17 11:21       ` Neil Jerram
2019-10-17 11:38         ` zx spectrumgomas
2019-10-18  3:36           ` zx spectrumgomas
2019-10-18  7:25             ` Mark H Weaver
2019-10-18  8:36               ` zx spectrumgomas
2019-10-18  8:52                 ` tomas
2019-10-18  8:58                   ` Ulrich Küttler
2019-10-18  9:26                 ` Mark H Weaver
2019-10-18  9:51                   ` Alex Sassmannshausen
2019-10-18  9:51                   ` zx spectrumgomas [this message]
2019-10-18 10:03                     ` tomas

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFCvokBW_esS8x41rrQ-7-wFyR_Pz8cNfx4Fzt3TfEFgRSo6Lw@mail.gmail.com \
    --to=spectrumgomas@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=mhw@netris.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.
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).