> The resignations followed a single event -- a vote that failed to remove a former director, a longstanding member of the community, from the leadership group.
This post (without taking sides, I haven't even read his post yet) is that individual's defence of himself, which doesn't appear to be linked from this post:
"Some time ago I received notification via email that there are complaints against me. No details were provided and I was informed that I would neither receive those details or be involved in the whatever process was to take place. Further, TSC members were not allowed to speak to me directly about these matters, including my work colleagues also on the TSC."
The canonical source [1] on the Node side seems to have been fully redacted at this time, so here's the post in the community forum where people are discussing the issue [2].
Once again not taking sides (although this article seems to have dropped off the homepage).
The fact that we can't get any answer on this beyond Vagg's side is frustrating. From reading his side, it all seems incredibly minor stuff that would in no way need to end with a leadership change.
Can someone in the Node.js community enumerate the complaints fully, here or in some public place?
Can someone explain what happened? The article did a very poor job at it (or, at least, I didn't understand it), as it seemed to contradict itself or not shed enough light on things.
What did Vagg actually do? Why did other members leave?
The list of complaints seems to have been removed from the vote issue [1] on his removal 'at the request of several core collaborators who felt that listing the issues was not fair to Rod'.
He lists the issues himself in his response post [2] (see 'Response to the list of complaints'), where he also states 'Please note that I did not ask for this text to be redacted.' (although it's unclear whether he refers to the redaction of certain links in the list as copied in his post, or the whole list on nodejs/TSC#310).
So [1] seems to be the authoritative source on the Node side, [2] the authoritative source on the opposite side.
Disclaimer again, I'm not taking sides, I haven't read everything yet, I'm just gathering links for people to draw their own conclusions.
It is hard to find out what happened because it is more mundane than the titillation of vague code of conduct allegations and requires a little digging and neither of these make for good web stories.
The gist of it is that back in March the Nodejs board realized it was in non-compliance with its by-laws. The by-laws limit board membership to one employee per employer unless that company is a Platinum sponsor. Vagg and another board member were(are?) employed by the same company and that company was(is?) not a Platinum sponsor. Legal council had confirmed the opinion that this was in non-compliance with the bylaws.
The community did not appear to support changing the by-laws to allow the two members to continue to serve. Vagg's response in the linked discussion did not suggest any sort of path toward solving the problem.
--- Speculation follows
The by-laws did not provide a mechanism for handling this situation. Neither of the two employees resigned. The company did not become a Platinum sponsor. The board continued to be in non-compliance.
---Discussion
A person could make a plausible case that continued presence on the board that causes non-compliance is not an acting good faith and is therefore a possible code of conduct violation at the level of a board member. It is hard for an argument that non-compliance with the bylaws is acceptable to gain traction.
[OK, a bit more speculation] The Node Foundation's statement regarding removal is more likely to be related to by-law non-compliance than the code of conduct. Non-compliance with the by-laws is the level at which the Foundation is appropriately involved. Based on the archived discussion, the need to change the Board membership has been known for nearly six months. The failed vote to remove a member and neither conflicting member resigning means that the board is unable to resolve the problem on its own.
[+] [-] tekacs|8 years ago|reply
This post (without taking sides, I haven't even read his post yet) is that individual's defence of himself, which doesn't appear to be linked from this post:
https://medium.com/@rvagg/the-truth-about-rod-vagg-f063f6a53...
[+] [-] bitL|8 years ago|reply
"Some time ago I received notification via email that there are complaints against me. No details were provided and I was informed that I would neither receive those details or be involved in the whatever process was to take place. Further, TSC members were not allowed to speak to me directly about these matters, including my work colleagues also on the TSC."
[+] [-] tekacs|8 years ago|reply
Once again not taking sides (although this article seems to have dropped off the homepage).
[1]: https://github.com/nodejs/TSC/issues/310
[2]: https://github.com/nodejs/community-committee/issues/111
[+] [-] adjkant|8 years ago|reply
The fact that we can't get any answer on this beyond Vagg's side is frustrating. From reading his side, it all seems incredibly minor stuff that would in no way need to end with a leadership change.
Can someone in the Node.js community enumerate the complaints fully, here or in some public place?
[+] [-] falcolas|8 years ago|reply
[+] [-] defkev|8 years ago|reply
[deleted]
[+] [-] StavrosK|8 years ago|reply
What did Vagg actually do? Why did other members leave?
[+] [-] tekacs|8 years ago|reply
He lists the issues himself in his response post [2] (see 'Response to the list of complaints'), where he also states 'Please note that I did not ask for this text to be redacted.' (although it's unclear whether he refers to the redaction of certain links in the list as copied in his post, or the whole list on nodejs/TSC#310).
So [1] seems to be the authoritative source on the Node side, [2] the authoritative source on the opposite side.
Disclaimer again, I'm not taking sides, I haven't read everything yet, I'm just gathering links for people to draw their own conclusions.
[1]: https://github.com/nodejs/TSC/issues/310
[2]: https://medium.com/@rvagg/the-truth-about-rod-vagg-f063f6a53...
[+] [-] brudgers|8 years ago|reply
The background context can be read here, https://web.archive.org/web/20170821222518/https://github.co...
The gist of it is that back in March the Nodejs board realized it was in non-compliance with its by-laws. The by-laws limit board membership to one employee per employer unless that company is a Platinum sponsor. Vagg and another board member were(are?) employed by the same company and that company was(is?) not a Platinum sponsor. Legal council had confirmed the opinion that this was in non-compliance with the bylaws.
The community did not appear to support changing the by-laws to allow the two members to continue to serve. Vagg's response in the linked discussion did not suggest any sort of path toward solving the problem.
--- Speculation follows
The by-laws did not provide a mechanism for handling this situation. Neither of the two employees resigned. The company did not become a Platinum sponsor. The board continued to be in non-compliance.
---Discussion
A person could make a plausible case that continued presence on the board that causes non-compliance is not an acting good faith and is therefore a possible code of conduct violation at the level of a board member. It is hard for an argument that non-compliance with the bylaws is acceptable to gain traction.
[OK, a bit more speculation] The Node Foundation's statement regarding removal is more likely to be related to by-law non-compliance than the code of conduct. Non-compliance with the by-laws is the level at which the Foundation is appropriately involved. Based on the archived discussion, the need to change the Board membership has been known for nearly six months. The failed vote to remove a member and neither conflicting member resigning means that the board is unable to resolve the problem on its own.
[+] [-] fgjjgutjvnu|8 years ago|reply
[+] [-] k__|8 years ago|reply
I mean this seems like a campaign to crush the node leadership, someone wants to get power over node, but who?
[+] [-] _Marak_|8 years ago|reply
[+] [-] fgjjgutjvnu|8 years ago|reply
[deleted]
[+] [-] exikyut|8 years ago|reply
Also, are there backup(s) anywhere for the "Many [...] complaints, since removed from the committee's pages"?
[+] [-] unknown|8 years ago|reply
[deleted]
[+] [-] unknown|8 years ago|reply
[deleted]
[+] [-] fgjjgutjvnu|8 years ago|reply
[deleted]
[+] [-] bitL|8 years ago|reply