Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

meta: decharter the Docs and Testing Working Groups #121

Merged
merged 1 commit into from
May 30, 2017

Conversation

jasnell
Copy link
Member

@jasnell jasnell commented May 10, 2017

The Documentation and Testing Working Groups are not active and have not been in some time. The existing teams may remain, but the associated nodejs/testing and nodejs/docs repositories should be archived, the charters revoked, and the responsibilities folded back into the CTC.

/cc @nodejs/ctc @nodejs/testing @nodejs/documentation

The Documentation and Testing Working Groups are not active and
have not been in some time. The existing teams may remain, but
the associated nodejs/testing and nodejs/docs repositories should
be archived, the charters revoked, and the responsibilities folded
back into the CTC.
@mcollina
Copy link
Member

👍

@eljefedelrodeodeljefe
Copy link

eljefedelrodeodeljefe commented May 10, 2017

Cross post:

Yes, please. I was writing what was needed (mandating and so on), apart from actual user activity. Both have not happened, despite resurrection tries. It's time...

Maybe someone will come around with a good idea, or stars in the core repo align desperate need of fundamentally better docs at some point.

Docs are generally working well at the moment even without the explicit WG.

@a0viedo
Copy link
Member

a0viedo commented May 11, 2017

👍 so all discussions involving the docs should take place under nodejs/node repository?

@jasnell
Copy link
Member Author

jasnell commented May 11, 2017

@nodejs/ctc members, this will need actual sign offs and not just thumbs up emojis :-)

cjihrig

This comment was marked as off-topic.

Trott

This comment was marked as off-topic.

@jasnell
Copy link
Member Author

jasnell commented May 12, 2017

@Trott .. yeah, I plan to. Wanted to make sure there was sufficient support first.

mhdawson

This comment was marked as off-topic.

@fhemberger
Copy link

A little bit off-topc, but still related: what about inactive translation groups? There are several without any activity for a while, so translated content may end up outdated (or even just plain wrong).

@Trott
Copy link
Member

Trott commented May 20, 2017

A little bit off-topc, but still related: what about inactive translation groups? There are several without any activity for a while, so translated content may end up outdated (or even just plain wrong).

@fhemberger I don't think any of those are chartered in the first place, so we can't decharter them. If you have ideas as to how we might address inactive internationalization teams, though, it's certainly worth discussing. Maybe @mikeal has some ideas. (Probably best to open another issue to discuss this.)

bnoordhuis

This comment was marked as off-topic.

@Trott
Copy link
Member

Trott commented May 20, 2017

@nodejs/ctc members, this will need actual sign offs and not just thumbs up emojis :-)

@jasnell I think you can proceed with landing this PR at this point, although maybe consider waiting 72 hours or so as I just pinged the groups in the relevant issues (nodejs/testing#54 and nodejs/docs#127). But that's up to you.

https://github.com/nodejs/CTC/blob/master/WORKING_GROUPS.md#nodejs-core-working-groups says that charter revocation can happen by consensus of the working group in question. So, if we have consensus on the part of WG members, we don't need a CTC vote.

For @nodejs/testing, between this PR and the issue mentioned above, you have 4 of the 6 folks on the WG expressing agreement (@santigimeno, @cjihrig, you, me). No one on the WG has expressed opposition. Consensus!

For @nodejs/documentation, between this PR and the issue mentioned above, you have 3 members of the WG expressing agreement (@eljefedelrodeodeljefe, @benjamingr, @a0viedo). Again, there is no opposition. Their governance doc does not mention a quorum (and I'm not sure that would be relevant anyway, as it is probably superseded by https://github.com/nodejs/CTC/blob/master/WORKING_GROUPS.md#nodejs-core-working-groups for this particular decision). Consensus!

Given all this, I'm going to remove the ctc-review label. Feel free to re-add it, of course, if you feel it's appropriate.

@Trott Trott removed the ctc-review label May 20, 2017
@jasnell
Copy link
Member Author

jasnell commented May 20, 2017

SGTM... I'll move forward with this on Monday

evanlucas

This comment was marked as off-topic.

Qard

This comment was marked as off-topic.

@jasnell
Copy link
Member Author

jasnell commented May 30, 2017

Given that there have been no objections, getting this landed.

@jasnell jasnell merged commit ed2a44c into nodejs:master May 30, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet