It has been a productive year for the Mojaloop Community. A hearty thanks goes out to the past year’s elected members of the Community Governance Committees. Your participation and contributions were greatly appreciated.
Mojaloop Community members are invited to participate in choosing new leaders for the Change Control Board, Design Authority and Community Council. To qualify to participate in this election, you must have been 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.
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 technology proposals among other things.
It is important to note that this committee does not involve itself in business, product 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 a demonstrable knowledge of the Mojaloop codebase and be actively involved in workstreams for at least a year preceding their nomination. You will also need to abide by the Mojaloop Community Code of Conduct.
Change Control Board
The Change Control Board drives wider adoption of the Mojaloop Specification. It is tasked with improving clarity and promoting uniformity of implementations, balancing existing implementations and changes, and driving the costs lower for implementation and maintenance. The CCB also takes the responsibility to safeguard the Mojaloop Family of API specifications so that it upholds the Level One Principles.
Members of the Change Control Board will serve for one year and can be re-elected.
To qualify to vie for a seat on the Change Control Board, you must have a demonstrable knowledge of the Mojaloop codebase and be actively involved in workstreams for at least a year preceding their nomination. You will also need to abide by the Mojaloop Community Code of Conduct.
The Change Control Board is offering two positions for election:
CCB Rapporteur:
- Should be an expert in Financial services (DFSP expert)
- Thorough understanding of Mojaloop Design Principles
- Thorough understanding of Level One Principles
- Thorough understanding of Mojaloop family of APIs (FSPIOP, Settlement, Administration, 3PPI, Reporting)
- Ability to understand product requirements from Mojaloop adopters, implementers (including potential ones) and translate them into designs, APIs, technical requirements as needed
- Ability to understand technical designs and implementations to ensure alignment with Mojaloop specifications
- Ability to critically analyze change requests proposed to provide reviews and feedback
- At least a year of presence in the Mojaloop Community
- Time commitment to do these for the required duration (one year)
- Commitment to the Mojaloop Code of Conduct and other policies
CCB Convener:
- Organizational abilities to facilitate CCB meetings and co-ordinate with various SIG owners as needed and publicize these
- Thorough understanding of Mojaloop Design Principles
- Thorough understanding of Level One Principles
- Thorough understanding of Mojaloop family of APIs (FSPIOP, Settlement, Administration, 3PPI, Reporting)
- Ability to maintain CCB and SIG artifacts (specification documents, Open API / Swagger files, etc) in GitHub and other locations as necessary
- Ability to analyze and understand new change requests, solution proposals, product requirements to ensure engagement of various groups as needed
- Availability to interact with existing, new contributors to facilitate membership into various SIGs and support proposals for formation of new SIGs
- At least a year of presence in the Mojaloop Community
- Time commitment to do these for the required duration (one year)
- 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.
Details | Timeline |
---|---|
Call for Nominations and Registration to Vote | 27 October – 4 November |
Voting Period | 11-16 November |
Announcement of Election Results | 21 November |
Transition Week | 21 November – 2 December |
Please fill out this form to register to vote in the Mojaloop Community Governance Elections and to nominate or self-nominate representatives for the three committees.
We look forward to your active participation in this process. If you have any questions about this process, please contact 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.