Skip to content

Summit topic: Deprecations future #153

Closed

Description

@BridgeAR

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!

Activity

  1. BridgeAR commented on Apr 6, 2019

    @BridgeAR
    Author

    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.

  2. mhdawson commented on Apr 11, 2019

    @mhdawson
    Member

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

  3. BridgeAR commented on Apr 19, 2019

    @BridgeAR
    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 :)

  4. ghinks commented on Apr 19, 2019

    @ghinks

    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.

  5. BridgeAR commented on May 13, 2019

    @BridgeAR
    Author

    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.

  6. jorydotcom commented on May 15, 2019

    @jorydotcom
    Collaborator

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

  7. trivikr commented on May 30, 2019

    @trivikr
  8. trivikr commented on May 30, 2019

    @trivikr
    Contributor

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

  9. bnb commented on Jul 5, 2019

    @bnb
    Member

    Going to close since this is for a past event 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions