nodejs / board

The Node Foundation Board of Directors

Board of Directors

The Node.js Foundation is a member based organization. There are 5 classes of Membership: Platinum, Gold, and Silver Members, Associated Entity Members and Individual Members.

A list of non-Individual members and additional information is available on the website: https://nodejs.org/en/foundation/members/

Individual Members

Individual Members of the Node.js Foundation have the ability to both run and vote for representation on the Board of Directors.

Representation on the Board of Directors

The Individual Members are represented on the Board of Directors an Individual Director. A representative is elected in January every two years with no limitations to the number of terms served.

Current Individual Directors

TBD

Previous Individual Directors

• Feross Aboukhadijeh @feross • Jan 2016 - Jan 2017.
• Ashley Williams @ashleygwilliams • Jan 2016 - Jun 2018.
• William Kapke @williamkapke • Jan 2017 - Mar 2019.

Registration and Cost

Anyone with a GitHub account may become an Individual Member. Visit https://identity.linuxfoundation.org/pid/99 to register.

The cost of Individual Membership is:

• Node.js Project Contributors: free*
• Students: $25/yr
• General Population: $100/yr

^{* links to a Private repo that is only accessible to GitHub users who are on the Members team of the nodejs GitHub organization. Users are added to the team (by Collaborators) when they contribute consistently to a Node.js Foundation project.}

Questions? Comments?

Please file an issue.

board's Issues

Q&A w/ @wprl on Individual Membership Candidacy

This thread is for asking @wprl questions regarding his run for the Node.js Foundation Board of Directors.

README outdated

The README.md links to last year's blog post... which then links to #12 (Nominations for the 2016 election)

Q&A w/ @jaredhanson on Individual Membership Candidacy

This thread is for asking @jaredhanson questions regarding his run
for the Node.js Foundation Board of Directors.

2017 Node.js Foundation Individual Membership Director ballot now open

Ballot now open for voting through January 30 at 17:00 UTC.

The Node.js Foundation is a member-supported organization. The Node.js Foundation Individual Director is the Node.js project’s community voice on the board. There are two individual directors that sit on the Node.js Foundation board and they serve a two-year term.

The Individual Membership Director is responsible for soliciting feedback and data that represents the wishes of other individual members and the community at large. They have been entrusted with the duty to make decisions based on the information they receive to best represent the community, and can gather input for proposals when relevant and granted permission to do so.

This includes participating and voting in Board meetings, introducing and driving forward initiatives to conclusion that capture the mission of the Node.js project, and representing the Board at speaking engagements (this is by no means a comprehensive list). Read more about “What’s it like being on the
Node.js Foundation Board of Directors?”.

What does the Board of Directors do?

The Board meets every month to approve resolutions and discuss Node.js Foundation administrative matters. This includes legal considerations, budgeting and approving Foundation-led conferences and other initiatives. Technical governance is overseen by the TSC, not the Board of Directors.

The current board members are listed here.

Who is running for the Individual Membership Director seat?

Read more about why our candidates are running below.

• William Kapke @williamkapke
  • I'm running for the Node.js Board of Directors!
• Kat Marchán @zkat
  • Director nomination for Kat Marchán
• Charlie Robbins @indexzero
  • I'm running to increase transparency to the community from the Node.js Board
    of Directors
• William P. Riley-Land @wprl
  • I Would Like to Represent Individual Members of the Node.js Foundation

When is the election? Nominations were solicited until January 15th.

• Ballot will be distributed on January 20th.
• The election will close January 30th at 17:00 UTC.

How do I vote?

You must be an Individual Member of the Node.js Foundation to cast a vote. If
you are a member, you can vote NOW!

How do I become a member?

Individual membership costs $100 a year, or $25 for students.

Contributors to the Node.js project, including all Working Groups and
sub-projects, are eligible for free membership. Please
contact us for discount codes. You are
required to have a GitHub account to register.

What’s the benefit of being an individual member?

• You have a vote and voice on the Node.js Foundation Board of Directors
  through the two above-mentioned elected Individual Membership Directors.
