From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: github.com@gnu.support Newsgroups: gmane.emacs.tangents Subject: Re: [syl20bnr/spacemacs] Proposal to improve GPL compliance (#14444) Date: Wed, 3 Mar 2021 08:44:33 +0300 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34520"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0 (3d08634) (2020-11-07) Cc: emacs-tangents@gnu.org To: "syl20bnr/spacemacs" Original-X-From: emacs-tangents-bounces+get-emacs-tangents=m.gmane-mx.org@gnu.org Wed Mar 03 06:49:46 2021 Return-path: Envelope-to: get-emacs-tangents@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 1lHKOH-0008sx-Uz for get-emacs-tangents@m.gmane-mx.org; Wed, 03 Mar 2021 06:49:45 +0100 Original-Received: from localhost ([::1]:59308 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lHKOG-0004qh-K4 for get-emacs-tangents@m.gmane-mx.org; Wed, 03 Mar 2021 00:49:44 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58890) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lHKO2-0004qZ-BA for emacs-tangents@gnu.org; Wed, 03 Mar 2021 00:49:30 -0500 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:40481) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lHKO0-00087P-4I for emacs-tangents@gnu.org; Wed, 03 Mar 2021 00:49:29 -0500 Original-Received: from localhost ([::ffff:41.210.141.203]) (AUTH: PLAIN securesender, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 000000000001E084.00000000603F2343.000067DC; Tue, 02 Mar 2021 22:48:51 -0700 Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=217.170.207.13; envelope-from=github.com@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-tangents@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-tangents-bounces+get-emacs-tangents=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-tangents" Xref: news.gmane.io gmane.emacs.tangents:606 Archived-At: * Lucius Hu [2021-03-01 22:33]: > > So the programs contained in Spacemacs package create modified > work. Maybe you think with "not modifying Emacs on the fly" that it > does not modify the OS executable on the fly. Your software is > written in Emacs Lisp (how I see it) and is modified work of > original. > > Point to a source file of emacs that is modified. > > > Compiling or not compiling is not essential. It is Emacs Lisp. No need > to compile > > This is hilarious. Anyone with elementary knowledge of how > interpreter works knows that the program needs to be compiled. We speak of the work in copyright terms. It does not matter how you call it, you can call it framework, configuration, etc. It does not matter because I have not spoken of technicalities or classification of type of software. What matters is that it is new package, new work, new software. It really does not matter if you modify C sources or you add Emacs Lisp, you have made the work. It is nice work. It is combination of various other works and Spacemacs programs. Thus it is new work in copyright terms. > > As it directly uses mainstream Emacs to > provide new Emacs version > > What are you talking about? Where is the new emacs? Emacs Lisp code is modifying the original Emacs. Emacs Lisp code in original Emacs is part of Emacs. Look inside of Emacs Lisp code distributed with Emacs to understand. > > It is also visibly not the same appearance so that demonstrates > the modification. > > Following your definition, if you change the wallpaper, colortheme, > etc of an operating system, you are considered to modify the > OS. This is just nonsense. I have not been speaking of the OS and I do not know how is this relevant, but here are my comments for you. If user changes a wallpaper, user did not write software and did not distribute software. It is not relevant to copyright. If a color theme is changed and it is not software, that is user's option to change it. If however a color theme is software and user decides to publish it, and that software runs with GNU Emacs, then such should be published with the appropriate license compatible with GNU GPLv3. The copyright notice must be placed properly in the file of the color theme. Spacemacs files do not have proper copyright notices, could you please look into that issue as that is one practical thing you can improve, it impacts users of Spacemacs and helps them understand the licensing.