Archiving modules repo and stopping team meetings

[qballer]

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.

[MylesBorins]

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.