• 20% off regular price registration to Node Interactive 2017

See you at the (digital)poll?

cc @nodejs/tsc @nodejs/ctc @nodejs/evangelism

Q&A w/ @guyellis on Individual Membership Candidacy

This thread is for asking @guyellis questions regarding his run for the Node.js Foundation Board of Directors.

Link to Node.JS Project Contributors Membership is 404

Node.JS Project Contributors (any member of the GitHub Org): free

https://github.com/nodejs/members/issues/1 looks like it no longer exists or is private. What is the process for contributors to register now?

Thanks!

List of members?

Is there a list of people that are members?
Maybe just a running total of how many members strong we are?

Discuss alleged misconduct of our community manager

This serves to notify the community of my intent to raise the issue of alleged misconduct of our community manager during the board's next private session. The details of the matter beyond this information will only be made public with approval of the board.

Foundation member label on Github?

Just noticed these. Do all members get them?

Our Contribution Policy Pledge...

The following was presented to the Board by Ashley and myself on 2017-02-13 during the public Board Meeting.

Ashley and I have had a chance to review some of our membership's top goals for this year-- and today, we'd like to discuss our first joint effort.

We know some of you are excited for us to introduce you to the unique dynamic that has made the Node.js project so successful-- so, we'd like to start with what we believe is one of the biggest tenants to that success: our Contribution Policy.

While we grant complete autonomy to our groups so they can choose any policy they desire- the unanimous choice across them is to:

• publicly offer PRs
• allow sufficient time for iteration and feedback
• commit when consensus has been reached.

Our Membership expects us to participate in our Individual Member roles under the same standards to which the community holds itself. To that end, we are pledging our commitment to follow our community's Contribution Policy.

Starting today, we will be hosting and maintaining a new Board repository under the Node.js GitHub organization. We will post board related topics for community review, feedback and iteration. Once matured to a satisfactory state, by community standards, we will pursue approval here- with the Board. Any of you, of course, are encouraged to visit, review, and even participate.

We, the Board, currently have a few initiatives underway that have not met this standard-- so unfortunately, Ashley and I, cannot commit affirmative votes at this time. We apologize for any delays this causes. We are excited and look forward to assisting you in swiftly ushering them through the process over the next few weeks and months-- so they are ready for our future meetings without delay.

At this point, we're certain you are concerned about some private issues that are inappropriate to make public. We, of course, acknowledge and understand these exceptions. Fortunately, our community also has procedures for similar scenarios.

Our Security group regularly needs to discuss vulnerabilities and find resolution in private. They issue generalized statements to the community without providing sensitive information.

Our Moderation group discusses controversial or concerning events in a semi-private repository that is available to members that have made significant and valuable contributions to the project.

Using these, and other, existing examples-- we can operate within our Community's expectations and avoid any friction that can slow progress. If you get a chance, we encourage you to review the CONTRIBUTING.md base policy that is in the TSC repo.

Q&A w/ @zkat on Individual Membership Candidacy

This thread is for asking @zkat questions regarding her run for the Node.js Foundation Board of Directors.

Q&A w/ @watson on Individual Membership Candidacy

This thread is for asking @watson questions regarding his run
for the Node.js Foundation Board of Directors.

Published By-Laws are out of date

The By-Laws published at https://nodejs.org/en/foundation/ are out-of-date. I believe there have been 2 changes:

• 2015-11 Raise number of Individual Board Members to 2
• 2016-12 Coin Toss resolution.

Perhaps I missed something else, so we'll need to track them down. The individual changes are not merged in to the document yet. We need to complete this and publish them!

Node.js Board Statement on TSC Action

Earlier this week, the Technical Steering Committee (TSC) announced the results of a vote to remove a member from the TSC based on a pattern of behavior, summarized in nodejs/TSC#310. The vote asked two specific questions: Should the member be removed from the TSC and should the member be asked to voluntarily resign from the TSC? For both questions, the results were the same: six responded 'No', four responded 'Yes', two members of the TSC abstained, and one member was recused. As a result of this vote, four TSC members stepped down from their positions: Anna Henningsen, Bryan Hughes, Myles Borins, and Jeremiah Senkpiel.

