You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It was never discussed with me (a core member who intends to make significant contributions and maintain the Node.js loader implementation) whether or not this should be a working group or a team. As you can see in the calendar that I made, my intention was to make it an official working group, so I am unsure why this was made into a team.
EDIT: After looking at the repo a bit more, it has become clear to me that it is still very much a WIP.
I assume everything is still up for debate as the members of this team/group are still not listed…
The text was updated successfully, but these errors were encountered:
This repo was set up as a fork of the Modules one, and Modules is just a team (not a Working Group). That's the only reason; there was no discussion.
The Modules team at one point discussed becoming a Working Group but decided against it. WGs have more obligations. We could become one if we want to, but I think there's no rush. I don't think there's anything we want to do that we can't do as our current status.
It was never discussed with me (a core member who intends to make significant contributions and maintain the Node.js loader implementation) whether or not this should be a working group or a team. As you can see in the calendar that I made, my intention was to make it an official working group, so I am unsure why this was made into a team.
EDIT: After looking at the repo a bit more, it has become clear to me that it is still very much a WIP.
I assume everything is still up for debate as the members of this team/group are still not listed…
The text was updated successfully, but these errors were encountered: