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: Adding packages to ELPA Date: Fri, 19 Sep 2014 10:44:35 -0400 Message-ID: References: <87wq97i78i.fsf@earlgrey.lan> <87sijqxzr2.fsf@newcastle.ac.uk> <877g11c8wh.fsf@gmx.us> <83fvfo15z7.fsf@gnu.org> <8361gj20h7.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1411139381 23152 80.91.229.3 (19 Sep 2014 15:09:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 19 Sep 2014 15:09:41 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Sep 19 17:09:34 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 1XUzoT-0002A0-9B for ged-emacs-devel@m.gmane.org; Fri, 19 Sep 2014 17:09:33 +0200 Original-Received: from localhost ([::1]:58792 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUzoQ-00027j-Lq for ged-emacs-devel@m.gmane.org; Fri, 19 Sep 2014 11:09:30 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44737) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUzQf-0001e8-Jl for emacs-devel@gnu.org; Fri, 19 Sep 2014 10:45:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XUzQY-0007gw-4u for emacs-devel@gnu.org; Fri, 19 Sep 2014 10:44:57 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:25489) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUzQQ-0007e4-Bf; Fri, 19 Sep 2014 10:44:42 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArUGAIDvNVNFpZEG/2dsb2JhbABZgwaDSsA9gRcXdIIlAQEBAQIBVhYKAwULCzQSFBgNJIgECNIZF456B4Q4BJQelHuBaoNMIQ X-IPAS-Result: ArUGAIDvNVNFpZEG/2dsb2JhbABZgwaDSsA9gRcXdIIlAQEBAQIBVhYKAwULCzQSFBgNJIgECNIZF456B4Q4BJQelHuBaoNMIQ X-IronPort-AV: E=Sophos;i="4.97,753,1389762000"; d="scan'208";a="90288567" Original-Received: from 69-165-145-6.dsl.teksavvy.com (HELO pastel.home) ([69.165.145.6]) by ironport2-out.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Sep 2014 10:44:36 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id D25E7642C6; Fri, 19 Sep 2014 10:44:35 -0400 (EDT) In-Reply-To: <8361gj20h7.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 19 Sep 2014 16:39:32 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.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:174554 Archived-At: >> So, it's important to be very proactive and to try and get packages into >> GNU ELPA very early on, when the copyright status is much more simple, >> so that the copyright assignments can be collected progressively as the >> contributions get accepted. > Why not add them to Emacs instead? Because I find it doesn't scale as well. - GNU ELPA packages can be released on their own schedule. - we're not seriously affected by bugs in GNU ELPA packages since they can be fixed and released independently. - the maintainer of `foo' might not like to have to download a 300MB repository to hack on her 300-lines package. > Having them in Emacs will almost immediately contribute to their > quality, because much more experienced eyes will look over them. I'd hope that the same holds for elpa packages. That's why you can type "make" in `elpa' to compile and prepare all the packages (you just need to add that directory to your package-directory-list). I strongly encourage all Emacs contributors/maintainers to have a checked out tree of `elpa' that they update alongside the `emacs' repository and to treat it as a "secondary" lisp directory. > On top of that, we gain more potential contributors to Emacs itself, > because having write access and a package in the core naturally leads > to more involvement in core development. The access rights to `elpa' and to `emacs' are the same already. Stefan