all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Adam Porter <adam@alphapapa.net>
To: yoni@rabkins.net
Cc: emacs-devel@gnu.org
Subject: Re: Distribution statistics for ELPA and EMMS
Date: Fri, 14 Jul 2023 14:45:04 -0500	[thread overview]
Message-ID: <2f28dcca-3f8b-eb7b-95ec-1867c0d1eaf4@alphapapa.net> (raw)
In-Reply-To: <875y6mzj4n.fsf@rabkins.net>

> Currently we have two developers who have voiced that they would 
> likethis feature in ELPA. Perhaps if others chime in then it should
> be considered.

Obviously, I think every developer would like to see the download counts 
of their packages.  I check mine on MELPA now and then to get a sense of 
how popular they are, at least relative to each other.  If nothing else 
it gives me an idea about how I may need to better document or publicize 
them (the ones that seem under-utilized, that is).  And, of course, it 
can be a nice ego boost.  :)

So, yes, it would be nice if ELPA offered something similar.  Nothing 
fancy, just a download counter, would be good.  Even better would be a 
page showing downloads per month, or something like that, for historical 
purposes.

However, another factor to keep in mind is that some packages may be 
downloaded regularly for continuous integration testing, which may 
inflate the download count.  One might think that this would only be a 
small number, and I guess for most packages it is, but I have seen on 
some of mine, which seem to be included in some distros with regular CI, 
that the Git repo is cloned hundreds or thousands of times per week, 
numbers far beyond the users of the package.  Maybe that pattern is 
confined to cloning the Git repo rather than downloading from ELPA, but 
I can't say.

As far as uniqueness, I would, of course, suggest that IP addresses 
should be protected.  Maybe some simple aggregation in the sense of 
collating multiple downloads from one address in a short period of time 
could be useful, but anything beyond that would seem bogus.

My two cents.  :)



  reply	other threads:[~2023-07-14 19:45 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
2023-07-14 19:45       ` Adam Porter [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2f28dcca-3f8b-eb7b-95ec-1867c0d1eaf4@alphapapa.net \
    --to=adam@alphapapa.net \
    --cc=emacs-devel@gnu.org \
    --cc=yoni@rabkins.net \
    /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.