Toggle quote (11 lines)
> >> Doesn't this package effectively recommend a nonfree
> >> service-as-a-software-substitute? It'd be better to keep users away
> >> from such "services". Also, sorry to say, I'm pretty sure this is
> >> against the Free Software Distribution Guidelines
> > IANAL, but as far as I understand, having clients for various
> > "services" out there, even if those services are not distributed as
> > free software, is permissible.
>
> I also think so. In particular, this is not a SaaSS because there is no
> software to substitute in the first place.
As to centralized services — I also believe it is acceptable to include
clients for them. I mean tools like YouTube video downloaders.
I like how F-Droid approaches this — programs written for the purpose
of connecting to centralized services are labeled as having a possible
anti-feature.
However, I argue that ChatGPT is SaaSS rather than a pure "service".
The software being substituted is a "large language model" (LLM). It
isn't a *conventional* piece of software, it's a trained neural
network. But this doesn't mean it isn't software at all. I performs
advanced computation — that's also what software does.
And since nonfree software shouldn't be recommended in distros, the same
goes with SaaSS.
Toggle quote (4 lines)
> I think a clear rule is important, and my opinion is that it should be
> permissive. These clients are useful pieces of software, if only because
> they constitute an opportunity to learn code.
Even if it is a good opportunity, it's a side aspect. Nonfree software
wouldn't get packaged merely because it provides some good opportunity.
So it shouldn't affect the decision here on SaaSS, either.
Also, when looking for some code to take inspiration from, I prefer to
look at public git repositories rather than on distro packages. And
even if I were to learn elisp from Guix packages, there are already
many that do not have freedom issues.
Lastly, I admit this is a harder problem than it seems — search engines
could also be presented as (at least partially) SaaSS and it would be
hard to leave without these
Wojtek
-- (sig_start)
fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79 FD1A
♥ R29kIGlzIHRoZXJlIGFuZCBsb3ZlcyBtZQ== | ÷ c2luIHNlcGFyYXRlZCBtZSBmcm9tIEhpbQ==
? YnV0IEplc3VzIGRpZWQgdG8gc2F2ZSBtZQ== | ? U2hhbGwgSSBiZWNvbWUgSGlzIGZyaWVuZD8=
-- (sig_end)
On Tue, 01 Aug 2023 12:02:42 +0200 Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
Toggle quote (31 lines)
> Hello,
>
> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
>
> > Am Sonntag, dem 30.07.2023 um 22:51 +0200 schrieb Wojtek Kosior:
> >> Hi!
> >>
> >> > * gnu/packages/emacs-xyz.scm (emacs-chatgpt-shell): New variable.
> >>
> >> Doesn't this package effectively recommend a nonfree
> >> service-as-a-software-substitute? It'd be better to keep users away
> >> from such "services". Also, sorry to say, I'm pretty sure this is
> >> against the Free Software Distribution Guidelines
> > IANAL, but as far as I understand, having clients for various
> > "services" out there, even if those services are not distributed as
> > free software, is permissible.
>
> I also think so. In particular, this is not a SaaSS because there is no
> software to substitute in the first place.
>
> > IMHO, we would need a clear guideline for all of them rather than
> > singling out ChatGPT even if using it is harmful for everyone
> > involved.
> >
> > Nicolas, Andrew, WDYT?
>
> I think a clear rule is important, and my opinion is that it should be
> permissive. These clients are useful pieces of software, if only because
> they constitute an opportunity to learn code.
>
> Regards,