We, as well as the community, were deeply concerned by these events, and as a result convened a private, meeting of the Node.js board on Tuesday August 22nd. It was deemed necessary to clearly articulate our position and values as the Node.js Foundation Board as follows:

When the Node Foundation was formed in 2015, it was critical to all stakeholders that the authority over day to day governance of the project be granted exclusively to the TSC and this is reflected in the committee’s charter. This was specifically to provide independence to the TSC and empower it to self govern. However, recent incidents have indicated that the governance rules of the TSC are not adequate to address situations such as this. Specifically, individual Code of Conduct issues often transcend the current rules available to address them, affecting the ability of the larger Open Source community to engage and participate in the Node.js project. If conduct issues cannot be resolved acceptably by the TSC under its existing rules, we, as the Foundation Board, have to evaluate whether the structures created at the beginning of our Foundation's journey need to be adjusted in order to address these issues appropriately. The Board will look at options for long term solutions to these issues.

The health of the Node.js community is of paramount importance to the Board, and the behavior of Node.js leadership is critical to this health. The Board does not support antagonistic, aggressive or derogatory behavior in the community and leadership and expects that the TSC will enforce its Code of Conduct equally amongst community members, collaborators, and leadership. Accordingly, we urge the TSC to revisit this issue and suspend the individual involved from active TSC participation until this matter is resolved, hopefully with consensus, including support from those who recently resigned, if they would be willing to help.

We believe that this issue is extremely important and that timeliness and thoroughness of response is critical. As a result, the Board will be devoting the entirety of its August 28th meeting to a private discussion of the current situation. In this session, we’ll be focused both on responding to this incident, as well as reviewing long term governance changes to the TSC, CTC, and Community Committee Charter and rules while respecting the need for these groups to preserve their independence of operation. Due to time constraints, the public board meeting will be canceled for this month, however, we will continue to communicate updates to the community, as they become available. If any member of the community has questions they should direct them to:

• Mark Hinkle, Executive Director, Node.js Foundation ([email protected])

The Node.js Board of Directors

Q&A w/ @ashleygwilliams on Individual Membership Candidacy

This thread is for asking @ashleygwilliams questions regarding her run
for the Node.js Foundation Board of Directors.

Draft Policy for Board Approval

We need to get the individual membership terms ready for board approval.

Membership Cost

• Free for active contributors to projects at the Foundation
• $25 for Students
• $99 for all other individuals.

Eligibility for Election

• Person must not be on the Node TSC
• Person must be a member.

Elections

• One vote per person, majority wins.
• One-year term.

Open Issues

• Timeline for first election.
• Signup tool for members (checks if they are a member of a relevant org, takes their money).

Did I miss anything?

Does the Member signup (AND Renewal!) still work?

I just visited the signup link and it gave me an error... but then I went back and it said I was already a member. Which is true. 😃

This evening I used the "Open Mic" time at the SFNode Meetup to promote people signing up and getting involved. I just want to make sure the system is still working.

This year we will have renewals for the first time- so does that work? Will some people (with signup timing just right) be able to vote just before their 1 year expires?

Q&A w/ @ecowden on Individual Membership Candidacy

This thread is for asking @ecowden questions regarding his run
for the Node.js Foundation Board of Directors.

Q&A w/ @geek on Individual Membership Candidacy

This thread is for asking @geek questions regarding his run
for the Node.js Foundation Board of Directors.

Discussion: Membership Levels and Collaborators

1. What will the Foundation membership levels be?
2. Currently, there is no requirement that a Collaborator also must be a member of Foundation. It seems reasonable to require that Collaborators also maintain their membership (either as individuals or through affiliation with a member organization)

Nominations for 2017 Individual Member representative

Almost 1 year ago- nominations opened up for the Individual Membership representative. So- it seems we should be due to start the process again.

