-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
make --skip-newsletter the default #779
Comments
I understand that this is a bit weird, but let me explain:
Because, for some reason, people don't subscribe to the release announcements although we hint at them on the website and in the README, we decided to make it really obvious that this is important, hence adding it to Making this flag work the opposite way would be in stark contrast what we want to achieve with raising awareness for the release announcements. I'm open to better ideas here, but for the time being, I think it will stay as it is. |
hm i understand the reasoning on why you want people to subscribe, but its also kind of weird at the same time. a notice, thats annoyingly posted in blink red/green for a couple seconds to users might still be an option, but that might also alienate people, unless you add some flying unicorns! so ok, i get it :) |
Cool, so I think that - apparently - we can do a better job at explaining why this is important. What would have helped for you to understand that when seeing it in the CLI? Adding some explanation? |
yes actually having a note on why this newsletter is so important for everyone and why you care so much (meaning you don't wanna sell anything but simply tell them about security updates) would probably make a lot of difference |
That makes sense, what do you think about:
|
great! |
Cool, I'll add that to the CLI in the next release - thank you for your feedback! |
At least to me it is quite weird to have a cli ask for a newsletter. Is this really the way to treat users to do that by default, especially if --id and --secret are used (which is incredibly helpful for tests, setting up testusers etc)
The text was updated successfully, but these errors were encountered: