From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Wojtek Kosior <koszko@koszko.org>
Cc: Andrew Tropin <andrew@trop.in>,
64958-done@debbugs.gnu.org,
Nicolas Goaziou <mail@nicolasgoaziou.fr>,
Cayetano Santos <csantosb@inventati.org>
Subject: bug#64958: [PATCH] gnu: Add emacs-chatgpt-shell.
Date: Sat, 09 Sep 2023 12:31:30 +0200 [thread overview]
Message-ID: <f65719315f9538ca30760b7213f31cad503cd146.camel@gmail.com> (raw)
In-Reply-To: <aebb8acd35e448b162b4a29198270cef8aba07ae.camel@gmail.com>
Am Montag, dem 31.07.2023 um 22:03 +0200 schrieb Liliana Marie Prikler:
> 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. See some social networking
> applications or messengers. 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?
Got two ayes, so pushed.
Cheers
prev parent reply other threads:[~2023-09-09 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 15:52 [bug#64958] [PATCH] gnu: Add emacs-chatgpt-shell Cayetano Santos via Guix-patches via
2023-07-30 20:51 ` Wojtek Kosior via Guix-patches via
2023-07-31 7:13 ` Cayetano Santos via Guix-patches via
2023-07-31 20:03 ` Liliana Marie Prikler
2023-08-01 10:02 ` Nicolas Goaziou
2023-08-01 10:35 ` Wojtek Kosior via Guix-patches via
2023-08-09 9:16 ` Andrew Tropin
2023-09-09 10:31 ` Liliana Marie Prikler [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=f65719315f9538ca30760b7213f31cad503cd146.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=64958-done@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=csantosb@inventati.org \
--cc=koszko@koszko.org \
--cc=mail@nicolasgoaziou.fr \
/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).