-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking download statistics #27
Comments
Thank you for this info, Damian. There exists one (very limited) view into Github repo clones and page visitors: https://github.com/Fortran-FOSS-Programmers/FOODIE/graphs/traffic Unfortunately, it gives you the number of clones and unique cloners only for past 2 weeks. I never found a way to see beyond past 2 weeks, but I suspect that data may be stored for all visits and clones since birth of a repository. Accessing this information? I don't know. There is an answer on this Stack Overflow post about how to incorporate Google Analytics into README.md to track page views - which is not quite what we are after, but better than nothing. http://stackoverflow.com/questions/10056638/how-to-get-github-clone-stats |
Sent from my iPhone
Thanks for that. I haven't checked the link yet, but I think it's a great to have traffic information that is accumulated for more than two weeks. Capturing README page views could be a good indicator of overall interest in the software.
|
Hi @rouson @milancurcic @zbeekman and All, thank you for the interesting talk of yesterday! I will take care about of your suggestions/critics I hope in the next week. Here, just some thoughts about funding research. Unfortunately, I am not allowed to attend at any interesting conferences in numerical/HPC/scientific-software or similar topics: my research Institute (CNR-INSEAN) is under strong economic crisis (as well as Italy and Europe in general from 2008), so I can attend to only 1 conference per year strictly related to Naval or Maritime topics. However, it would be very welcome if you consider worth to present this work to a conference. In the case you think it is worth to present our work, I can help for doing presentation materials (slides, tests, examples, screencasts...) for you. For the founding research I think my help is very small. I can help with some low level work... So, assuming that we can favorite the OpenCoarrays and FOODIE installations by means of distros repositories, I am thinking to something like the following to gathering statistics:
I am not sure this is feasible before I try to do, but I am optimistic on that. What do you think? See you soon. |
These all sound like good ideas. I look forward to hearing what you find out as you work out the solutions. Damian
|
@rouson and all, See you soon. |
Thanks for investigating this. D |
I just want to add two resources I found:
|
Same as above. If you’d like to add this to the OpenCoarrays README too, please do. If so, please clone the OpenCoarrays repository and submit a pull request. Either Alessandro or I will review and accept the request and I’ll add you to the contributors list on opencooarrays.org. Damian |
Thank you Zaak, your help is always valuable! I have tried Bitdeli in the past (maybe 1 year later). but it always had some problems... If I remember correctly it was due to some GitHub API changes. I completely forget the Homebrew installs! Feel free to add an Homebrew formula, your help is very very appreciated, I am a poor Arch Linux user... never coming close to a shining Mac :-) Let me know how can help you for making FOODIE homebrew-enabled. P.S. to all: I am quite busy these days, I am sorry for my silence... I am trying to complete a disaster recovery... the data on a cluster and on my own backup blown up subsequently in few weeks, sigh! I am trying to play with ddrescue & Co., any suggestions are welcome :-( |
@szaghi I will try to write & submit a formula for FOODIE. Before I do that, however, I need to update FoBiS.py and FORD formula, and write an opencoarrays formula. I hope I'll get to FOODIE next week. |
@zbeekman Take your time, this does not matter. Thank you very much for your help! |
One thing I think is very important when going after funding is having data on the usage and impact of the software. This could take several forms:
Item 1 above is something the most challenging and is the subject of the remainder of this post.
One is that we post our own tar ball with releases, e.g., see "opencoarrays-1.1.1.tar.gz" at https://github.com/sourceryinstitute/opencoarrays/releases/tag/1.1.1. Then we use the following external tool to track downloads of the aforementioned tar ball: http://www.somsubhra.com/github-release-stats/. Enter "sourceryinstitute" and "opencoarrays" into the two fields on the latter page. Sadly even this only provides incomplete data because if someone downloads either of the tar balls that GitHub automatically posts to the aforementioned URL, we get no information on those tar balls. I've even thought about renaming the tar ball "download-this-one.tar.gz" or something similar. Very frustrating.
To help make installation easier for users, I also asked Alessandro to develop a Portfile that enables installation via MacPorts package management software on OS X. That Portfile now exists, but it turns out that MacPorts will only report downloads if the user also installs the mpstats port. Arrggghh. We ask people to do so, but we have no control over it and the corresponding web page shows only one download: http://stats.macports.neverpanic.de/categories/38/ports/25626#installs_over_time, which I'm almost certain is wrong. Our tar ball has been downloaded from GitHub over 275 times. It doesn't seem believable to me that the MacPorts installations would be less than more than 100 times smaller than the tar ball downloads now that we mention MacPorts prominently in our installation instructions.
I hope people can push on the maintainers of GitHub to do a better job with tracking such data, but at least it's good the we have something. That's better than nothing, which is what BitBucket offers.
Also, I have a web developer investigating whether we can use Google Analytics to track clicks on the link to the OpenCoarrays release tar ball from the main page on www.opencoarrays.org, but I don't have an answer on that yet either. I'm really amazed at how difficult it can be to get data that I would think would be easily accessible. Nonetheless, I believe strongly it's worth the effort.
The text was updated successfully, but these errors were encountered: