all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Felix Lechner via <help-guix@gnu.org>
To: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>, Andy Tai <atai@atai.org>
Cc: help-guix@gnu.org
Subject: Re: sending to guix-patches does not seem to show?
Date: Sun, 18 Feb 2024 09:42:28 -0800	[thread overview]
Message-ID: <87le7h1xff.fsf@lease-up.com> (raw)
In-Reply-To: <877cj23y2x.fsf@gmail.com>

Hi Andy,
Hi Artyom,

> sending a patch to guix-patches does not seem to result in the
> creation of a new debbugs issue

> I'm having the same issue

You are not alone. [1][2]

Please note that I do not maintain Debbugs.  I would like to, but lost
an internal appeals process, which was non-public. I wrote:

> The Debbugs system is unmaintainble. FSF is unable and unwilling (!)
> to publish a code base for the version deployed on
> debbugs.gnu.org. I'd call that a disaster for a free-software advocacy
> group.
>
> Without a code base, no one can propose patches. It's absurd for
> anyone working with free software. On a practical level, it is
> impossible to fix or discuss issues like these. [3]

To preserve at least some privacy and perhaps goodwill, I'll paraphrase
the response. I believe it correctly reflects the applicable GPL-2
license [4] yet somehow missed my point:

    FSF did not write Debbugs. FSF does not distribute any version of
    it. No one who uses a program and patches it has an obligation to
    release the private modified version.

I hope that publishing the information did not violate anyone's privacy
expectations.  The Guix community deserved to know.

To sum it up, there are capable people who work on Debbugs. It's just
not me.  Please direct comments about Debbugs to the help-debbugs
mailing list. [5] With some luck, your issue will be addressed shortly.
Maybe it was fixed already. Thank you!

Kind regards
Felix

[1] https://mail.gnu.org/archive/html/help-debbugs/2024-02/msg00028.html
[2] https://mail.gnu.org/archive/html/help-debbugs/2024-02/msg00030.html
[3] https://lists.gnu.org/archive/html/guix-devel/2024-02/msg00187.html
[4] https://codeberg.org/lechner/debbugs-gnu/src/branch/history/COPYING
[5] https://lists.gnu.org/mailman/listinfo/help-debbugs


  reply	other threads:[~2024-02-18 17:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18  7:18 sending to guix-patches does not seem to show? Andy Tai
2024-02-18  9:45 ` Artyom V. Poptsov
2024-02-18 17:42   ` Felix Lechner via [this message]
2024-02-18 20:29     ` Andy Tai
2024-02-18 20:44       ` Felix Lechner via

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=87le7h1xff.fsf@lease-up.com \
    --to=help-guix@gnu.org \
    --cc=atai@atai.org \
    --cc=felix.lechner@lease-up.com \
    --cc=poptsov.artyom@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 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.