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

Archiving modules repo and stoping team meetings #567

Open
qballer opened this issue Nov 4, 2020 · 1 comment
Open

Archiving modules repo and stoping team meetings #567

qballer opened this issue Nov 4, 2020 · 1 comment

Comments

@qballer
Copy link
Contributor

@qballer qballer commented Nov 4, 2020

In today's meeting (#565 ), @MylesBorins made a suggestion to discontinue team meetings and archiving this repo.
The main reasons discussed are as follows:

  • The team didn't create a charter for its self and most activities happen in https://github.com/nodejs/node upstream
  • We wouldn't like to create friction in landing PR's in nodejs
  • Most work that this team set out to do should be considered done and can be trusted with the general collaborator's community. Especially when the API is officially stable.

All attendees seemed to be on board with this notion and this issue is created to make sure all loose ends are being handled.

A few things to do before we conclude activities here are:

  • Make sure the nodejs bot can still ping members when PR's modify ESM implementation/docs.
  • We should tirage remaining open issues in this repo and migrate whatever is needed to node core.
  • Keep the team on github to make sure future discussion can still happen off issues if needed.
  • Perhaps set a final meeting to make sure issues are covered.

Feel free to raise any concerns or things I might have missed.

@qballer qballer pinned this issue Nov 7, 2020
@qballer qballer unpinned this issue Nov 7, 2020
@MylesBorins
Copy link
Member

@MylesBorins MylesBorins commented Nov 18, 2020

We only had 3 people show up to the meeting today. I think it is safe to say the Module meetings have run their course.

I've removed the recurring event from the Node.js calendar. Thanks for all the meetings y'all.

Let's work async to clean up the issues so we can archive the repo.

We definitely need to continue work on loaders but that will happen either Node.js core or in a new group that can be spun up.

Great work y'all.

MylesBorins added a commit to MylesBorins/TSC that referenced this issue Nov 18, 2020
After many years of work we are marking ESM in Node.js as stable
and sunsetting the Modules Team. Some high level next steps

* Mark modules as stable in core
* Review remaining open issues in nodejs/modules and close / transfer
* Simplify team structure and prune inactive team members

Refs: nodejs/node#35781
Refs: nodejs/modules#567
Refs: https://github.com/orgs/nodejs/teams/modules/discussions/8
mhdawson pushed a commit to nodejs/TSC that referenced this issue Nov 23, 2020
* strategic initiatives: mark modules as complete

After many years of work we are marking ESM in Node.js as stable
and sunsetting the Modules Team. Some high level next steps

* Mark modules as stable in core
* Review remaining open issues in nodejs/modules and close / transfer
* Simplify team structure and prune inactive team members

Refs: nodejs/node#35781
Refs: nodejs/modules#567
Refs: https://github.com/orgs/nodejs/teams/modules/discussions/8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.