Decharter Intl WG

Question

Decharter Intl WG

jasnell opened this issue 7 years ago · 16 comments

I would like to propose dechartering the Intl WG in favor of it being a more informal Team. I'm not convinced that we ever really had much benefit of it being a formally chartered working group. A team would still be just as effective without having any of the additional overhead of a chartered working group.

ping @srl295

Answer 1 · 2017-10-11T11:47:12.000Z

ping @srl295

Answer 2 · 2017-10-11T13:25:25.000Z

@srl295 unless you object I'd agree that Intl could be a team.

Answer 3 · 2017-10-16T23:17:20.000Z

sure— sounds OK off the top of my head (and I'll go change my slides…)

Answer 4 · 2017-10-16T23:24:56.000Z

^ I could not find a lot of details on team vs. WG. I filed the above issue nodejs/Intl#45 over any changes that should happen to the Intl repo. In particular, does the Intl repo need to close, because there are some valuable issues there— but, they could move to issues in other repos but with appropriate tags.

Answer 5 · 2017-10-16T23:33:28.000Z

@srl295 Team = GitHub team, so @nodejs/intl would be the team. Yeah, not a lot of documentation on how that differs from a chartered WG. We could definitely improve there. The repo does not need to close. (Testing WG was de-chartered but the repo remains, for example.)

Answer 6 · 2017-11-01T20:43:21.000Z

What's the next step here?

Answer 7 · 2017-12-11T16:47:13.000Z

Ping @nodejs/tsc

Answer 8 · 2017-12-11T21:47:51.000Z

Ping @nodejs/tsc

nodejs/nodejs.org#1513
#437

Answer 9 · 2017-12-11T21:53:54.000Z

Going through remaining open issues in https://github.com/nodejs/Intl/issues right now. Planning on archiving the repo (basically making it read-only) sooner or later.

Answer 10 · 2017-12-11T21:55:40.000Z

@srl295 earlier discussion was that the repo did not necessarily need to close if the WG became a team. Is the repo still useful for the team ?

Answer 11 · 2017-12-11T21:59:13.000Z

@mhdawson @srl295 OK, I won't archive the repo for now and I'll stop my march through all the issues to close them that I started a few minutes ago. It does seem that the Intl repo is a bit of a graveyard though. I think the issues in that repo would probably get more activity/visibility elsewhere.

Answer 12 · 2018-02-17T00:37:50.000Z

The discussion appears to have stalled. What is the next step here?

Answer 13 · 2018-02-17T02:37:03.000Z

@jasnell did it? What's left to do? I have a PR nodejs/Intl#47 to redirect to i18n, and I'm going to go over the rest of the Intl issues and refile…

Answer 14 · 2018-02-17T15:36:00.000Z

The conversation in this thread did at least :-) Since there is actively happening elsewhere in the org, does this specific issue need to stay open?

Answer 15 · 2018-02-17T17:34:54.000Z

Aha. #353 can close

Answer 16 · 2018-02-18T21:07:06.000Z

Thanks @srl295, I'll close this.