My research says @feross's term will be ending in January.

Q&A w/ @contra on Individual Membership Candidacy

This thread is for asking @contra questions regarding his run
for the Node.js Foundation Board of Directors.

Who/Where is nodejs.org email running?

I don't actually know who is running this or what the setup is but we'll need to figure it out before we offer people email addresses as part of membership.

I know that the LF has some people who host email infra, is this being moved over? @mkdolan

Lacking obvious student registration link

The link in the readme for individual registration points to the standard membership form. There's no obvious link to register as a student member.

Discussion: Mailing Lists

What specific mailing lists do we need? Which mailing lists are already established under @nodejs.org and @iojs.org? What is our migration strategy for these? What new lists need to be created? e.g. [email protected], [email protected], [email protected], etc

Linux Foundation quietly drops community representation

http://mjg59.dreamwidth.org/39546.html

Since Node.js Foundation is part of the Linux Foundation, how does this affect Node.js and the current elections right now?

Q&A w/ @tejasmanohar on Individual Membership Candidacy

This thread is for asking @tejasmanohar questions regarding his run
for the Node.js Foundation Board of Directors.

I'm not a member even though I participate in a Working Group

I'm a member of the Node.js Tracing Working Group and as far as I can understand from the Cost section I should therefore be on the Members team on the Node.js GitHub organization, but since I get a 404 when accessing it I guess that I'm not?

Q&A w/ @williamkapke on Individual Membership Candidacy

This thread is for asking @williamkapke questions regarding his run for the 2017 Node.js Foundation Board of Directors.

PR board minutes for 2017-02-13 Board Meeting

@mikeal, we would like to get a PR up of the proposed public 2017-02-13 Board Meeting minutes at least 36 hours before the meeting. Please let me know if I can help.

Open nominations for Individual Membership Director for the Node.js Foundation Board

The 2017 nomination for the Individual Membership Director seat is now open closed.

Nominations are being solicited until January 15th.
A ballot will be distributed on January 20th.
The election will be completed by January 30th.

UPDATE
We'll be share the link for voting on Friday, January 20th. Voting will close on January 30th at 17:00 UTC. Nominees will be notified same day and prior to the January Node.js Foundation Board meeting.

Please comment here and link to a blog post about yourself and why you would like to represent the individual membership of the Foundation. We will be providing further content that will help inform folks on what is means to be a Director soon!

Please make sure that you have registered as a member of the Foundation prior to announcing your nomination.

Relevant Links:

https://nodejs.org/en/foundation/members/#becoming-an-individual-member
https://nodejs.org/en/blog/community/individual-membership/

What's it like being on the Node.js Foundation Board of Directors?

Nominations:

(Please update!)

• Your name here! @yourgithubhandle
• William Kapke @williamkapke
• Charlie Robbins @indexzero
• Kat Marchán @zkat
• William P. Riley-Land @wprl

Q&A w/ @pgte on Individual Membership Candidacy

This thread is for asking @pgte questions regarding his run
for the Node.js Foundation Board of Directors.

Q&A w/ @feross on Individual Membership Candidacy

This thread is for asking @feross questions regarding his run
for the Node.js Foundation Board of Directors.

Clarify By-Laws WRT Community Committee

1. The type of committee the Community Committee ("CommComm") is-- is not explicitly stated anywhere. The By-Laws define 2 types: Board Committees and Member Committees. The TSC is a Member Committee. I assume the CommComm was enacted under:

Section 5.4 Committees of the Members
(a) From time to time, the Board may establish Member Committees in addition to the
Technical Steering Committee (as described in paragraph (b) below). Membership attendance
and voting rights in all Member Committees shall be as specified in Article II, and any such
Member Committee may operate under such further rules of process as it may propose and
which are approved by the Board.

2. The TSC is excluded from the requirement that its committee members must be Foundation Members:

Section 2.8 Participation
Participation in the Technical Steering Committee and development projects sponsored by the Foundation shall not be limited to Members ... [snip]

