From: Jim Porter <jporterbugs@gmail.com>
To: rms@gnu.org
Cc: eliz@gnu.org, relekarpayas@gmail.com, philipk@posteo.net,
susam.pal@gmail.com, emacs-devel@gnu.org
Subject: Re: Naming guidelines for ELPA packages (was: Re: [NonGNU ELPA] New package: devil)
Date: Mon, 15 May 2023 21:51:51 -0700 [thread overview]
Message-ID: <e68419dd-6d6a-cc75-9736-dca4c1b14cc8@gmail.com> (raw)
In-Reply-To: <E1pygTK-0004et-1U@fencepost.gnu.org>
On 5/15/2023 3:15 PM, Richard Stallman wrote:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> I think your guideline text is good. It's quite clear, and readable
> too.
>
> But I'm confusd by this subsequent comment:
>
> > However, I also think it's important to show how you can
> > come up with a good compromise if you're a package author who just can't
> > let go of your fun package name. In my mind, showing in the
> > documentation how to compromise on this would go a long way towards
> > making package authors not feel like they're being micromanaged.
>
> The last paragraph of your draft text, about goblin-functions,
>
> > Instead, I finally opt for a compromise: I'll still use "Goblin" when
> > documenting the package and prefix names in my code with "goblin-", but
> > I decide to submit it to GNU ELPA as "goblin-functions". While this
> > isn't as descriptive as "gobject", it does at least provide a hint to
> > the reader that this is a collection of functions (intended for other
> > Lisp authors, as opposed to end users).
>
> seems to do that -- so why is a change needed?
I just want to adjust the emphasis of the text to gently nudge package
maintainers to choose something as simple as possible like "gobject" if
they can (or if they're willing). I think the final draft will be pretty
close to how it is now, but with a couple extra sentences to add more
detail.
> I think goblin-gobjects might be a superior compromise.
That's a good idea. I'll change the text to use that name instead. Thanks.
next prev parent reply other threads:[~2023-05-16 4:51 UTC|newest]
Thread overview: 42+ 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
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 [this message]
2023-05-16 8:42 ` Naming guidelines for ELPA packages Madhu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e68419dd-6d6a-cc75-9736-dca4c1b14cc8@gmail.com \
--to=jporterbugs@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
--cc=relekarpayas@gmail.com \
--cc=rms@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.