Skip to content
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

Anonymous usage statistics service #81

Closed
ctrueden opened this issue May 11, 2014 · 5 comments

Comments

Projects
None yet
2 participants
@ctrueden
Copy link
Member

commented May 11, 2014

We should create a service for monitoring anonymous usage statistics and submitting them to us. This would be optional of course, with the user being prompted at the beginning whether to allow it.

These statistics would be very useful to see which features people are actually using, to prioritize improvements.

Migrated-From: http://trac.imagej.net/ticket/750

@ctrueden ctrueden added this to the 2.0.0 milestone May 11, 2014

@ctrueden

This comment has been minimized.

Copy link
Member Author

commented May 11, 2014

I've tentatively added this to the 2.0.0 milestone, because it would be insanely great to start collecting such information ASAP. It won't tell us what people need, but it will at least tell us what people use.

Technically, we could just record module identifier strings when they are executed, and aggregate them into a discrete histogram. The UsageService (StatisticsService is already taken in ImageJ) could live in SciJava Common, although the prompt asking users whether to enable it would be part of ImageJ and any other SciJava application that wishes to enable it.

@ctrueden

This comment has been minimized.

Copy link
Member Author

commented Jul 17, 2014

I've started some branches: https://github.com/scijava/scijava-common/compare/usage-statistics, https://github.com/imagej/imagej-updater/compare/usage-statistics

But I think the imagej-updater work will get split out into a new imagej-usage component, which depends on imagej-updater and is added to imagej as a new dependency. This is because the usage stuff will depend on org.json:json which the updater otherwise doesn't need. And the updater is also a rather finicky component—best not to have anything in there that isn't needed to update/recover the ImageJ installation.

@dscho

This comment has been minimized.

Copy link
Member

commented Jul 18, 2014

Good thinking about avoiding dependencies to make it easier to reuse imagej-updater.jar in bootstrap.js!

@ctrueden

This comment has been minimized.

Copy link
Member Author

commented Jul 18, 2014

Three branches now:

Initial skeleton for upload of JSON data is in place. Still lots and lots to implement.

@ctrueden

This comment has been minimized.

Copy link
Member Author

commented Aug 12, 2014

@ctrueden ctrueden closed this Aug 12, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.