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: Inclusion of websocket library Date: Wed, 31 Jul 2013 00:25:36 -0400 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1375244758 28686 80.91.229.3 (31 Jul 2013 04:25:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 31 Jul 2013 04:25:58 +0000 (UTC) Cc: emacs-devel@gnu.org To: Andrew Hyatt Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 31 06:26:00 2013 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 1V4Nz2-0003ok-Mn for ged-emacs-devel@m.gmane.org; Wed, 31 Jul 2013 06:25:56 +0200 Original-Received: from localhost ([::1]:55961 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V4Nz2-0003DW-4W for ged-emacs-devel@m.gmane.org; Wed, 31 Jul 2013 00:25:56 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57932) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V4Nyr-0003DF-HC for emacs-devel@gnu.org; Wed, 31 Jul 2013 00:25:53 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V4Nyj-0000zJ-PT for emacs-devel@gnu.org; Wed, 31 Jul 2013 00:25:45 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:34075) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V4Nyj-0000z8-8N for emacs-devel@gnu.org; Wed, 31 Jul 2013 00:25:37 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABK/CFFFpZvt/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLDiYSFBgNJIgeBrMwjX2RCgOkeoFegmop X-IPAS-Result: Av4EABK/CFFFpZvt/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLDiYSFBgNJIgeBrMwjX2RCgOkeoFegmop X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="20224029" Original-Received: from 69-165-155-237.dsl.teksavvy.com (HELO pastel.home) ([69.165.155.237]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 31 Jul 2013 00:25:30 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 3E6B766EAF; Wed, 31 Jul 2013 00:25:36 -0400 (EDT) In-Reply-To: (Andrew Hyatt's message of "Fri, 12 Jul 2013 01:29:32 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.182 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:162279 Archived-At: > What is involved is putting this on GNU ELPA? Mostly, signing copyright paperwork. > I can certain do that, and maintain it there, but since my package is > already available via Marmalade, it is already available via an ELPA > that (I think) most ELPA-users are using. Is there a further > advantage to putting this on the GNU ELPA specifically? Some advantages: - the GNU ELPA archive is the only archive that's configured by default, so you can tell people to M-x package-install without worrying about whether or not they've added Marmalade to their config. - the code uses the same copyright rules as Emacs code, so that we can easily move code between the two. IOW it'd be ready for inclusion in Emacs proper. - all Emacs maintainers have write access to the code, so it can benefit from random cleanups or adjustments to new features. Stefan