From: Adam Porter <adam@alphapapa.net>
To: emacs-devel@gnu.org
Subject: Re: How to contribute new package to GNU ELPA?
Date: Sat, 26 Dec 2020 14:24:13 -0600 [thread overview]
Message-ID: <875z4oz576.fsf@alphapapa.net> (raw)
In-Reply-To: 87lfdkioeo.fsf@dick
dick.r.chiang@gmail.com writes:
> s> Seems request.el will not be included in GNU ELPA.
> s> https://github.com/tkf/emacs-request/issues/112
>
> I disagree with your conclusion.
>
> Just because some random contributor (dickmao) is unwilling to solicit
> Mr. Arakaki's written release does not mean you must do the same.
> After all, his acquaintance with Mr. Arakaki is just as non-existent
> as yours.
>
> An importunate email campaign to the effect of "I will continue
> emailing you once per week until you respond definitively yes or no.
> Apologies in advance." seems apropos.
Mr. Arakaki has not commited to the repo in over 6.5 years:
https://github.com/tkf/emacs-request/commits?author=tkf Since, according
to GitHub, he has made over 4,000 commits to other projects in the past
year, it seems likely that he is uninterested in the project.
As I pointed out in my message of a few days ago about "Emacs HTTP
libraries," Request.el seems to have some issues with governance and
maintenance: https://github.com/tkf/emacs-request/issues/172
So although it's generally usable, considering 1) the bugs I encountered
in using it, ones that forced me to use url.el instead, 2) its
maintenance issues, and 3) the issues I pointed out regarding Curl and
handling of sensitive data on the command line and in temporary files, I
don't think it should be added to ELPA. (If you have more questions,
please refer to the message I posted, which I thoroughly footnoted.)
Instead, I would encourage Lars to continue the work on his
with-fetched-url branch, which looks very promising.
next prev parent reply other threads:[~2020-12-26 20:24 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 12:11 How to contribute new package to GNU ELPA? stardiviner
2020-12-19 6:22 ` Stefan Monnier
2020-12-19 7:08 ` stardiviner
2020-12-19 15:35 ` Stefan Monnier
2020-12-20 2:12 ` stardiviner
2020-12-20 12:29 ` Emacs HTTP libraries [was: Re: How to contribute new package to GNU ELPA?] Adam Porter
2020-12-20 13:44 ` Daniel Brooks
2021-03-28 1:47 ` T.V Raman
2021-03-28 22:42 ` Vladimir Sedach
2021-03-29 9:00 ` Sv: " arthur miller
2021-03-29 22:03 ` Jose E. Marchesi
2021-03-29 22:09 ` Darshit Shah
2021-03-30 11:12 ` Arthur Miller
2021-03-30 12:03 ` Daniel Martín
2021-03-30 12:46 ` Stefan Kangas
2021-03-30 12:50 ` Eli Zaretskii
2021-03-30 13:14 ` Lars Ingebrigtsen
2021-03-30 13:39 ` Eli Zaretskii
2021-03-30 13:48 ` Lars Ingebrigtsen
2021-03-30 13:55 ` Eli Zaretskii
2021-03-30 14:25 ` Eli Zaretskii
2021-03-30 14:34 ` Lars Ingebrigtsen
2021-03-30 15:15 ` Eli Zaretskii
2021-03-31 13:36 ` Lars Ingebrigtsen
2021-03-30 16:13 ` Clément Pit-Claudel
2021-03-30 16:21 ` Eli Zaretskii
2021-03-30 16:49 ` Clément Pit-Claudel
2021-03-30 17:03 ` Eli Zaretskii
2021-03-30 19:53 ` Clément Pit-Claudel
2021-03-31 1:08 ` Stefan Monnier
2021-03-31 6:22 ` Eli Zaretskii
2021-03-31 5:54 ` Eli Zaretskii
2021-03-30 20:53 ` T.V Raman
2021-03-31 6:02 ` Eli Zaretskii
2021-03-31 16:01 ` read-process-output-max (was: Emacs HTTP libraries) Stefan Monnier
2021-03-31 17:13 ` Eli Zaretskii
2021-03-31 23:05 ` read-process-output-max Stefan Monnier
2021-04-01 7:12 ` read-process-output-max Eli Zaretskii
2021-03-30 18:08 ` Sv: Emacs HTTP libraries [was: Re: How to contribute new package to GNU ELPA?] Arthur Miller
2021-03-31 8:59 ` Robert Pluim
2021-03-31 17:21 ` Daniel Brooks
2021-04-01 14:23 ` Robert Pluim
2021-04-01 16:09 ` Daniel Brooks
2021-04-02 12:10 ` Robert Pluim
2021-04-01 16:57 ` tomas
2021-03-29 23:56 ` Daniel Brooks
2020-12-20 13:56 ` David Engster
2020-12-20 17:27 ` Lars Ingebrigtsen
2020-12-20 14:36 ` Stefan Monnier
2020-12-20 15:17 ` Jean Louis
2020-12-20 15:23 ` Helmut Eller
2020-12-20 16:02 ` Daniel Brooks
2020-12-21 5:47 ` Richard Stallman
2020-12-21 14:17 ` Stefan Monnier
2020-12-22 5:17 ` Richard Stallman
2020-12-21 16:59 ` Philip K.
2020-12-21 17:23 ` Eli Zaretskii
2020-12-21 17:41 ` Arthur Miller
2020-12-21 18:13 ` Eli Zaretskii
2020-12-21 18:18 ` Arthur Miller
2020-12-21 23:51 ` Philip K.
2020-12-22 3:32 ` Lars Ingebrigtsen
2020-12-22 3:35 ` Eli Zaretskii
2020-12-22 10:38 ` Philip K.
2020-12-22 16:02 ` Eli Zaretskii
2020-12-22 16:59 ` Philip K.
2020-12-22 17:15 ` Eli Zaretskii
2020-12-22 5:20 ` Richard Stallman
2020-12-22 6:42 ` Arthur Miller
2020-12-22 10:49 ` Philip K.
2020-12-22 12:03 ` Jean Louis
2020-12-22 13:23 ` Philip K.
2020-12-23 4:26 ` Richard Stallman
2020-12-22 13:04 ` Arthur Miller
2020-12-23 4:26 ` Richard Stallman
2020-12-23 11:27 ` Arthur Miller
2020-12-24 5:51 ` Richard Stallman
2020-12-24 12:59 ` Arthur Miller
2020-12-25 4:41 ` Richard Stallman
2020-12-20 14:18 ` How to contribute new package to GNU ELPA? Stefan Monnier
2020-12-21 14:03 ` stardiviner
2020-12-26 9:09 ` stardiviner
2020-12-26 15:21 ` dick.r.chiang
2020-12-26 20:24 ` Adam Porter [this message]
2020-12-26 20:39 ` Stefan Monnier
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=875z4oz576.fsf@alphapapa.net \
--to=adam@alphapapa.net \
--cc=emacs-devel@gnu.org \
/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).