Version 1.0.0

Project Charter

The mission, values, and governance of the OpenECU Alliance and the process for projects to join.

Mission Statement

"Standardize, simplify, and democratize access to ECU data through open specifications and community-maintained tools."

We believe that:

  • ECU data should be accessible to enthusiasts, tuners, and developers alike
  • Open standards foster innovation and interoperability
  • Community maintenance ensures long-term project sustainability
  • Collaboration produces better outcomes than fragmentation

Core Values

Openness

All Alliance specifications and projects are open: freely available, source code is open source, development happens in public, decisions are made transparently.

Community First

The Alliance serves the automotive enthusiast community: user needs drive feature priorities, contributors are valued, feedback channels are maintained.

Quality

Alliance projects maintain high standards: code is reviewed before merging, tests validate functionality, documentation accompanies features.

Sustainability

Projects should outlast their original creators: knowledge is documented, multiple maintainers are cultivated, dependencies are carefully managed.

Vendor Neutrality

The Alliance does not favor any vendor: all ECU manufacturers are supported equally, no exclusive partnerships, community decides priorities.

Scope

In Scope

ECU Log Standards

Specifications for log file formats and channel mappings

Log Analysis Tools

Applications that read, visualize, and analyze ECU data

Tuning Utilities

Tools that assist with ECU calibration and tuning

Data Export/Import

Converters between formats

Educational Resources

Documentation helping users understand ECU data

Out of Scope

  • ECU firmware or embedded software
  • Commercial tuning software
  • Hardware products
  • Projects unrelated to automotive ECU data

What is an Alliance Project?

An Alliance Project is software that has been donated to the OpenECU Alliance for long-term community maintenance. Unlike Spec-Compatible applications (which are independently maintained), Alliance Projects:

  • Are hosted under OpenECU Alliance GitHub organization
  • Are maintained by Alliance contributors
  • Follow Alliance governance and quality standards
  • May use Alliance branding and trademarks
  • Receive community support resources

Benefits of Becoming an Alliance Project

For Project Owners

Sustainability - Project lives on even if you step back
Contributors - Access to Alliance contributor pool
Credibility - Association with established organization
Infrastructure - GitHub org, CI/CD, hosting support
Community - Connection to broader ecosystem

For Users

Longevity - Reduced risk of project abandonment
Quality - Alliance quality standards
Integration - Better integration with other Alliance projects
Support - Community support channels

Eligibility Criteria

To be considered for donation, a project must meet these criteria:

CriterionRequirement
RelevanceRelated to ECU data, logging, tuning, or analysis
MaturityFunctional software with existing users
LicenseOpen source (OSI-approved) or willing to relicense
QualityReasonable code quality, some documentation
MaintenanceCurrent owner willing to participate in transition
Community FitAligns with Alliance mission and values

Project Donation Process

1

Express Interest

Open a discussion in the OpenECUAlliance repository with project details

2

Initial Review

Steering Committee reviews scope, technical soundness, and community interest (2-4 weeks)

3

Due Diligence

Code review for quality/security, license verification, dependency audit

4

Community Discussion

30-day public comment period for community feedback

5

Steering Committee Vote

Requires supermajority (2/3) approval

6

Transfer

Repository transferred, CI/CD configured, announcement published

Project Lifecycle

Project States

IncubatingNew projects in evaluation period
ActiveFully maintained, accepting contributions
MaintenanceBug fixes only, no new features
ArchivedNo longer maintained, read-only

Incubation Period

New Alliance Projects enter a 6-month incubation period and are evaluated for quality and community engagement. Graduation criteria:

  • Active maintainers (2+ recommended)
  • Passing CI/CD pipeline
  • Documentation complete
  • Community engagement demonstrated

Spec-Compatible vs Alliance Project

AspectSpec-CompatibleAlliance Project
OwnershipIndependentAlliance
GovernanceSelf-governedAlliance governance
MaintenanceOwner's responsibilityCommunity responsibility
Branding"Spec-Compatible" badge"Alliance Project" badge
RequirementsImplement specImplement spec + Alliance processes
SupportOwner providesAlliance community

Note: Becoming an Alliance Project is entirely optional. Many excellent applications remain independently maintained.

Contact

Project Donation Inquiries

projects@openecualliance.org

General Questions

info@openecualliance.org