all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: guix-devel@gnu.org
Subject: Re: Why [bug#47081] Remove mongodb?
Date: Mon, 22 Mar 2021 17:14:51 +0100	[thread overview]
Message-ID: <87blbbxj0k.fsf@gnu.org> (raw)
In-Reply-To: <aa0180ed3aa4280dd975a75da1c28644ee4788de.camel@zaclys.net> ("Léo Le Bouter"'s message of "Sun, 21 Mar 2021 23:15:32 +0100")

Hi Léo,

Léo Le Bouter <lle-bout@zaclys.net> skribis:

>> Removing a package and its services is not something to do lightly:
>> it
>> breaks user configs with no recourse.
>> 
>> We must insist on getting more opinions on such matters, and I think
>> there just wasn’t enough feedback here.  I understand it can be
>> frustrating to wait for input, but in such a case, please do.  This
>> project has always strove for consensus.
>> 
>> Remember that the opinion of those who’ve been taking care of
>> security
>> issues in Guix for years, those who’ve been maintaining MongoDB,
>> those
>> who wrote the service and its tests, are invaluable; they must have a
>> say.  I insist: humbly solicit and wait for their feedback.
>> 
>
> I understand, and I did not think it was a light thing to do, no one
> mentionned anything we should do for the remove, so I actually do not
> know how we handle that but the security/non-free code thing put some
> urge into the situation, apologizes for moving on and pushing without
> waiting for more feedback, few people gave their feedback on IRC and by
> email and that's why I felt more confident doing the actual change.

Sure, now you know.  :-) For package removal, we have to wait for
feedback, pinging people if needed, and waiting longer than
usual—security pressure or not.  Removing a package can only happen if
there’s some consensus.

Thanks for your reply!

Ludo’.


  parent reply	other threads:[~2021-03-22 16:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12  0:56 [bug#47081] [PATCH 0/5] gnu: Remove mongodb Léo Le Bouter via Guix-patches via
2021-03-12  0:57 ` [bug#47081] [PATCH 1/5] gnu: Remove mongo-tools Léo Le Bouter via Guix-patches via
2021-03-12  0:57   ` [bug#47081] [PATCH 2/5] doc: Remove mongodb-service-type Léo Le Bouter via Guix-patches via
2021-03-12  0:57   ` [bug#47081] [PATCH 3/5] tests: databases: Remove mongodb test Léo Le Bouter via Guix-patches via
2021-03-12  0:57   ` [bug#47081] [PATCH 4/5] services: Remove mongodb service Léo Le Bouter via Guix-patches via
2021-03-12  0:57   ` [bug#47081] [PATCH 5/5] gnu: Remove mongodb Léo Le Bouter via Guix-patches via
2021-03-12  0:59 ` [bug#47081] [PATCH v2 1/6] gnu: Remove go-gopkg.in-mgo.v2 Léo Le Bouter via Guix-patches via
2021-03-12  0:59   ` [bug#47081] [PATCH v2 2/6] gnu: Remove mongo-tools Léo Le Bouter via Guix-patches via
2021-03-12  0:59   ` [bug#47081] [PATCH v2 3/6] doc: Remove mongodb-service-type Léo Le Bouter via Guix-patches via
2021-03-12  0:59   ` [bug#47081] [PATCH v2 4/6] tests: databases: Remove mongodb test Léo Le Bouter via Guix-patches via
2021-03-12  0:59   ` [bug#47081] [PATCH v2 5/6] services: Remove mongodb service Léo Le Bouter via Guix-patches via
2021-03-14 14:54     ` Christopher Baines
2021-03-14 14:58       ` Léo Le Bouter via Guix-patches via
2021-03-14 15:31         ` Christopher Baines
2021-03-16 10:11           ` bug#47081: " Léo Le Bouter via Guix-patches via
2021-03-12  0:59   ` [bug#47081] [PATCH v2 6/6] gnu: Remove mongodb Léo Le Bouter via Guix-patches via
2021-03-17 16:56 ` Why [bug#47081] Remove mongodb? zimoun
2021-03-17 17:09   ` Léo Le Bouter
2021-03-17 17:56     ` zimoun
2021-03-17 18:16       ` Léo Le Bouter
2021-03-17 18:51         ` zimoun
2021-03-17 19:05           ` Léo Le Bouter
2021-03-17 19:11           ` Léo Le Bouter
2021-03-17 21:24             ` zimoun
2021-03-20 11:37     ` Ludovic Courtès
2021-03-21 22:15       ` Léo Le Bouter
2021-03-22  9:55         ` Efraim Flashner
2021-03-22 16:14         ` Ludovic Courtès [this message]
2021-03-22 16:45           ` Jack Hill
2021-03-17 17:20   ` 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

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

  git send-email \
    --in-reply-to=87blbbxj0k.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=lle-bout@zaclys.net \
    /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.