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

Collect usage statistics #1359

Closed
tobiasdiez opened this issue May 6, 2016 · 7 comments
Closed

Collect usage statistics #1359

tobiasdiez opened this issue May 6, 2016 · 7 comments

Comments

@tobiasdiez
Copy link
Member

tobiasdiez commented May 6, 2016

Automatically (and of course anonymously) collect usage statistics, for example about:

  • changed preferences (to determine better default values)
  • number of open databases, size of db, ...
  • used functionality (to extract main use cases)

Maybe also occasionally ask questions about the way users use JabRef and/or what they want (a lite version of the recent survey).

Of course, the should have to option to opt out of this data collecting.

@simonharrer
Copy link
Contributor

We could leverage Google Analytics for this which allows to send arbitrary events to the cloud for analysis.

@tobiasdiez
Copy link
Member Author

In this case, we may use https://github.com/siddii/jgoogleanalytics or some related project.

@Siedlerchr
Copy link
Member

As an alternative we could use Piwik:
https://github.com/piwik/piwik-java-tracker
It can be self-hosted and would be a bit more user-privacy-friendly

@simonharrer
Copy link
Contributor

I do not like this self-hosted stuff, as it draws developer resources away from the more important things - improving JabRef :)

@tobiasdiez
Copy link
Member Author

Decision from devcall: use google.

@Siedlerchr
Copy link
Member

Google analytics no longer works. There is no actual version which can be used.

tobiasdiez added a commit that referenced this issue Apr 6, 2017
* First draft of telemetry

* Add preferences to disable telemetry collection

* Specify instrumentation key in environment variable

* Track all dialogs

* Add dialog to ask user if he wants to share his data with us

* Improve dialog text

* Adapt text
Siedlerchr added a commit that referenced this issue Apr 6, 2017
* upstream/master:
  Implement #1359: collect telemetry (#2283)
  Write groups under tag `group` instead of `groupstree` to enhance compatibility with previous versions (#2704)
  Avoid conversion of single underscores (#2711)
  Fix #628: implement hierarchical keywords (#2703)
@lenhard
Copy link
Member

lenhard commented Apr 7, 2017

This can be closed as it has been implemented in #2283 with Microsoft Azure.

@lenhard lenhard closed this as completed Apr 7, 2017
Siedlerchr added a commit that referenced this issue Apr 13, 2017
* upstream/master: (39 commits)
  Fix fetcher test
  Allow failures for fetcher test (#2730)
  Use JabRefExecutor service
  Move DOI fetching to separate thread #2682
  Remove gui dependency in logic (#2726)
  Fixed freeze on Mac OS X when creating/editing groups (#2727)
  Only ask once if telemetry data should be collected
  Update wiremock from 2.5.1 to 2.6.0
  Update mockito-core from 2.7.21 to 2.7.22
  Update log4j to latest version
  Azure test (#2724)
  Fix build
  Move expand filename to FileUtil
  Unicode conversion bibtexkey (#2720)
  Add sorting of all groups and subgroups, recursively (#2666)
  Only check capitalization of note and howpublished fields if they start with a word character
  Remove overhauled @author tag
  Implement #1359: collect telemetry (#2283)
  Add licenses of new dependencies
  Fix cssStyleHelper warnings
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants