Governance

With the open smart grid platform we intend to have the right balance between a benevolent Dictator and a Formal Meritocracy in order to have a balanced decision-making process and to prevent unwanted dictators and everlasting discussions. The basic principle is that decisions are based on consensus. If this decision making process takes too long or a decision is required, the community council has the authority to make a decision. Grid eXchange Fabric complies with the LF Energy governance

The governance and rules should be respected.

Community council / Technical Steering Committee

The community council consists of 5 members and has the authority to make decisions on all community related subjects.

The community council is responsible for:

• General ambitions, objectives and goals

• Principles and understandings

• Governance and consultation bodies

When the community grows, members of the community council can be elected. If the situation demands or requires it, the community council has the ability to establish sub councils for a specific subject, area of domain.

The community council consist of the following members:

• - Lead Architect - Chairman

• - Product owner GXF & LF Energy TAC member for GXF

• - Lead Architect

If you would like to join the community council, please contact us! Mention @OSGP/communitycouncil in an github issue. The (online) community council meetings will happen when needed.

Maintainers

Maintainers are responsible for maintaining parts of the code-base. Maintainers have the following responsibilities

• Coordinate development activity

• Make sure code/documentation reviews are being done

• Coordinate pull-requests

In case of long discussions or arguments, maintainers or other can request a community council decision.

Current maintainers:

• GXF Platform and smart lighting domain:

• GXF Platform and Smart metering domain:

• GXF Architecture & documentation:

Contributors

Contributors include anyone in the technical community that contributes code, documentation, or other technical artifacts to the project.

Anyone can become a contributor. There is no expectation of commitment to the project, no specific skill requirements and no selection process. To become a contributor, a community member simply has to perform one or more actions that are beneficial to the project.