unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Kangas <stefan@marxist.se>
Cc: emacs-devel@gnu.org
Subject: Re: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package
Date: Wed, 19 Jan 2022 09:03:05 +0000	[thread overview]
Message-ID: <87y23ct7w6.fsf@posteo.net> (raw)
In-Reply-To: <CADwFkm=e5pVqLrp8VUfGPo2mo9tB+2r3XDRdKNHNS+mM15HV1g@mail.gmail.com> (Stefan Kangas's message of "Sun, 16 Jan 2022 14:32:47 -0800")

Stefan Kangas <stefan@marxist.se> writes:

> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Interesting idea, though it should probably be opt-in, at the risk of
>> skewing the popularity data towards enthusiasts.  Just one thing: It
>> seems like this would either require a special server or to scrub the
>> server logs.  Is either of that feasible?
>
> I don't know what you mean by scrubbing the server logs, but my idea is
> that we just extract whatever data we need from it, while ensuring that
> we remove any personal identifiers.

Not sure why I wrote "scrubbing", I just meant to say that since
the packages are to my knowledge hosted statically, one would have to
use the HTTP logs to check for queries in the URL.

>> It might not be bad to collect these notes somewhere.  I also have my
>> private notes, and if more people want to contribute, being able to
>> quickly check what the status of a package is (waiting for a patch to be
>> applied, obsoleted, ...) would be useful.
>
> I wouldn't mind just keeping a separate org-file in nongnu.git or even
> just notes directly in the elpa-packages file.  The main problem will be
> to ensure that such notes don't go too wildly out of date.

In that case elpa-packages might be preferable.

>>  I agree that it would be preferable,
>> but a tone for what packages are added to NonGNU ELPA can already be
>> set.
>
> I think we agree; my point is merely that the tone we want to set will
> carry more weight to the extent that NonGNU ELPA is successful and
> widely used.

Yes, I agree.

>>  It might be possible to spread NonGNU
>> ELPA via compat (https://git.sr.ht/~pkal/compat), as soon as it is
>> released.  It seems that there is already some interest in using this
>> package, most notably from transient.  But as the package is already
>> borderline heretical, I hesitate to do something like this (the same
>> applies to updating the default rcirc and erc server lists).
>
> Personally, I would just do it.  The new defaults are arguably just
> better in those cases; no one will benefit from not having NonGNU ELPA
> or trying to connect to an almost dead IRC network.

Ok, I will use this thread as an excuse if anyone were to complain ^^.

> BTW, could you consider adding the fix for the vulnerability in
> enriched-text-mode on Emacs < 25.3, as detailed in etc/NEWS.25?

I can take a look at that, thanks for the reminder!

-- 
	Philip Kaludercic



  parent reply	other threads:[~2022-01-19  9:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <164145738158.2838.5769558384331859964@vcs2.savannah.gnu.org>
     [not found] ` <20220106082302.0A19CC0DA1E@vcs2.savannah.gnu.org>
2022-01-06 10:02   ` [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package Philip Kaludercic
2022-01-06 12:00     ` Stefan Kangas
2022-01-06 13:35       ` Philip Kaludercic
2022-01-06 14:30         ` Packages quality (was: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package) Stefan Monnier
2022-01-06 15:03           ` Bozhidar Batsov
2022-01-06 17:07             ` Packages quality Stefan Monnier
2022-01-06 19:50               ` Tim Cross
2022-01-07  7:54               ` Stefan Kangas
2022-01-07 11:45                 ` John Yates
2022-01-07 12:16                   ` Stefan Kangas
2022-01-07 15:52                     ` John Yates
2022-01-07  7:55             ` Packages quality (was: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package) Stefan Kangas
2022-01-07 10:22               ` Bozhidar Batsov
2022-01-07 10:54                 ` Stefan Kangas
2022-01-06 17:28           ` Packages quality Philip Kaludercic
2022-01-06 19:55         ` [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package Juri Linkov
2022-01-07  7:55         ` Stefan Kangas
2022-01-16 17:49           ` Philip Kaludercic
2022-01-16 22:19             ` Stefan Monnier
2022-01-19  8:57               ` Philip Kaludercic
2022-01-19 15:19                 ` Stefan Monnier
2022-01-16 22:32             ` Stefan Kangas
2022-01-16 23:16               ` Ergus
2022-01-19  9:05                 ` Philip Kaludercic
2022-01-16 23:47               ` Stefan Monnier
2022-01-19  9:03               ` Philip Kaludercic [this message]
2022-01-17  7:37             ` Jean Louis
2022-01-19  9:10               ` Philip Kaludercic
2022-01-07 10:02         ` Stefan Kangas
2022-01-10  1:18           ` Stefan Monnier
2022-01-07  9:38     ` Augusto Stoffel

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=87y23ct7w6.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=stefan@marxist.se \
    /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).