Updated May 27, 2016
Software contributors add functionality to the core open-source SEED Platform™ repository.
A company may contribute software that provides new functionality, fixes bugs, or enhances performance of SEED Platform.
Benefits to Technical Ally
- Official standing as Technical Ally, including promotion and recognition opportunities
- License to use SEED Platform trademark
- Limited technical support
- Access to SEED Platform Collaborative community (ability to share product/service offerings with users, user forum, Collaborative calls and webinars, events such as the Better Buildings Challenge)
Software contributor Technical Allies must meet these requirements annually:
- Contribute code to the Github repository through pull requests, and have it accepted into the Master branch.
- Code contributor agrees that contributions are submitted per SEED’s BSD open source license.
- Code contributions must be substantial (e.g. a new feature or important bug fix, not a typo fix).
- Contributors should notify the SEED team in advance of any plans that would impact the codebase so that development effort can be coordinated. In addition, the SEED team can determine in advance whether a potential contribution would be deemed substantial.
- Execute a SEED Platform trademark sublicense with LBNL.
To be approved as a SEED-Platform Technical Ally, software contributors must follow this process:
Please note that any individual or organization is welcome to participate in the SEED Platform open-source project following the general process outlined above. Official recognition as a Technical Ally is only required when the organization wishes to use the SEED Platform trademark and logo to publicly identify their contributions to the SEED Platform Collaborative. For a complete list of SEED Platform contributors, please see the Authors page in the SEED Platform source-code repository.
- Fill out the SEED Technical Ally interest form
- Fork the SEED-Platform Source Code
- Create a feature branch in the local repository
- Follow coding standards and testing requirements: patches should pass existing tests and provide new tests if needed, along with adequate documentation.
- Agree to the software contribution terms: The SEED-platform project does not currently have a contributor license agreement. Developers who contribute code to this project will retain the copyright in their work and at the same time grant permission for LBNL to distribute the software under the modified BSD license contained in the repository. Note that LBNL cannot accept into the project any code licensed under GPL, Apache 2, or other similarly restrictive licenses.
- Commit your changes
- Create a new Pull Request against SEED-Platform’s develop branch
- Check on the continuous integration test results in your pull request to verify that it successfully passed all the CI tests.
- Complete a code review, if requested
- Code contribution must be a significant feature addition or bug fix, and be accepted into the Master (stable) branch of SEED-Platform, in order to be officially recognized as a SEED-Platform Technical Ally.