-
Notifications
You must be signed in to change notification settings - Fork 59
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
Comments
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., |
+1 the key thing for me is what can we do to reach the right people without impacting end users. |
@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 :) |
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. |
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. |
Just documenting here that this topic has been added to the working agenda! Thank you! |
This comment has been minimized.
This comment has been minimized.
Time: CEST Thu 30-May-2019 12:00 (12:00 PM) |
Going to close since this is for a past event 👍 |
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:
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!
The text was updated successfully, but these errors were encountered: