Skip to content

Latest commit

 

History

History
56 lines (39 loc) · 4.92 KB

COMMUNITY_BOARD_SEAT_EXPECTATIONS.md

File metadata and controls

56 lines (39 loc) · 4.92 KB
Raw

Expectations of the Community Board of Directors representatives

The OpenJS Foundation bylaws provide for up to three board seats to be filled by the community. This is a brief description of why they exist, and what responsibilities they carry.

About the OpenJS Foundation Board of Directors

As a non-profit, the OpenJS Foundation is overseen by a Board of Directors. Their responsibilities range from managing the business oversight of the Foundation, including budget, marketing, and Foundation staff, to setting legal policy. The Board has a responsibility to ensure that Foundation activities support its purpose as defined in the bylaws:

  • Promote the widespread adoption and continued development of key JavaScript solutions and related technologies worldwide.
  • Facilitate collaboration within the JavaScript and web development community.
  • Create a center of gravity for open source projects throughout the end-to-end JavaScript ecosystem guiding them toward open governance and diverse collaborator bases.
  • Host the infrastructure to support hosted JavaScript open source projects (the “Projects”).
  • Enable, through advancement of Projects and strategic partnerships, an open and accessible web.
  • Undertake such other activities as may from time to time be appropriate to further the purposes and achieve the goals set forth above.

Representations on the Board of Directors

There are three ways by which one becomes a Director.

  • Your company is a Platinum member, and you are appointed.
  • Your company is a Gold or Silver member, and you are elected by the other Gold or Silver members.
  • You are chosen by the community to fill one of the community seats.

Responsibilities of Directors

All Directors have a responsibility to represent the organization or community group which appointed or voted them into their role. In addition, all Directors have a responsibility to represent the best interests of the organization and our development communities.

At a high level, a Director’s responsibilities include:

  • Attending as many board meetings as possible. The board generally meets once per month for two hours. Board meetings require quorum in order to vote, and every meeting includes a vote on the prior meeting’s minutes.
  • Be in touch with your constituents. The most effective board members are in tune with the facts of their community, and opinions held by the people they represent. Their objective is to represent these faithfully and articulately in board matters. Community Directors are expected to be active participants in CPC meetings.
  • Be in touch with your legal counsel. The OpenJS Foundation has legal counsel to advise the Foundation itself. However, for matters of policy, corporate Directors should discuss their positions with corporate counsel to ensure they are aligned with their organization’s positions.
  • Direct Foundation marketing and communication efforts through events, press and analyst outreach, web, social and other marketing efforts.
  • Assist in fundraising and financial governance overall.
  • Read and respond to board emails, particularly votes. The Board attempts to accomplish working sessions and votes between meetings over email, so that meeting time is saved for items which require live discussion.
  • Review monthly meeting minutes. The Board is required to take minutes. These are captured by The Linux Foundation and distributed prior to each call. Directors should review these and make comments and clarifications as needed.
  • Participate in special meetings and committees. There are a few special committees which meet quarterly, including the audit and finance committee. Also, the Board may hold working sessions from time to time. Directors are expected to participate as they are able.

As a community director there are also a few more specific responsibilities:

  • Bring issues from the CPC to the board, follow up to ensure progress and help manage the tracking board https://github.com/openjs-foundation/cross-project-council/projects/5
  • Request and follow up on votes on changes to governance that require board input.
  • Advocate for and facilitate sharing of information between the board, the CPC and the projects.
  • Act as one of the main contacts between the board, Foundation staff and the CPC and the projects.
  • Support the Executive director and foundation staff in building/implementing Foundation programs.

While the Board aspires to meet in-person at least once per year, face-to-face attendance is not mandatory. If a Director cannot secure funding from their organization to attend, or if the schedule does not work, the Foundation provides the ability to dial in.

Estimated time commitment per month for Community Directors:

  • Board/committee meetings: 2-3 hours
  • CPC meetings: 4-5 hours
  • Reviewing meeting minutes, responding to board emails: 2 hours
  • Connecting with constituents: 5 hours (or more)

Total commitment: 13 - 15 hours per month.