3. A benefit of Silver Membership is the opportunity to place a representative on Member Committees:

Section 2.5 Privileges of Silver Membership
... [snip]
(c) appoint one voting representative, on a one vote per Member basis, to each Member
Committee (for example, a Marketing Committee, Finance Committee, etc.) other than the
Technical Steering Committee;

I think we probably want CommComm to have the same exclusions the TSC has above.

/cc @nodejs/community-committee

Section 2.5 c) might need to be updated to include Community Commitee

According to 2.5 c) member organizations are currently able to assign individuals to the Community Committee. I don't believe this is intentional.

/cc @nodejs/community-committee

Foundation Board Code of Conduct?

I've looked at the Node.js Project Code of Conduct and I'm not sure if that applies to just the project or the whole of Node.js Foundation. Is there a specific Code of Conduct for board members? Especially in how they conduct themselves in public places in regards to members of the foundation?

Initial Meeting

Let's figure out a time for this :)

Multiple Representation of a Company

At the Board Meeting on 2017-03-27, an issue of multiple representation of a company on the Board was discussed.

The By-Laws state:

Only one Member which is part of a group of Related Companies shall be entitled at one time to have a representative on the Board or vote on matters voted on by the Members provided, however, that the (i) TSC Director or the Individual Director, but not both, may be an employee of a Platinum Member or one of its Related Companies, notwithstanding the fact that such Platinum Member is also represented on the Board by virtue of its right to appoint a Director under Sections 2.3(a) and 4.3(a) of these Bylaws, and (ii) the Individual Director may be an employee of a Gold or Silver Member or one of its Related Companies, notwithstanding the fact that such Member may already be represented on the Board by an employee elected to the Board of Directors.

It was discovered, and confirmed with legal, that there is currently a conflict that needs to be resolved. Rod Vagg (the TSC Director) and Dan Shaw (a Gold Member Director) are both employed by NodeSource. Since NodeSource is not a Platinum Member, they do not meet the exclusion clause for Platinum Members.

We can change the By-Laws, with a 2/3 vote, to allow 2 people from the same company to be on the board. However, it is unclear if the TSC & community would support this change and it is believed this rule was to provide an incentive for a company to pay to become a Platinum member.

If the By-Laws are not changed: Rod or Dan will need to resign, assign someone in their stead, or somehow be removed.

The Board believes it is important to both notify the community of this situation and collect feedback on the possible solutions. Please comment with which solution you prefer and why. Remember that the solutions would apply to all companies. Feedback that specifically addresses NodeSource, or any company, in particular will be considered derailing and will be moderated. Any other comments that stray from direct feedback on possible solutions will also be considered derailing and will be moderated. If you have related questions, feel free to open up another issue on this repo! Thanks!

//cc @nodejs/tsc

NodeConf

So, I own the Trademark for NodeConf and generally administer the organization and help out with events where I can.

Every NodeConf is run by an individual or company independent of myself (except for the ones I run personally, obviously). We've grown the list of NodeConfs by offering some support and the use of the term under a few conditions:

• NodeConf ONE-SHOT -- Event must be single day, single track. Organizers need only sign up on the organizers repo.
• NodeConf -- Event should be at least 2 days and be of high production value. Organizer must have previously attended a NodeConf (Either US or EU usually).

There are two other events that have previously only been run by me: NodeConf SummerCamp and NodeConf Adventure, which are both unconference format events.

If we decide to bring NodeConf in to the foundation we could put a bit more organization around helping to promote these community events as well as extend the brand to any new events that address audiences we have not previously reached. We could also add some conditions that offer incentives for members to participate: 10% off tickets for individual members and 10% off of sponsorships for corporate members of the foundation.

Rename this repo to `Board` and assign ownership

The Individual Directors, @ashleygwilliams and myself, would like to have a "Board" repo for collaboration with us & and any other willing participants of the Node.js Foundation Board of Directors. I suggest we repurpose THIS repo for it since it already deals with the topic. The bit of membership information that exists here today will stay.

