From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: [NonGNU ELPA] New package: llm Date: Mon, 21 Aug 2023 08:26:40 +0000 Message-ID: <87o7j04x8f.fsf@localhost> References: <54c21d90-8bd6-8723-9e33-d69179b37bd0@gmail.com> <87wmxrmmbz.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31279"; mail-complaints-to="usenet@ciao.gmane.io" Cc: ahyatt@gmail.com, jporterbugs@gmail.com, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Aug 21 10:27:10 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qY0Fi-0007vM-3g for ged-emacs-devel@m.gmane-mx.org; Mon, 21 Aug 2023 10:27:10 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qY0Es-00033T-SZ; Mon, 21 Aug 2023 04:26:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qY0Eq-000335-BT for emacs-devel@gnu.org; Mon, 21 Aug 2023 04:26:16 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qY0Em-0000LY-Vf for emacs-devel@gnu.org; Mon, 21 Aug 2023 04:26:15 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 2591B240028 for ; Mon, 21 Aug 2023 10:26:10 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1692606370; bh=yYX1yqyPxhorhPwsrQyRkM3oH2jjGJNEqjSDxG0BwCM=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=r4yBcKp3oWTG9opJ9P3yXhdVatX7i7wOwhLtj3jGUZ6yMeLqfF4ojmnKIj87NoqnY avHU+DoUQgB5QrR47inqni5aOib1nHRlHcIBmEK2+Chc3S+vpKJzNkSK/qhXvSHLU0 4yGRqZz3yyJgKDdjW5Zv6eL7PkwJ7rgHneXZo8ArbUbfbtKS829gSo+uuaEZpMEwLc gUELAbT/T7wWDGP81pFQnfisooTJfa2UUZBr6ux3s7DrCAdvIbcuT6JlVn6/AvKplK 7acjiUfa1+W5Rt50xXXZKQu018E6z23n9SRTKzSrnsmL0CkfBEkilm6N5NfEToEBul 4PkAIRfxD9hog== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4RTltT3LxVz6tvk; Mon, 21 Aug 2023 10:26:09 +0200 (CEST) In-Reply-To: Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -53 X-Spam_score: -5.4 X-Spam_bar: ----- X-Spam_report: (-5.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:309038 Archived-At: Richard Stallman writes: > Could you please tell me what conclusions or ideas that discussion > reached? Among other things, we have discussed Oracle SQL support in sql.el: https://list.orgmode.org/orgmode/E1pKtph-00082q-4Z@fencepost.gnu.org/ Richard Stallman writes: > ... > > The 'support' is essentially specialised comint based interfaces tweaked > > to work with the various SQL database engine command line clients such > > as psql for Postgres and sqlplus for Oracle. This involves codes to use > > the comint buffer to send commands/regions to the SQL client and read > > back the results and run interactive 'repl' like sessions with the > > client. > > Thanks. > > Based on our general policies, it is ok to do this. It is ok for > Postgres because that is free software. It is ok for Oracle because > that is widely known. Another relevant bit is related to the fact the Oracle SQL, through its free CLI, may actually connect to SaaS server. https://list.orgmode.org/orgmode/E1pKtpq-00086w-9s@fencepost.gnu.org/ Richard Stallman writes: > ... > > I am not sure about SaaSS - even postgresql (free software) may be used > > as a service provider by running it on server the user does not control. > > For sure, it CAN be used that way. If a Lisp package is designed to > work with a subprocess, a user can certainly rig it to talk with a > remote server. It is the nature of free software that people can > customize it, even so as to do something foolish with it. When a user > does this, it's per responsibility, not ours. > > We should not distribute specific support or recommendations to use > the Lisp package in that particular way. I also suggested the following, although did not yet find time open discussion on emacs-devel: https://list.orgmode.org/orgmode/87k015e80p.fsf@localhost/ Ihor Radchenko writes: > Richard Stallman writes: > >> > Would it then make sense to note the reasons why we support one or >> > another non-free software in a separate file like etc/NON-FREE-SUPPORT? >> >> I think it is a good idea to document the reasoning for these >> decision. But I think it does not necessarily have to be centralized >> in one file for all of Emacs. Another alternative, also natural, >> would be to describe these decisions with the code that implements the >> support. > > Will file header be a good place? > > Note that there is little point adding the reasons behind supporting > non-free software if they cannot be easily found. Ideally, it should be > a standard place documented as code convention. Then, people can > consistently check the reasons (or lack of) behind each individual > non-free software support decision. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at