RFC for package PopCon: a popularity contest for R and packages
I've developed a prototype package called PopCon (short for popularity
contest), a package for tracking the popularity of R and its packages.
I'd like this work to be similar in spirit to the Debian package
Once Popcon is loaded, it captures two kinds of information from the
user and stores it into a cache: the names of the libraries he/she
loads, and the names of symbols requested from his/her code. Once the
cache is full, the goal is to flush the data to a central server for
storage, free for anyone to download and analyze. That's it. Pretty
simple use and works behind the scenes. You can get the prototype here:
And note that flushing of the cache is NOT TURNED ON and IT WON'T
FORWARD ANY DATA ANYWHERE! It only gets deleted.
So, I envision all the software and data generated and stored to be
licensed under a GPL and a Creative Commons license, or even public domain.
Thoughts? I'm looking for volunteers, because there are many issues to
hash out. Here's a few of them:
1. Obviously storing IP addresses or any bit of personal information is
out, but I'm interested in generating a permanent random key of some
sort so that data from the same R installs can be tracked. I'm wondering
if just md5 hashing the combination of R version, platform, and IP
address would be appropriate and reproducible per R install. The debian
package popularity-contest has the benefit of installing an '/etc'
config file and generating the key once, while I'd like PopCon users to
just call 'library(PopCon)' and do nothing else.
2. I'm willing to maintain the central server and work on the
infrastructure, but help will definitely be needed. Also, if there's
significant interested, maybe R core would be interested in this.
3. What exactly is PopCon tracking as far as symbol names go? It
currently used an R_ObjectTable object attached to the search path to
capture names, but is this the best way? see
http://www.omegahat.org/RObjectTables/. It's also replacing
base::getHook to trap library loads.
4. What else would be interesting to track? Some folks have suggested
various bits of R.Version() output.