Contributing to iLEAP

iLEAP is continuously shaped and strengthened through the insights, feedback, and contributions of our community. Explore the opportunities below to help influence iLEAP’s evolution and future direction.

How to Contribute

As a contributor, you can partake in the project through various ways and opportunities.
When contributing, you always have the option to share your input and thoughts in a more private way with the project team.
In some cases, you may also be invited to provide feedback via GitHub directly or during our participatory workshop.

Here is the list of different ways of how you can contribute to iLEAP

Option 1. Provide (high-level) feedback to the iLEAP Technical Specification

If you found something that is missing or should be improved (or maybe even removed from the iLEAP tech specs), please let us know.
You can do this by either:
1. Fill in the Public Feedback Tracker, where you can also find past feedback documented
2. Write to us at team@ileap.global and share your feedback in confidential.

Option 2. Suggest a new business case or use case for iLEAP

If you find that a more general business case is missing (for example: you would like to use iLEAP in a market-based measures scenario), please get in touch with us.

Option 3. Detailed feedback and comments on iLEAP Technical Specifications Pull Requests

As a contributor, you are part of the iLEAP community and are generally welcome and asked to provide feedback for changes we made in the iLEAP Tech Specs.
This is generally coordinated through GitHub Pull Requests comments.
You can access the list of Pull Requests in the iLEAP repository at GitHub here.

Option 4. Submit a change proposal via a GitHub Pull Requests

The iLEAP Tech Specs are edited by the iLEAP Secretariat with feedback from the community. This community consists of the parties involved in the pilot and a larger group of interested parties who have signed up as contributors.
To propose an actual change to the iLEAP Tech Specs, you can always clone the repository and submit a pull request to the iLEAP repository on GitHub. This is explained in more detail here.
If you have any questions about this, please write to team@ileap.global contact the project team.

Option 5. Suggest a company, initiative, NGO, etc. as a contributor to or pilot tester of iLEAP

If you think there is a party, business initiative, company, NGO etc. that could be interested in contributing to iLEAP, please let us know by writing to team@ileap.global.

Close-up of colorful programming code displayed on a computer monitor with a dark background.

Resources

Prepare to Contribute

Before contributing, explore the key documents, technical specifications, and reference materials that shape iLEAP.

The GLEC Framework
A high-level project summary is given at the iLEAP website
The Pilot Testing document gives a high-level summary of the iLEAP Tech Specs that give you various pointers to “dive deeper”
The iLEAP Tech Specs rendered in HTML
The iLEAP Tech Specs repository containing the “source code” of the iLEAP Tech Specs
WBCSD PACT Tech Specs and Pathfinder Framework
The Feedback tracker, which is public, containing feedback received so far

If you need clarification or have any questions, please reach out to us at team@ileap.global