Closed crasskitty closed 4 years ago
@vgrichina recently removed the near-shell tracking opt-in on Gitpod, since there was no way to prevent it from opening every time you restart a workspace, which happens all the time in a Gitpod workflow. Additionally, if you're using a web-based IDE, you probably expect everything you do to be tracked already.
I'm curious where this new requirement is coming from, and how we plan to fix the usability issues that we ran into last time.
Engineering Time:
Back up:
Linking to the examples of how we are using this data
Cross posting this to NEAR/NEAR-wallet on Github cc: @kcole16
I spent about 1/2 hour looking through the docs linked above, and haven't seen anything that would let us save the opt-in/out info between gitpod sessions. Do we want to spend more time on this, or go with the fallback?
@janedegtiareva Let's go with the fallback -- any protest @potatodepaulo ?
We need text to put into the README.
"By using Gitpod in this project, you agree to opt-in to basic, anonymous analytics. No personal information is transmitted. Instead, these usage statistics aid in discovering potential bugs and user flow information."
I think we can add this to near-shell
and all the examples at https://near.dev
For the repos with a README-Gitpod.md
file, it can go in there. For those that don't have it, the regular README.md
file will do
"By using Gitpod in this project, you agree to opt-in to basic, anonymous analytics. No personal information is transmitted. Instead, these usage statistics aid in discovering potential bugs and user flow information."
I think we can add this to
near-shell
and all the examples at https://near.dev For the repos with aREADME-Gitpod.md
file, it can go in there. For those that don't have it, the regularREADME.md
file will do
Thank you! I can put this into readmes.
As a developer on the NEAR platform, I want to be informed, aware, and have the option to refuse or consent to my data being monitored anytime I interact with:
So that I have the ability to make an informed decision on if I want to give my data to NEAR.