How it works Three tracks, one codebase EDG now works like any other open source project: anyone can contribute, and everything that lands is available to everyone. Development follows three tracks: contributions from the user community, ongoing maintenance, and collectively funded features.   Track 1 Community contributions Bug fixes and new features from EDG users, submitted as pull requests. Reviewers, who are initially experienced EDG developers, evaluate the changes. Once approved, these changes are merged into the EDG codebase.   Track 2 Maintenance: always open Bug fixes and maintenance by the Alliance's EDG developers are published immediately.   Track 3 Features: collectively funded To support the EDG community, the Alliance will provide a way for larger features to be developed and funded by the community. In this way, organizations can support the development of larger features financially rather than committing their developers to the development of these features. Once a feature is funded, it is released to everyone at the same time.    One codebase, for everyone. Whichever track a change arrives on, it lands in the same public repository at the same time. No one gets early access.    The Fiscal Sponsorship Committee (FSC) oversees the process across all three tracks. It is chaired by John Spicer and will include volunteers from the EDG user community. Want a say in who sits on it? See how to get involved.   Chaired by John Spicer Includes volunteers from the EDG user community Oversees how contributions are reviewed and merged Sets priorities for maintenance and new features