Team structure and responsibilities#

Expectations of all team members#

Here are a few expectations we have of anybody that is formally on an Executable Books team.

Adhere to the Code of Conduct. All contributors to the Executable Books Project (including but not limited to individuals contributing code, providing technical support, discussing in repositories, teaching workshops, or discussing changes to EBP policy) are expected to adhere to the Code of Conduct.

Steering Council#

Their primary duty is to set organizational policy and strategy, to steward all technical and IP assets of the organization, to make decisions when we are at an impasse, and to delegate decision-making power to others in the organization.

See Steering Council for a list of current team members.

Responsibilies#

Note

This is intentionally blank for now, we will add more information in the coming weeks.

Expectations#

Note

This is intentionally simple for now, we will add more information in the coming weeks.

Steering Council Members agree to abide by the EBP Code of Conduct.

Privileges#

  • Owner status of the executablebooks GitHub organizations and repositories.

  • Admin privileges on all Executable Books repositories.

  • Access to any credentials or accounts that the project uses. At least two Steering Council members must have access to all project credentials.

  • Voting privileges for changing Team Policy.

  • All Core Team privileges

Core Team#

Individuals who are particularly interested in the EBP community and have demonstrated a willingness to participate in our community and further its mission. They guide discussion, grow the community, contribute code, and generally help the project improve.

See Core Team for a list of current team members.

Responsibilities#

Note

This is intentionally blank for now, we will add more information in the coming weeks.

Expectations#

Note

This is intentionally simple for now, we will add more information in the coming weeks.

Core Team Members agree to abide by the EBP Code of Conduct.

Privileges#

Note

This is intentionally simple for now, we will add more information in the coming weeks.

Emeritus Team#

For past members of the Core Team or Steering Council that no longer wish to have the responsibilities of team membership. Generally speaking, if a team member wishes to have their team status and responsibilities re-instated, they simply need to ask another core team member.

See Emeritus Team for a list of current team members.

Adding team members#

Our team membership is defined in the @executablebooks GitHub teams. To add a new team member to that list, add them to the team there.

Note

This section is intentionally simple right now, but we aim to add more process for when and how to add team members in the future.