Change Control Board, Design Authority and Community Council Elections

It has been a productive year for the Mojaloop Community. A hearty thanks goes out to the elected members of the Design Authority and Community Council – we greatly appreciate your work and contributions throughout your term! It is now time to elect new leaders in these groups, and this year we’re also including two roles in the Change Control Board as part of our electoral slate.

Mojaloop Community members are invited to participate in choosing new members of the Change Control Board, Design Authority and Community Council. To qualify to participate in this election, you must be an active contributor to the Mojaloop Open Source Software, and/or the Mojaloop ecosystem for at least a year.

Community Members are invited to register to vote and self-nominate or nominate an individual to serve on the Change Control Board, Design Authority or Community Council.

Qualifications for Community Council

The Community Council is the representative governing body of the Mojaloop community. Its responsibilities encompass the development and implementation of strategic targets for the community and the resolution of potential conflicts. Members of the Community Council will serve for one year and can be re-elected once. To qualify to vie for a seat on the Community Council, you will need to have a good knowledge of the Mojaloop community and ecosystem. You will also need to be an active contributor to Mojaloop’s mission and abide by the Mojaloop Community Code of Conduct.

Qualifications for Design Authority

The Design Authority provides technical oversight for the Mojaloop community. It is tasked with providing thought leadership on technical issues, resolving technical disputes, reviewing technological/stack proposals, and design reviews among other things. It is important to note that this committee does not involve itself in business discussions, products, or roadmap decisions.

Members of the Design Authority will serve for one year and can be re-elected. To qualify to vie for a seat on the Design Authority, you must have demonstrable knowledge of the Mojaloop codebase and be actively involved in workstreams for at least a year preceding your nomination. You will also need to abide by the Mojaloop Community Code of Conduct.

Change Control Board

Each new initiative that will result in the definition of one or more APIs will define those APIs through a Special Interest Group (SIG). The Special Interest Groups will have a formally designated convener who will be selected by the participants of a SIG. These conveners will collectively make up the Change Control Board. As such, the community will not directly elect members of the Change Control Board, but they will elect representative for the two new roles. Please see below for the requirements for each of those positions.

Change Control Board Rapporteur

1. Should be an expert in Financial Services (DFSP expert)
2. Thorough understanding of Mojaloop Design Principles
3. Thorough understanding of LevelOne Principles
4. Thorough understanding of Mojaloop family of APIs (FSPIOP, Settlement, Administration, 3PPI, Reporting)
5. Ability to understand product requirements from Mojaloop adopters and implementers (including potential ones) and translate them into designs, APIs and technical requirements as needed
6. Ability to understand technical designs and implementations to ensure alignment with Mojaloop specifications
7. Ability to critically analyze change requests proposed to provide reviews and feedback
8. At least a year of presence in the Mojaloop Community
9. Time commitment to do these for the required duration (one year)
10. Commitment to the Mojaloop code of conduct and other policies

Change Control Board Convener

1. Organizational abilities to facilitate CCB meetings, co-ordinate with various SIG owners as needed and publicize these meetings
2. Thorough understanding of Mojaloop Design Principles
3. Thorough understanding of LevelOne Principles
4. Thorough understanding of Mojaloop family of APIs (FSPIOP, Settlement, Administration, 3PPI, Reporting)
5. Ability to maintain CCB and SIG artifacts (specification documents, Open API/Swagger files, etc.) in GitHub and other locations as necessary
6. Ability to analyze and understand new change requests, solution proposals and product requirements to ensure engagement of various groups as needed
7. Availability to interact with existing and new contributions to facilitate membership into various SIGs and support proposals for formation of new SIGs
8. At least a year of presence in the Mojaloop Community
9. Time commitment to do these for the required duration (one year)
10. Commitment to the Mojaloop code of conduct and other policies

Timeline

The following timeline details the dates and milestones in the election and transition process.

Registration

Register here to vote in the Mojaloop Community Governance Elections.

We look forward to your active participation in this process. If you have any questions at all please connect with us on Discourse or contact me at soriko@mojaloop.io.

Connect with us here to join the Mojaloop community and learn more about how you can make an impact. Be sure to follow the Mojaloop Foundation on YouTube, Twitter, LinkedIn and Facebook for all the latest.