Baseline Protocol
v1.1.0
v1.1.0
  • Welcome
  • Basics
    • Introduction
    • Architecture
    • Glossary
    • FAQ
  • Protocol
    • The Baseline Protocol
    • Architecture
    • Components
    • Layer 2 Scaling
  • Standard
    • The Baseline Protocol Standard
    • The Core Specification
    • The API Specification
    • The CCSM Specification
    • Mainnet Standards
      • Mainnet
      • Mainnet Evolution
  • Community
    • Open Source Community
    • Contributing
    • Technical Members
    • Community Leaders
  • Governance
    • Overview
  • Source Code
    • Packages
      • Baseline
      • CCSM
      • Identity
      • Messaging
      • Privacy
      • Types
      • Vaults
    • Baseline Process
    • Developer Resources
  • Reference Implementations
    • Overview
    • BRI-1
      • Base Example
    • BRI-2
  • Connectors
    • SAP/Microsoft Dynamics
    • Google Sheets/Microsoft Dynamics
    • MSFT Excel Connector
  • Deprecated Work
    • Overview
    • Radish34 - DEPRECATED
      • Radish34 Explained - DEPRECATED
      • Interactive Demo - DEPRECATED
      • Workflow - DEPRECATED
      • Key Diagrams - DEPRECATED
Powered by GitBook
On this page
  • Baseline Core Developers
  • How to become a Baseline Maintainer?
  • What do Baseline Core Developers do?
  • Baseline Maintainers
  • How to become a Baseline Maintainer?
  • What is expected of Baseline Maintainers?
  • How to stop being a Baseline Maintainer or Maintainer?
  • How do Baseline Core Developers organize?
  • Slack Channels
  • Baseline Maintainer Meetings

Was this helpful?

Export as PDF
  1. Community

Technical Members

The Baseline Core Developers and Maintainers are the drivers of the further development and implementation of the protocol

PreviousContributingNextCommunity Leaders

Last updated 21 days ago

Was this helpful?

Baseline Core Developers

Anyone is welcome to join the Baseline Core Developers to develop technical advancements or even just engage in technical discussions that take place.

How to become a Baseline Maintainer?

Sign up to join the Baseline Core Developers **** to receive the calendar invites and access to the Google Drive resources.

What do Baseline Core Developers do?

Core developers are people who take an active role in advancing the Baseline Protocol and/or related projects. They are primarily responsible for:

  • Submitting or working on ****

  • Contributing code or contributing to specification work in the form of PRs that are linked to open and prioritized issues

  • Developing items on the to achieve high priority items

  • Setting up and supporting infrastructure (running demos, CI systems, community projects, etc.) that further the Baseline Protocol

  • Presenting the project and key technologies to the public (in-person, webinar, videos, articles, etc.)

  • Identify technical resources needed for further implementation of the protocol (developer onboarding materials, tutorials, etc.)

  • Working on and leading community efforts that drive adoption of the protocol

Baseline Maintainers

Baseline Protocol Maintainers are Baseline Core Developers with advanced Github repository permissions, requiring compliance with governance for such permissions.

How to become a Baseline Maintainer?

A Baseline Maintainer can become a Baseline Maintainer by doing the following,

  • Being an active Baseline Maintainer by actively attending the bi-weekly meetings

  • The current Maintainers (listed Code Owners) will be assigned to review the Pull Request, and the PR will be merged once two Maintainers approve the request

  • If the Baseline Maintainer request is denied or poses concerns, the proposer or other Baseline Core Devs can escalate to the TSC

What is expected of Baseline Maintainers?

To retain Maintainer permissions and status, Baseline Maintainers are required to comply with the following,

  • Show commitment over time by timely review of Pull Requests

  • Follow branch, PR, code, project style, and testing guidelines

  • Be reliable in completing issues to which they have been assigned

  • Demonstrate competency in software development or specification writing

  • Have a high degree of understanding of the project architecture

  • Be welcoming to others in the community who are using or interested in the protocol

  • Contribute in ways that substantially improve the quality of the project and the experience of people who use it

How to stop being a Baseline Maintainer or Maintainer?

To step away from being a Baseline Maintainer, you can notify the other core developers you would like to relinquish your maintainer status.

What can take away your Core Dev status?

  • You stop reviewing PR's, responding to messages, answering emails, and/or generally ghost the project.

  • You are disrespectful towards anyone in the community and/or involved in the project.

  • You are disruptive to the general process of maintaining the project, meetings, discussions, issues, or other.

How do Baseline Core Developers organize?

Slack Channels

The Baseline Maintainers use a private 'maintainers' channel in Slack that members with Maintainer status are added to.

Baseline Maintainer Meetings

Members with Maintainer status are required to join Baseline Maintainer meetings, as outlined in the terms above.

Making a contribution to the Baseline Protocol through , , or other efforts

Then completing the in its entirety to add users Github ID to the

Attendance Policy: Maintainers must notify the group or a community leader if unable to attend. If a Maintainer misses three consecutive meetings without prior notice, a community member will submit a PR to remove the member's GitHub ID from the

If a Maintainer is removed due to the attendance policy, they must attend 2 Core Dev sessions, notify the group of intent to re-commit, then submit the PR to be added back to the .

Two-thirds of all current Maintainers constitute a quorum for a meeting involving a question of removal. A simple majority vote from Maintainers is required to remove a Baseline Core Dev, but the TSC may be brought in to arbitrate if the Baseline Maintainer to be removed or any other Baseline Maintainer wishes to dispute the action. See **** for details.

The Baseline Core Developers talk in the **** to discuss updates, questions, concerns, or ideas between meetings.

There are bi-weekly Baseline Maintainer meetings where members can new or open , open repo issues and pull requests, roadmap items grant projects, and more.

here
Baseline Improvement Proposals (BLIPs)
Baseline Protocol Roadmap
BLIP work
progressing the roadmap
Pull_Request_Template
Code Owners file
'maintainer' Slack
Code Owners File
Code Owners File
'05-bl-core-devs' channel in Slack
Baseline Improvement Proposals (BLIPs)
Governance