From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Andrew Hyatt Newsgroups: gmane.emacs.devel Subject: Re: Inclusion of websocket library Date: Wed, 31 Jul 2013 09:56:36 -0400 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c1c00c1132ba04e2cf18a4 X-Trace: ger.gmane.org 1375279006 25424 80.91.229.3 (31 Jul 2013 13:56:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 31 Jul 2013 13:56:46 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 31 15:56:49 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 1V4WtU-0007A6-ST for ged-emacs-devel@m.gmane.org; Wed, 31 Jul 2013 15:56:49 +0200 Original-Received: from localhost ([::1]:60229 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V4WtU-00035l-EE for ged-emacs-devel@m.gmane.org; Wed, 31 Jul 2013 09:56:48 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43817) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V4WtM-00035F-HM for emacs-devel@gnu.org; Wed, 31 Jul 2013 09:56:45 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V4WtK-0007CL-31 for emacs-devel@gnu.org; Wed, 31 Jul 2013 09:56:40 -0400 Original-Received: from mail-oa0-x234.google.com ([2607:f8b0:4003:c02::234]:40840) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V4WtJ-0007Bt-TE for emacs-devel@gnu.org; Wed, 31 Jul 2013 09:56:37 -0400 Original-Received: by mail-oa0-f52.google.com with SMTP id n12so1503001oag.25 for ; Wed, 31 Jul 2013 06:56:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JdpetL9TII7/ZlqBAsDKiuNgemnT/mJv7DwGsD9yWkc=; b=wqj5Bta56EipG/aM/64cHRA+41fFLe+aUAMiCAOpsvqg1mBs1k0MbOrocVm6ocldXE 7Hghc7cYP2S5RkvkaFFtbU2mr9smQI/dIVqe2VpXYW/ikVNjhFSWVPrd1wD+sg9NHWY+ U52GdIGitdDyhZzAnVSe19XzsQXFOQJbFLdWHIYdAQJ/Kx0sHnugO3V7KRA0t3/AtoQP Ja4jral3TcMMGktRbelb99h//hPb7vzZi5Z+5LSt2JamuOsxmlUFj/yLSf+0Qe4bG3J7 ngwzCQKx48Jn25NOAEC47fDK1zX7vksrnHEQ3iUqHgQx4NH4jK3L+zVfnNYpxwuRcZM3 RqSA== X-Received: by 10.182.53.234 with SMTP id e10mr59710227obp.47.1375278996727; Wed, 31 Jul 2013 06:56:36 -0700 (PDT) Original-Received: by 10.76.166.198 with HTTP; Wed, 31 Jul 2013 06:56:36 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4003:c02::234 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:162293 Archived-At: --001a11c1c00c1132ba04e2cf18a4 Content-Type: text/plain; charset=ISO-8859-1 OK, sounds like a good thing. How do I go about uploading my code to GNU ELPA, and keeping it updated? On Jul 31, 2013 12:25 AM, "Stefan Monnier" wrote: > > 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 > --001a11c1c00c1132ba04e2cf18a4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

OK, sounds like a good thing. How do I go a= bout uploading my code to GNU ELPA, and keeping it updated?

On Jul 31, 2013 12:25 AM, "Stefan Monnier&q= uot; <monn= ier@iro.umontreal.ca> wrote:
> 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<= br> > already available via Marmalade, it is already available via an ELPA > that (I think) most ELPA-users are using. =A0Is 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= ,
=A0 so you can tell people to M-x package-install without worrying about =A0 whether or not they've added Marmalade to their config.
- the code uses the same copyright rules as Emacs code, so that we can
=A0 easily move code between the two. =A0IOW it'd be ready for inclusio= n in
=A0 Emacs proper.
- all Emacs maintainers have write access to the code, so it can benefit =A0 from random cleanups or adjustments to new features.


=A0 =A0 =A0 =A0 Stefan
--001a11c1c00c1132ba04e2cf18a4--