Add: telemetry policy to scope page #192
Conversation
about/package-scope.md
Outdated
|
|
||
| ### Telemetry & user-informed consent | ||
|
|
||
| Your package should avoid collecting usage analytics. With |
There was a problem hiding this comment.
from @choldgraf @NickleDave maybe something like this instead for the first sentence?
Your package must avoid collecting usage analytics without informing people using it.
| @@ -195,6 +195,27 @@ Packages to aid with instruction. | |||
|
|
|||
| ## Package technical scope | |||
|
|
|||
|
|
|||
There was a problem hiding this comment.
from @tupui
I think we should do something similar, provide a template basically and tell how/where the info should be presented to the users
leah: i really LOVE this idea of pyos having a badge on its package listing so users know what is being collected IF ANYTHING? that way we are super clear about that in our catalog so it's a value added element. We can also ask maintainers to add a badge / template to their README file and some standard language in there as well.
|
Ok - we haven't had any more feedback on this pr in a while. i'm going to go ahead and merge it as is. IF we need to modify the language at any time we can. but it's been sitting for several months now. |
Telemetry is an important part of our scope policy. It sets the stage to our ethical stances on collecting data about how users use packages and also what platforms they are on.
On one hand it is incredibly valuable to developers.
On the other, users need to KNOW what is being collected, and what is done with that data (their data).
This sets the stage for such policy.
Also being discussed here