You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We as TUfast want to understand our users better and improve (increase) open-source contribution. To do that, we need to collect and analyse anonymous user data. This helps us to see what parts of the extension are most and least used, as well as if advertisement banners (inviting users to participate at the project) are working.
We want to display our collected statistics on the tu-fast website to make them available to all our users and the general public.
This goal requires changes in three repositories:
This one (TUFastData)
TUfast_TUD
TUfast_website
The changes required in TUfastData are listed in this issue.
We start by implementing the following API-Endpoints:
An API endpoint that accepts a number of clicks and increases a global click counter by that amount (tracking of total time saved by users)
An API endpoint that accepts a boolean array to track which features are used by users and which not
An API endpoint that tracks the number of clicks onto our "hiring" banner link to track how many students are interested in joining our team
These API routes should be called a specific number of times per day/week which will be detailed in the corresponding issue in TUfast_TUD.
The text was updated successfully, but these errors were encountered:
We as TUfast want to understand our users better and improve (increase) open-source contribution. To do that, we need to collect and analyse anonymous user data. This helps us to see what parts of the extension are most and least used, as well as if advertisement banners (inviting users to participate at the project) are working.
We want to display our collected statistics on the tu-fast website to make them available to all our users and the general public.
This goal requires changes in three repositories:
The changes required in TUfastData are listed in this issue.
We start by implementing the following API-Endpoints:
These API routes should be called a specific number of times per day/week which will be detailed in the corresponding issue in TUfast_TUD.
The text was updated successfully, but these errors were encountered: