[PATCH 0/1] Add chromium-web-store extension

Hi, folks!

This patch adds chromium-web-store browser extension. Although I would like to

use Guix as well for installing chromium extensions, this is currently too

cumbersome. I've tried to "pack" a couple of extensions, some did work, some didn't.

So, I decided to fallback to Chrome Web Store for now. This chromium-web-store is

only missing part to do that.

P.S. A package built from this definition will be named `chromium-web-store-chromium`

due to the way `(make-chromium-extension ...)` names produced "extension packages".

Anthony (1):

gnu: browser-extensions: add chromium-web-store

gnu/packages/browser-extensions.scm | 35 +++++++++++++++++++++++++++++

1 file changed, 35 insertions(+)

--

2.35.3

---

gnu/packages/browser-extensions.scm | 35 +++++++++++++++++++++++++++++

1 file changed, 35 insertions(+)

Am Samstag, dem 04.06.2022 um 03:02 +0200 schrieb burning2007@ya.ru:

Do submit those that work.

You can do that, but as for the inclusion in Guix, please refer to the

FSDG [1], particularly "The system should have no repositories for

nonfree software and no specific recipes for installation of particular

nonfree programs. Nor should the distribution refer to third-party

repositories that are not committed to only including free software;

even if they only have free software today, that may not be true

tomorrow." Our importer infrastructure is already bending that rule;

there's no need to break it.

Cheers

[Removed anthony@example.com from CC because it's not a valid e-mail address]

burning2007@ya.ru schreef op za 04-06-2022 om 14:30 [+0300]:

External repositories are ok I think, no need to remove pip from Python

or ContentDB from Minetest or channels or "guix build -f" from Guix or

cabal.

Chrome Web Store is not just an external repository, it's a mostly non-

free repository (in contrast to, say, pypi, ContentDB), see my e-mail.

Greetings,

Maxime

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