unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Elis Hirwing <elis@hirwing.se>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] * elpa-packages (webpaste): New package
Date: Fri, 03 Dec 2021 12:06:54 +0100	[thread overview]
Message-ID: <d49e8c4a674f40dea40f62e29b7bbd9f6c142819.camel@hirwing.se> (raw)
In-Reply-To: <87tufqsio0.fsf@posteo.net>

[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]

On Thu, 2021-12-02 at 23:15 +0000, Philip Kaludercic wrote:
> Elis Hirwing <elis@hirwing.se> writes:
> 
> > On Thu, 2021-12-02 at 16:05 +0000, Philip Kaludercic wrote:
> > > Elis Hirwing <elis@hirwing.se> writes:
> > > 
> > > > I would like to submit a package that I maintain to the NonGNU
> > > > ELPA,
> > > > it's currently on MELPA, I've been maintaining it for years and
> > > > using
> > > > it for years.
> > > 
> > > Before someone else brings it up, have you considered adding the
> > > package
> > > to GNU ELPA?  Or are there reasons you are attempting to add the
> > > package
> > > to NonGNU ELPA first?
> > 
> > Partly because I haven't signed the CLA with GNU and that I have
> > contributors which I don't know if they have signed the CLA or not,
> > so
> > I just found it easier that way.
> 
> Looking at the contributor list, I certainly recognise more than a
> few
> names that have signed the CA and I'd expect to agree when asked if
> they
> would want to add the package to ELPA.  It is up to you if you would
> want to ask your contributors or not.
> 
> If you are sure that ELPA is not the right place, then adding the
> package to NonGNU ELPA shouldn't be an issue, and would certainly be
> a
> worthwhile addition.

I've now considered this and would still prefer the NonGNU ELPA.

Partly due to the extra work to check for CLA's for me from future
contributors, then also that it may scare of future contributors that
(like me) haven't done the necessary paperwork.

~ Elis

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-12-03 11:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 13:13 [PATCH] * elpa-packages (webpaste): New package Elis Hirwing
2021-12-02 16:05 ` Philip Kaludercic
2021-12-02 21:02   ` Elis Hirwing
2021-12-02 23:15     ` Philip Kaludercic
2021-12-03 11:06       ` Elis Hirwing [this message]
2021-12-03 11:24         ` Po Lu
2021-12-03 11:41           ` Elis Hirwing
2021-12-03 12:01             ` Stefan Kangas
2021-12-03 12:14               ` Elis Hirwing
2021-12-04 12:50                 ` Stefan Kangas
2021-12-04  8:36           ` Philip Kaludercic
2021-12-04  8:37         ` Philip Kaludercic
2021-12-04  5:40     ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d49e8c4a674f40dea40f62e29b7bbd9f6c142819.camel@hirwing.se \
    --to=elis@hirwing.se \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).