Skip to content

Mothballing and archiving the node-eps process #335

Closed

Description

@jasnell

@nodejs/tsc: For those who are not familiar with the term: mothballing == to stop using (a piece of equipment or a building) but keep it in good condition so that it can readily be used again.

Essentially, the nodejs/node-eps process has not been an overly successful process. The conversations there tend to get lost in the weeds, fail to progress, and attract trolling and bad behavior. The process of just setting up a working fork or working via a PR has been extremely successful in comparison (see URL, http2, n-api, node-chakracore, @bmeck's ESM PR, all for good examples).

The nodejs/node-eps approach never really got the love it needed from the TSC/CTC to be successful. I'm proposing that we archive the repo and no longer push it as a recommended process.

Activity

  1. Trott commented on Sep 7, 2017

    @Trott
    Member

    SGTM

  2. mcollina commented on Sep 7, 2017

    @mcollina
    SponsorMember

    SGTM

  3. MylesBorins commented on Sep 7, 2017

    @MylesBorins
    Contributor
  4. thefourtheye commented on Sep 7, 2017

    @thefourtheye
    Contributor

    SGTM

  5. mhdawson commented on Sep 8, 2017

    @mhdawson
    Member

    I wish we had an alternative but seeing how little love it has received SGTM for now.

  6. jasnell commented on Sep 12, 2017

    @jasnell
    MemberAuthor

    @nodejs/tsc ... we need more tsc members to weigh in.

  7. bnoordhuis commented on Sep 12, 2017

    @bnoordhuis
    Member

    One more SGTM for the collection.

  8. targos commented on Sep 12, 2017

    @targos
    Member

    SGTM

  9. evanlucas commented on Sep 12, 2017

    @evanlucas
    Contributor

    I like that idea

  10. Trott commented on Sep 12, 2017

    @Trott
    Member

    @nodejs/tsc ... we need more tsc members to weigh in.

    No one objected. 5 members besides you gave it the thumbs up. It was open for 5 days and TSC was @-notified immediately when the issue was opened.

    That's consensus. Someone who hasn't spoken up by now can be considered a "no objection" and/or "no opinion".

    (And now you have three more approvals! Four more if you include Joyee's thumbs up reaction.)

  11. jasnell commented on Sep 13, 2017

    @jasnell
    MemberAuthor

    Indeed, I'm happy to call it in favor of the proposal. It would just be helpful if all 22 TSC members would generally be more proactive about weighing in on such issues. As it is, assuming we're moving forward with this, I will open a PR against the nodejs/node-eps repo updating the README to say that it is archived and will open an issue there communicating the same.

  12. jasnell commented on Sep 13, 2017

    @jasnell
    MemberAuthor

    Closing as the issue appears to be resolved.

  13. Fishrock123 commented on Sep 20, 2017

    @Fishrock123
    Contributor

    ... I am not for this. I think it is useful and it should be used more.

  14. ofrobots commented on Sep 20, 2017

    @ofrobots
    Contributor

    I thought I had commented on this already. Here's post-closing +1 on this proposal.

  15. SamB commented on Jun 21, 2019

    @SamB

    Um ... shouldn't you have left a note about where to go instead at https://github.com/nodejs/node-eps#readme?

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions