unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jim Porter <jporterbugs@gmail.com>
Cc: emacs-devel@gnu.org, Susam Pal <susam.pal@gmail.com>
Subject: Re: Naming guidelines for ELPA packages
Date: Sun, 14 May 2023 19:00:55 -0400	[thread overview]
Message-ID: <jwvy1lqfrjx.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <fa61218a-aa60-81a6-8548-4b31b47585ee@gmail.com> (Jim Porter's message of "Sun, 14 May 2023 15:17:39 -0700")

> I agree. This is mainly an attempt to help package maintainers pick good (or
> "good enough") names on their own so that there's less time spent discussing
> this issue, and also to be upfront about what the Emacs/ELPA maintainers
> would prefer. That way, as a package maintainer, you can take these
> guidelines into account (or not) before you even submit the package.

Great.  Is there still something that needs to be resolved before we can
add this package to NonGNU ELPA, then?
[ BTW, I wish this went into GNU ELPA, instead.  Oh, and it should have
  a `.gitignore` along the lines of what I put in the appended patch.  ]


        Stefan


diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000000..af7e30dd09
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,3 @@
+/devil-autoloads.el
+/devil-pkg.el
+*.elc




  reply	other threads:[~2023-05-14 23:00 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11  5:23 [NonGNU ELPA] New package: devil Payas Relekar
2023-05-11  6:26 ` Po Lu
2023-05-11  6:33 ` Eli Zaretskii
2023-05-11  6:52   ` Philip Kaludercic
2023-05-11  7:07     ` Eli Zaretskii
2023-05-12 15:02       ` Brian Cully via Emacs development discussions.
2023-05-11  8:09     ` Susam Pal
2023-05-11  8:45       ` Philip Kaludercic
2023-05-11  8:58         ` Eli Zaretskii
2023-05-11  9:08           ` Susam Pal
2023-05-11  9:12             ` Philip Kaludercic
2023-05-11  9:19               ` Susam Pal
2023-05-11  9:34                 ` Ruijie Yu via Emacs development discussions.
2023-05-11 10:09                   ` Susam Pal
2023-05-11 10:31                     ` Susam Pal
2023-05-11 10:36             ` Eli Zaretskii
2023-05-11  8:56       ` Eli Zaretskii
2023-05-12 16:19   ` Jim Porter
2023-05-13  7:10     ` Philip Kaludercic
2023-05-13  9:05       ` Susam Pal
2023-05-15 22:12         ` Richard Stallman
2023-05-17 13:30         ` João Távora
2023-05-17 14:06           ` Philip Kaludercic
2023-05-17 15:41             ` João Távora
2023-05-17 15:46               ` Eli Zaretskii
2023-05-13 22:30     ` Richard Stallman
2023-05-14  4:29       ` Naming guidelines for ELPA packages (was: Re: [NonGNU ELPA] New package: devil) Jim Porter
2023-05-14  7:47         ` Naming guidelines for ELPA packages Philip Kaludercic
2023-05-14 19:23           ` Jim Porter
2023-05-14 19:33             ` Philip Kaludercic
2023-05-19  3:49               ` Jim Porter
2023-05-19  4:33                 ` Akib Azmain Turja
2023-05-20 16:51                   ` Philip Kaludercic
2023-05-21 21:03                   ` Richard Stallman
2023-05-14 21:36         ` Stefan Monnier via Emacs development discussions.
2023-05-14 22:17           ` Jim Porter
2023-05-14 23:00             ` Stefan Monnier [this message]
2023-05-15  1:36               ` Jim Porter
2023-05-15 22:15         ` Naming guidelines for ELPA packages (was: Re: [NonGNU ELPA] New package: devil) Richard Stallman
2023-05-15 22:15         ` Richard Stallman
2023-05-16  4:51           ` Jim Porter
2023-05-16  8:42           ` Naming guidelines for ELPA packages Madhu
  -- strict thread matches above, loose matches on Subject: below --
2023-05-15  1:40 Drew Adams

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=jwvy1lqfrjx.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=jporterbugs@gmail.com \
    --cc=susam.pal@gmail.com \
    /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).