Contributors to the Baseline Protocol can contribute in various ways listed below:

All work of the Baseline Protocol initiative is maintained publicly on a Github repository.

Full governance for contributing can be found here. ****

Anyone with a Github ID can fork the repo, submit an issue, submit a PR, or participate in the further development of the work.

There are many ways to contribute, including

  • Becoming a technical member by contributing to the technical developments and enhancements of the protocol by joining the Baseline Core Devs, and even becoming a Baseline Maintainer for advanced repo management

  • Being part of the Standards team to submit issues or pull requests for proposed updates and contributing to the discussions around open items regarding the specification****

  • Joining the Outreach team to create content and communicate it to more potential contributors, developers, product owners, and other stakeholders

There is one other, important, way to contribute: use the work in the Baseline Protocol to improve your own offerings. The Baseline Protocol is not a product or platform, the pattern is yours to implement.

Code of Conduct

The Baseline Protocol Code of Conduct is located here

Technical Contributors

Technical contributors are the Technical Members **** in the community.


As of October 1, 2021, the Baseline Protocol organizes using Baseline Improvement Proposals (BLIPs), which are managed similarly to Ethereum Improvement Proposals (EIPs). Everyone is encouraged to submit a BLIP for an idea related to the further development or enhancement of the protocol. BLIPs can be worked on by the Baseline Core Developers or anyone interested, and even be funded through the grant fund if requested and approved.

Work Item Management

The project management style varies by team, with the corresponding repo being the central location for major work items and the Google Drive storing working documents and deliverables.

Submitting a pull request

Follow these steps when submitting a pull request:

  1. Fork the repo into your GitHub account. Read more about forking a repo on Github here.

  2. Create a new branch, based on the main branch, with a name that concisely describes what you’re working on (ex. add-mysql).

  3. Ensure that your changes do not cause any existing tests to fail.

  4. Submit a pull request against the main branch.

Good practice strongly favors committing work frequently to allow Baseline Maintainers time to review. Be brave...let others see what you are working on, even if it isn't "ready."

eCLA and iCLA

Anyone can submit a pull request and commit work to the community. In order for your work to be merged, you will need to sign the eCLA (entity contributor agreement) or iCLA (individual contributor agreement). Here are the details:​

The iCLA happens automatically when people submit a pull request, or they can access directly by going to​

Core Developers and Commit Rules

Merging into Main requires review by three Baseline Maintainers. Active Baseline Core Developers may request to become Baseline Maintainers, and the TSC may step in to resolve any requests with conflicts.

​Vote in the TSC Election

All contributors to the Baseline repositories that have a merged pull request and signed iCLA in the calendar year, are eligible for a vote in the yearly Technical Steering Committee election. Eligible voters will receive information for voting in September.


The active contributors and maintainers of the Baseline Protocol repo can be found on Github.

Note: many contributors work in clones extending the protocol for their products. These people don't necessarily show up in the Github contributors list.

Last updated