From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: package and testing rant (was Re: package.el, auto-installation, and auto-removal) Date: Wed, 12 Nov 2014 18:31:11 -0500 Message-ID: References: <87a943umku.fsf@lifelogs.com> <87ppcvm7fj.fsf@newcastle.ac.uk> <87vbmndk46.fsf@lifelogs.com> <87wq72ls2h.fsf@ferrier.me.uk> <87k332lnn3.fsf_-_@ferrier.me.uk> <878ujhtx89.fsf@Rainer.invalid> <8761eki9ym.fsf@ferrier.me.uk> <87sihogkt0.fsf@ferrier.me.uk> <87bnocgh1r.fsf@ferrier.me.uk> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1415835093 14152 80.91.229.3 (12 Nov 2014 23:31:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 12 Nov 2014 23:31:33 +0000 (UTC) Cc: Achim Gratz , emacs-devel@gnu.org To: Nic Ferrier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 13 00:31:27 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XohNn-0001dB-E3 for ged-emacs-devel@m.gmane.org; Thu, 13 Nov 2014 00:31:27 +0100 Original-Received: from localhost ([::1]:57216 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XohNm-0002IK-TU for ged-emacs-devel@m.gmane.org; Wed, 12 Nov 2014 18:31:26 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43016) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XohNe-0002HH-IV for emacs-devel@gnu.org; Wed, 12 Nov 2014 18:31:24 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XohNY-0000xY-IK for emacs-devel@gnu.org; Wed, 12 Nov 2014 18:31:18 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:38800) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XohNY-0000xI-Em for emacs-devel@gnu.org; Wed, 12 Nov 2014 18:31:12 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhQNAOatTlRLd+sd/2dsb2JhbABcgw5UWII2hn7EDIdHBAICgRwXAQF8hAMBAQMBViMFCwsOJhIUGA0kiEsJDctlAQEBAQYBAQEBHpEIB4RLBYtkhAWGZoJEBYV6jV6DH4IRgW+CNIFiHy8BgkoBAQE X-IPAS-Result: AhQNAOatTlRLd+sd/2dsb2JhbABcgw5UWII2hn7EDIdHBAICgRwXAQF8hAMBAQMBViMFCwsOJhIUGA0kiEsJDctlAQEBAQYBAQEBHpEIB4RLBYtkhAWGZoJEBYV6jV6DH4IRgW+CNIFiHy8BgkoBAQE X-IronPort-AV: E=Sophos;i="5.04,797,1406606400"; d="scan'208";a="96799770" Original-Received: from 75-119-235-29.dsl.teksavvy.com (HELO pastel.home) ([75.119.235.29]) by ironport2-out.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 12 Nov 2014 18:31:11 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 3C6D943C2; Wed, 12 Nov 2014 18:31:11 -0500 (EST) In-Reply-To: <87bnocgh1r.fsf@ferrier.me.uk> (Nic Ferrier's message of "Wed, 12 Nov 2014 23:01:04 +0000") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:176861 Archived-At: >> No: many (most?) savannah gnu projects don't require copyright >> assignments. Also, when maintainers disappear, it's rather >> problematic to get bugs fixed. > A GNU project is a GNU project, is my understanding. savannah can host > non-gnu or GNU. GNU projects all need (C) assignment. You can't be GNU > without that. Of course you can. Bazaar is/was a GNU project, and its copyright belongs very clearly to Canonical (who used a similar copyright assignment principle, except without the same guarantees that they wouldn't misuse that copyright ;-). See https://www.gnu.org/help/evaluation.html for details of what it means to be "a GNU package". > Maybe that changed? It's been that way since before Savannah existed, AFAIK. > I don't see why it's any more easy to get bugs fixed. If a maintainer > for a GNU project disappears there's a regular course of action to chase > them up or hand off control. Isn't there? There used to be. It takes months, going through various intermediaries to get access rights, ... Whereas with the current setup I can install a bug fix as soon as git.sv.gnu.org is back online (oh wait, it is back online!), without even having to think about it. > But my comparison is what most authors will experience. Then they won't contribute to GNU ELPA. We're no worse, since they wouldn't contribute to Emacs either. I don't see the point of making GNU ELPA into a copy of MELPA/Marmalade: those already exist and they work well, AFAICT. > I mean that people who want to have an odd build will attempt to make > the Makefile do it and then break it. Which Makefile? elpa/Makefile? This file is not used directly by elpa.gnu.org, there's a manual step to update the file used by elpa.gnu.org, so the risk is very small (as long as someone monitors the elpa-diffs commits, of course). > Yes. But also, my repo is mine. We have to have discipline around the > Emacs source tree and I think everyone undestands that's shared. But the > expectation surely would be that my branch of the elpa.git is mine. If you don't want Emacs maintainers to contribute directly to your code, then elpa.git might indeed not be the best choice for you. > Really handy vs safe is something I think should err on the side of safe. Given the general quality of Elisp packages, I'm not sure it's worth the trouble. Also, in case there's a packaging bug, you can fix it trivially with a single commit bumping the version one more time. > Maybe you don't know enough about software ecosystems? Maybe. Stefan