Specifications Steering Committee

The Specifications Steering Committee (SSC) is a group of companies, industry influencers and technical leaders that convene to:

  1. Identify high-level baseline protocol project categories

  2. Articulate specific projects within those categories for the community to execute

  3. Rank projects by loose consensus so that contributors can spot attractive opportunities to work on

The group meets monthly (or biweekly, as needed) and is convened by the TSC Chair. From an OASIS governance perspective, the SSC is considered a subcomittee of the TSC, but in practice, the SSC and TSC have coequal roles in the community.

Project Leadership

Baseline Community Projects are the SSC's way of managing specific objectives for the baseline protocol initiative. SSC members commit themselves to one or more of these.

To be an SSC member means you are standing up -- alone or with a group of members -- to be accountable for one or more projects of the Baseline Protocol Initiative.

While others may do the development and task-work, an SSC member commits to articulating and prioritizing the work, identifying community members and others who can do the work, and using whatever incentive structure is available (or whatever influence one has) to help ensure the work gets done.

SSC Members also keep the community of project stakeholders regularly informed of status. This includes cases where milestones aren't being met or when a project should be shut down and the learning recycled into another project.

Projects in Zenhub and SSC Member Permissions

Here's a snapshot of the project roadmap in the baseline protocol's Zenhub dashboard:

Projects can be technical, strategic, or organizational. For example, a technical project would be finding a messaging system that suits the baseline specifications. An organizational project would be developing a powerful and flexible incentive structure for the baseline community. Both are managed and tracked in Zenhub as shown above.

SSC Members have Github write permission, which gives them the ability to add and edit Projects, Epics and Issues, and to assign (and be assigned) work to specific Contributors.

How to Join the SSC

Unlike the TSC, which is fixed at eleven elected members, the size of the SSC is flexible. To balance openness and inclusiveness with the need to keep the team manageable and accountable, there is a single rule that determines membership: Accountability for Active Projects.

If you want to help lead an existing project or if you intend to create a new project, post the following to the #SSC-membership-requests Slack channel (or optionally contact the TSC Chair directly):

  1. Your name, email, company/organization, github ID

  2. A one or two-sentence description of the area around which you intend to help provide leadership

You will receive back an invitation to either a special session of the SSC or the next general SSC meeting, and you may at that time state your intention to join the team. If no one asks for a further review by the TSC, you are approved as a new member of the SSC and can begin working on your Project(s).

SSC Members will be added to the Github Org, have Read access to the main Baseline Protocol repo and Write access to the Roadmap repo.

New SSC Member Quickstart

Within 24 hours of approval as a new SSC Member, you will be sent an email with instructions on how to get permissions to the various tools you now have at your disposal, including:

  1. The ability to create and edit projects, epics and issues on Zenhub (Write access to the Github repo.)

  2. The ability to post messages to community members

  3. Invitations to the SSC team meetings

To prepare for a great start to your time on the SSC, review the existing projects and top-level epics. Then get an idea where you want to focus your attention, and if it isn't represented in the dashboard, consider adding a Project or talk with other SSC members about it.

Other SSC Member Governance Details

Ending an SSC Membership

Just as getting into the SSC is about stepping up to lead on a project, leaving the SSC would be a natural process of ending those projects or cycling off leading them. The SSC will periodically do a house-cleaning segment in the regular meeting to achieve loose consensus on whether any projects require pruning.

Rough Meeting Agenda

SSC Meetings have these standard agenda items:

  1. Review of new Projects

  2. Triage of Projects that seem to need help

  3. Ranking of "top featured" Projects that will be promoted by community influencers

  4. Celebrate successful Projects and clean up list

Anyone in the member community can suggest agenda items for upcoming SSC meetings. Contact the TSC Chair.

Code of Conduct

Here is the link to the members Code of Conduct