With this, we would be the custodians of the repo. It will be our duty to keep the information up-to-date and coherent for the community. Additionally, we will rely on the assistance of @mikeal and @hackygolucky PLUS any Moderation group that may be formed in the future.

One stipulation I want to call out is that during an election period, if an exiting representative is pursuing re-election, they must not edit/moderate any issues regarding the election. They may, however, participate in them as any other community member would be allowed.

As this repo is not currently under the governance of any particular group except, by default, The Board- I am presenting this post to provide an OPEN notification of the desire to complete this action giving the community an opportunity to vocalize any possible objections. I will leave this open for a minimum of 1 week.

Q&A w/ @indexzero on Individual Membership Candidacy

This thread is for asking @indexzero questions regarding his run for the Node.js Foundation Board of Directors.

Q&A w/ @bnb on Individual Membership Candidacy

This thread is for asking @bnb questions regarding his run
for the Node.js Foundation Board of Directors.

Election rules and eligibility

In order to elect a member from the community we need to establish rules for the election and eligibility for running for board representative.

Eligibility already discussed:

• A member of the TC is not eligible.
• An employee of a company that already has a representative on the board is eligible.

Rules for election:

• @Danese is there an existing model we can base this off?

Q&A w/ @sup on Individual Membership Candidacy

This thread is for asking @sup questions regarding his run
for the Node.js Foundation Board of Directors.

Board vote to allow community member on board

Need to add an item to the first board meeting agenda to vote on changing the By-Laws to allow a community representative on the board.

This issue is to get this item onto the board's agenda.

Can't join with GitHub due to existing Linux Foundation account

The README.md tells me to join with my GitHub account, but I already have a Linux Foundation account so when I try to log in using GitHub, I'm told another account already exists with those credentials. I couldn't find a way to associate my GitHub account with my existing account.

Membership & Email Signup Flow Strawman

Goals:

1. Maintain a single point of administration for lists of members and teams under the foundation.
2. Leverage GitHub repositories for the communication and archive capacity whenever possible.
3. Automate as much of the process as possible.

Signup Flow

1. A potential member logs in to GitHub through a web form at membership.nodejs.org
2. If they are a member of the nodejs GitHub org they are offered free membership, otherwise they are asked to pay a fee ($25 student, $99 individual).
3. They succeed in signing up as a member.
4. They are added/invited to the node-foundation GitHub org and added to the members team.

A cron job runs every hour which syncs the state of members in the node-foundation GitHub org with our email system (using mailgun).

Sync Service

1. Pulls every user in the members team and forward @nodejs.org to the email address in their GitHub profile.
2. Pulls the members of the security teams and routes [email protected] to that team.

I'm not sure yet if there is a good reason to have any other email forwards. We can use GitHub private repos for any sensitive information and we have the benefit of an archive for new members coming in to those groups -- not to mention we have the use of public repos for most communication.

If we need to do an email campaign to all member that should be as simple as pulling the list of all members and sending them an email through mailchimp.

Cost of Membership

Following on from #3 this is to discuss the cost of membership.

Proposed using Linux Foundation model:

• $25/year for Students
• $99/year for Everyone Else

Also discussed free or $1/year membership for core contributors.

Candidacy disqualification for persons that work for a node sponsor

I believe there needs to be a rule to disqualify any candidate for a seat on the board if you work for a company that sponsors node. This could serve to stack the board. Developers need to be assured of unbiased representation and advocacy. While board members do not make decisions as part of the TSC, they influence policy and legal decisions with an impact upon the project.

Nominations for the 2016 election.

If you wish to run for the 2016 individual membership election for the Node.js Foundation Board of Directors please comment here and link to a blog post about yourself and why you would like to represent the individual membership of the foundation.

Please make sure that you have registered as a member of the foundation prior to announcing your nomination (more information on how to do this will be public soon).

Relevant Links:

• https://nodejs.org/en/foundation/members/#becoming-an-individual-member
• https://nodejs.org/en/blog/community/individual-membership/