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

Also report python version, collect supported from pypi, and report where appropriate #19

Open
yarikoptic opened this issue May 2, 2020 · 3 comments

Comments

@yarikoptic
Copy link
Collaborator

For user: it might be valuable to know that newer version drops support for the python he uses, and what would be the latest newer (if any) which supports user's python

For developers: would be useful to know % of users at this point in time who still uses the version they are considering to drop. Would have been very valuable e.g. in python 2 to 3 migration times.

@satra
Copy link
Contributor

satra commented May 2, 2020

i know that the access logs of the backend server encodes the CI info. i need to check if the CI info is stored in database. also i would want to restrict i think the amount of information going into the db, and what aspects of it are accessible/searchable. this will require a joint refactor of both client and server.

@satra
Copy link
Contributor

satra commented May 2, 2020

i meant to say the same mechanism we are using for CI can be used for other pieces. and since my intent was not to make scope of etelemetry service beyond our projects, we can craft some aspects specific to our needs.

@yarikoptic
Copy link
Collaborator Author

I thought that ultimately it was intended to be generic, thus not only for our projects - I don't think they are too special anyways to require some special treatments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants