The Open Endurance Initiative was created to help foster open innovation, collaboration, and equity in endurance sports.

The motivation to create OEI was born from the idea to open source Group Run Finder and the dataset that powers it–an effort that is currently in progress–to better align development of that product with the overarching goal of fostering community and inclusion in running. Much of the work that is being migrated and open sourced is what powers GRF today, and the objective is to expand on that foundation to enable developers to more quickly build commercial-grade applications that serve the larger endurance sports ecosystem, we hope with similar objectives to our own.

We're still early on in this process and this is very much work-in-progress, but the genuine hope is that of building a long-lasting platform that can be used to encourage innovation, transparency, and equity in our respective sports. For more info on OEI's goals, please visit openendurance.org (ahem, we sure could use some help building building that site 🤷).

Interesting in helping shape the future of open source endurance sports? Jump in and give us a hand (see Contribute to OEI, below) or drop us a line with your ideas, thoughts, or other feedback.

OEI is just getting started, and we need your help! Here's what we're looking for:

• Maintainers to help with various projects
• Developers
• Devops engineers
• Graphic designers and UX folks
• Security experts
• Writers to help with documentation and requirements
• Writers to help with marketing copy and web content
• Social media experts to help with awareness efforts
• Legal counsel specializing in open source software

Note that we're building an ecosystem of tools, so where your time is best spent depends on what you like to do. For example, we need UI/UX help building out our design system and developer help with our core SDK./ For a look at everything we're working on, check out the repositories below or the OEI Roadmap.

If you're interests lie outside something that can be accomplished through github–social media or legal, for example–email us to talk about how we can best collaborate.

OEI's documentation, source code, tools, and related NPM packages are typically released under either the MIT or GPLv3 license. See each repository's LICENSE file for specifics.

Photos used in the docs are property of their respective owners (probably @kcargile) and are subject to copyright unless otherwise specified.