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

Advisory board relationship with leadership #2

Open
max-mapper opened this issue Nov 10, 2014 · 1 comment
Open

Advisory board relationship with leadership #2

max-mapper opened this issue Nov 10, 2014 · 1 comment

Comments

@max-mapper
Copy link

According to this charter version the purpose of the board is defined as to Provide guidance and input to leadership. It is also defined as not Intended to serve as an authoritative governance board. The Node.js Advisory Board advises, but does not manage the Node.js project core committers team leadership.

I'm curious if the 'leadership' that is alluded to here is defined anywhere in detail? e.g.:

  • Names of people in leadership
  • What powers the leadership have
  • What process the leadership uses to lead the project

etc

@junosuarez
Copy link

@maxogden thanks for asking these questions - I think they're highly relevant. Before getting bogged down in the makeup and implementation of this proposed advisory board, I think there is much more room for understanding the role and scope of the advisory board. Understanding the relationship to other project governance bodies is an essential part of that.

dshaw pushed a commit to dshaw/nodejs-advisory-board that referenced this issue Nov 15, 2014
conduct: add nationality and language to protected characteristics
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants