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

Summit topic: Deprecations future #153

Closed
BridgeAR opened this issue Mar 27, 2019 · 10 comments
Closed

Summit topic: Deprecations future #153

BridgeAR opened this issue Mar 27, 2019 · 10 comments

Comments

@BridgeAR
Copy link

So far our user experience was partially meh, when it comes to deprecation warnings. We often struggle with deprecations due to our very heterogeneous users. There is often a gap in the requirements for e.g., CLI users, big companies that want the most reliable and safe way doing things, individuals who e.g., write a small script and so on. Most important though: we mainly reach the wrong people when printing our deprecation warnings. In general there are lots of pros and cons with deprecations.

That's why I would like to brainstorm what we could do to:

  • reach the right people
  • improve the average experience for all users
  • still have a good way to improve the Node.js code base

So far I already thought about e.g., using a Node.js survey to gather further data and to figure out what our users actually believe and also about add an option to opt-into providing data when it comes to deprecations or other usage data.

This is very likely not an easy task and I ask not only Node.js collaborators to join but people who e.g., have run into deprecation warnings before, who found them distracting, great, weird and people who have e.g., strict requirements in companies. I believe we need a lot more feedback on this topic! If anyone has a lot of experience in this field, great, please join this session!

@BridgeAR
Copy link
Author

BridgeAR commented Apr 6, 2019

One thing I would like to also do in this session is going through all our current deprecations and determine if the deprecation really makes sense or not or if we want to remove the feature or not including a short risk summary by using https://gzemnid.nodejs.org.

One thing we might be more careful about in the future are non-underscore aliases, e.g., os.tmpDir(). Those are pretty cheap to maintain and removing them might not be worth it.

@mhdawson
Copy link
Member

+1 the key thing for me is what can we do to reach the right people without impacting end users.

@BridgeAR
Copy link
Author

@nodejs/package-maintenance this should likely be important to you and it would be great if people active in that working group could join this session :)

@ghinks
Copy link

ghinks commented Apr 19, 2019

Hello @BridgeAR indeed you are correct. It would be good to talk. I think you would like to hear what actually happens at some of the larger organizations at the summit. I'm going to reach out to a couple of people.

@BridgeAR
Copy link
Author

BridgeAR commented May 13, 2019

Here is a rough agenda: https://docs.google.com/document/d/1aBlgJRkvokGcALUCQqiUQ4SRcJ_ivHN0JhiI7u208Uc/edit?usp=sharing

Please add suggestions / comments in case anyone would like to add something or to be changed / reworded.

@jorydotcom
Copy link
Collaborator

Just documenting here that this topic has been added to the working agenda! Thank you!

@trivikr

This comment has been minimized.

@trivikr
Copy link
Contributor

trivikr commented May 30, 2019

Time: CEST Thu 30-May-2019 12:00 (12:00 PM)
Zoom link: https://zoom.us/j/381668642

@benjamingr
Copy link

benjamingr commented May 30, 2019

@bnb
Copy link
Member

bnb commented Jul 5, 2019

Going to close since this is for a past event 👍

@bnb bnb closed this as completed Jul 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants