unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Skyler Ferris via Guix-patches via <guix-patches@gnu.org>
To: 55790@debbugs.gnu.org
Subject: [bug#55790] [PATCH 0/1] Add chromium-web-store extension
Date: Mon, 11 Mar 2024 19:39:30 +0000	[thread overview]
Message-ID: <4db608bd-a791-41be-858d-44f0ac344bdf@protonmail.com> (raw)
In-Reply-To: <20220604010204.14054-1-burning2007@ya.ru>

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

Hi all,

It looks like there's a disagreement between Liliana and Maxime which was never fully addressed, so it's not clear if this will ever be merge-able.

My take is that Maxime's example of pip is relevant because the [pypi terms of use](https://pypi.org/policy/terms-of-use/) only requires that a royalty-free license is present, and non-free licenses can be royalty-free (I am not a lawyer). However, based on Liliana's interpretation of the FSDG the conclusion is "pip should not be included" rather than "the webstore should be included". Of course, removing pip is likely to cause problems for people as pip is a widely used method of managing python code. I do not know if any of the people in this conversation so far are legal experts and I would want to have a high level of confidence before proposing such a controversial change.

Considering that this email came from an address that cannot be valid, I think it is also fair to be concerned that this email might have been sent in bad faith with the intent of creating conflict and disrupting the project. Since we don't have any reason to think that including pip is a violation of the FSDG other than presumably amateur analysis, pip is a high-profile package so it's not likely to have been overlooked, and the only person who has expressed interest in including the webstore has gone out of their way to obfuscate their identity, I think it would be fair to simply close this issue with no further discussion. But I do not feel comfortable taking that action unilaterally considering the sensitivity of the matters discussed.

Regards,
Skyler

[-- Attachment #2: Type: text/html, Size: 2020 bytes --]

      parent reply	other threads:[~2024-03-11 19:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-04  1:02 [bug#55790] [PATCH 0/1] Add chromium-web-store extension burning2007
2022-06-04  8:28 ` [bug#55790] [PATCH 1/1] gnu: browser-extensions: add chromium-web-store burning2007
2022-06-04  8:48 ` [bug#55790] [PATCH 0/1] Add chromium-web-store extension Liliana Marie Prikler
2022-06-04 11:28   ` burning2007
2022-06-04 11:30   ` burning2007
2022-06-04 13:08     ` Maxime Devos
2022-06-04 13:09     ` Maxime Devos
2024-03-11 19:39 ` Skyler Ferris via Guix-patches via [this message]

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=4db608bd-a791-41be-858d-44f0ac344bdf@protonmail.com \
    --to=guix-patches@gnu.org \
    --cc=55790@debbugs.gnu.org \
    --cc=skyvine@protonmail.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).