From: Yoni Rabkin <yoni@rabkins.net>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Distribution statistics for ELPA and EMMS
Date: Fri, 14 Jul 2023 10:02:16 -0400 [thread overview]
Message-ID: <875y6mzj4n.fsf@rabkins.net> (raw)
In-Reply-To: <87zg3zotzq.fsf@posteo.net> (Philip Kaludercic's message of "Fri, 14 Jul 2023 07:03:05 +0000")
Philip Kaludercic <philipk@posteo.net> writes:
> Eduardo Ochs <eduardoochs@gmail.com> writes:
>
>> On Thu, 13 Jul 2023 at 17:55, Yoni Rabkin <yoni@rabkins.net> wrote:
>>>
>>> I want to start the talk with the claim that Emms is a popular music and
>>> video package for Emacs. However, I have absolutely no numbers or
>>> statistics to back that claim. Is there a way to find out? Are any
>>> statistics collected by ELPA?
>>>
>>> Is there a way to answer the question: how many times was Emms installed
>>> in 2022?
>>
>> Hey, thanks for asking that!
>>
>> I'm the author of an Emacs package that is in ELPA and that I don't
>> have any idea how many users it has - I mean, besides the ones that
>> I've interacted with - and I was planning to start my talk about it
>> in the next EmacsConf by saying that it has "at least 10 users"... =/
>
> Then again, if you go by download counts like MELPA, you will severely
> overestimate the number of users, since AFAIK they do not distinguish
> between downloads and updates, nor do they know if someone just
> installed a package and then immediately removed it.
I don't think that's important since we are not selling copies of the
software, nor trying to drive advertisement. Instead, what I had in mind
is a way of gauging activity. I'm thinking simply of the number of
installs and/or updates, even if that number is normalized to the most
"active" package.
A developer who wants insight could visit the ELPA page for their
package once in a while, note the change in the numbers, and draw their
own conclusions.
I think that seeing your package being installed and/or updated would be
a great way of encouraging people to continue developing. Developers,
especially of niche packages, could otherwise feel like they are "vox
clamantis in deserto"; shouting into a great empty wilderness.
> There was some discussion about updating the protocol that package.el
> uses, in which context thinking about some reliable yet privacy
> preserving method of estimating the user count would be nice to have.
I see no pressing reason to identify unique downloads as opposed to
simply downloads/updates, so I don't think privacy will be a concern.
Currently we have two developers who have voiced that they would like
this feature in ELPA. Perhaps if others chime in then it should be
considered.
--
"Cut your own wood and it will warm you twice"
next prev parent reply other threads:[~2023-07-14 14:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 20:54 Distribution statistics for ELPA and EMMS Yoni Rabkin
2023-07-13 23:16 ` Eduardo Ochs
2023-07-14 7:03 ` Philip Kaludercic
2023-07-14 14:02 ` Yoni Rabkin [this message]
2023-07-14 19:45 ` Adam Porter
2023-07-17 2:25 ` Richard Stallman
2023-09-19 14:49 ` Adam Porter
2023-09-19 16:38 ` Philip Kaludercic
2023-09-19 19:00 ` Akib Azmain Turja
2023-09-19 19:13 ` Emanuel Berg
2023-09-19 19:42 ` Yoni Rabkin
2023-09-19 22:06 ` Philip Kaludercic
2023-09-07 16:46 ` Stefan Kangas
2023-09-07 17:10 ` Yoni Rabkin
2023-09-07 21:35 ` Akib Azmain Turja
2023-09-07 22:07 ` Stefan Kangas
2023-09-07 23:09 ` Lynn Winebarger
2023-09-08 7:51 ` Philip Kaludercic
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=875y6mzj4n.fsf@rabkins.net \
--to=yoni@rabkins.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).