From: Richard Stallman <rms@gnu.org>
To: Adam Porter <adam@alphapapa.net>
Cc: cavandusen@gmail.com, jdtsmith@gmail.com, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: activities
Date: Wed, 31 Jan 2024 22:49:11 -0500 [thread overview]
Message-ID: <E1rVO4d-00072i-RB@fencepost.gnu.org> (raw)
In-Reply-To: <25fcd3d0-3fa7-4b52-8afe-4f627c0f7f83@alphapapa.net> (message from Adam Porter on Mon, 29 Jan 2024 18:24:48 -0600)
[[[ 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’m not sure I follow. Most of the time package authors don’t
> > ssy anything until they want to publish the package, so how can
> > the maintainers suggest to them to contribute to an existing
> > package?
> >
> > An alternative would be for potential package authors to post to
> > emacs-devel, stating that they would like to see feature foo in
> > package bar. If it turns out that it is not feasible to
> > implement the feature, then sure, a new package can be created.
> Please don't forget the possibility that the author has already
> considered and rejected the idea to modify an existing library. I
> reached this decision over 3 years ago, before I started working on
> burly.el, which has led me to finally develop activities.el. Sometimes
> it is best to start with a fresh perspective, rather than trying to
> shoehorn ideas into an existing framework.
First, I have no opinions about what to do with activities.el in
particular. It could potentially be useful for many users, but it
probably won't be useful for me on a Linux console. It doesn't seem
to affect Emacs at a deeper level. So I decided to leave its design
issues to others. I'm writing only about this broader question.
I am glad that you first considered adding the feature to an existing
package. Thinking about that was a wise thing to do.
You reached the conclusion that it was better to make a new, separate
package. Maybe that is right. (I don't know the details so I have no
opinion about it.)
Nonetheless, it would be good if everyone considering a new feature
were to ask for advice on emacs-devel about the best way to implement
it before starting to write it.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2024-02-01 3:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 0:59 [ELPA] New package: activities Adam Porter
2024-01-26 7:33 ` Philip Kaludercic
2024-01-26 10:36 ` Adam Porter
2024-01-29 19:50 ` Adam Porter
2024-01-30 7:16 ` Philip Kaludercic
2024-01-30 7:43 ` Adam Porter
2024-01-26 7:45 ` Eli Zaretskii
2024-01-26 10:42 ` Adam Porter
2024-01-26 12:32 ` Eli Zaretskii
2024-01-26 21:59 ` Adam Porter
2024-01-27 7:08 ` Eli Zaretskii
2024-01-27 8:46 ` Adam Porter
2024-01-27 14:53 ` Eric S Fraga
2024-01-27 15:32 ` Eli Zaretskii
2024-01-27 16:14 ` Sergey Organov
2024-01-28 11:25 ` Eric S Fraga
2024-01-29 10:45 ` Sergey Organov
2024-01-29 13:03 ` Philip Kaludercic
2024-01-29 22:23 ` Sergey Organov
2024-01-29 15:29 ` Fraga, Eric
2024-01-26 8:25 ` Eshel Yaron
2024-01-26 10:48 ` Adam Porter
2024-01-29 21:48 ` JD Smith
2024-01-30 0:08 ` Chris Van Dusen
2024-01-30 0:24 ` Adam Porter
2024-02-01 3:49 ` Richard Stallman [this message]
2024-01-30 2:50 ` JD Smith
-- strict thread matches above, loose matches on Subject: below --
2024-01-27 19:20 Drew Adams
2024-02-01 5:33 Joseph Turner
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=E1rVO4d-00072i-RB@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=adam@alphapapa.net \
--cc=cavandusen@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jdtsmith@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.