EEA Community Projects, an OASIS Managed Open Project

EEA Community Projects, an OASIS Managed Open Project, exists to provide a neutral forum for diverse stakeholders to create high-quality specifications that facilitate Ethereum’s longevity, interoperability, and ease of integration. The EEA Community Projects intend to develop clear, open standards, high-quality documentation, and shared test suites that facilitate new features and enhancements to the Ethereum protocol.

For more information on the goals of this effort, see the project charter.

You can also sign up for the EEA Community Projects email group to receive occasional official notifications and discussions.

Governance

The EEA Community Projects operate under the terms of the OASIS Open Project Rules, its Project Governance Document and the applicable license(s) specified in LICENSE.md.

It is overseen by the EEA Community Projects Governing Board.

List of projects & TSCs

Each EEA Community Project is managed by a Technical Steering Committee and overseen by the Project Governing Board.

• Baseline Protocol
  • repos:
    • ethereum-oasis/baseline
    • ethereum-oasis/baseline-website
  • website: baseline-protocol.org
  • email list: baseline@lists.oasis-open-projects.org
  • chat: Slack
  • twitter: @baselineproto
  • TSC Members:
    • Brian Chamberlain
    • Hudson Jameson
    • Anais Ofranc
    • Stefan Schmidt
    • Kartheek Solipuram
    • George Spasov
    • Tomasz Stanczak
    • Conor Svensson
    • Cale Teeter
    • Kyle Thomas
    • John Wolpert (Chair)
  • Governance document: https://github.com/eea-oasis/baseline/blob/master/docs/community/governance.md
• Ethereum OpenRPC - Bootstrapping
  • repos:
  • website:
  • email lists:
  • chat:
  • TSC Members:
  • Governance document:

Contributing

Everyone is welcome to contribute to EEA Community Projects - you do not need to be a "member" of anything to submit a technical contribution or get involved with any of the above project communities. Details on how to contribute to EEA Community Projects can be found on the respective repositories listed above.

CLA & Non-assert signatures required

All technical contributions must be accompanied by a Contributor's License Agreement. This requirement allows our work to advance through de jure standards development stages in forums such as EC or ISO. You will get a prompt to sign this document when you submit a pull request to a project repository, or you can sign here. If you are contributing on behalf of your employer, you must also sign the ECLA here.