Introduction
Projects started outside of the Green Software Foundation (GSF) can be donated to the Green Software Foundation.
Benefits of donating a project
Projects donated to GSF are:
- in a neutral environment which fosters collaborative, open development and offers a path to maturity via progressing through the Project Lifecycle
- available for contribution from our 50+ member organizations
- given marketing support from GSF, including:
- being listed on the GSF website and in our newsletter updates;
- the opportunity to participate in GSF events; and
- shout-outs and connections via social media.
- given mentorship in areas such as, but not limited to:
- project management;
- governance;
- legal;
- tooling;
- security best practices; and
- documentation.
Approval
To donate to the GSF, a project must meet either the Incubation approval criteria (if it is a software project) or Draft approval criteria (if it is a documentation project). These criteria are as follows:
Software project (Incubation criteria)
Approval criteria
To move to the next stage, the proposed project must:
- Have an assigned GSF PM
- Have a representative of at least one member organization of the GSF.
- As the project moves through its lifecycle, this representative will attend the parent Working Group, champion the project, volunteer to lead it, and provide updates.
The project’s name must:
- Have the approval of the GSF Marketing team
- Not be trademarked
Document project (Draft criteria)
Approval criteria
To move to the next stage, the proposed project must:
- Have an assigned GSF PM
- Have at least three representatives from different member organizations of the GSF.
- As the project moves through its lifecycle, these representatives will attend the Working Group and champion the project, volunteer to lead it, and provide updates.
- We require at least three representatives to help ensure that the project runs smoothly and progresses towards its goals.
The project’s name must:
- Have the approval of the GSF Marketing team
- Not be trademarked
Membership of donor body
If the donor is already a GSF member, they can continue to work on and run the project but must jointly share it with other member organizations.
If the donor is not a GSF member, they must find a representative of at least one GSF member organization, who is also a Working Group attendee, to take over the project. The conditions in the below must also be met.
Transfer of project ownership
If you donate a project to the GSF, you must transfer complete ownership of it over to the Foundation. This transfer of ownership includes all intellectual property associated with the project, such as patents, trademarks, copyrights, and any other proprietary rights. By transferring ownership, you surrender all rights and authority over the project, and the Green Software Foundation will assume full responsibility for the future development, management, and distribution of the project.
This transfer of ownership is mandatory based on the rules specified in the GSF Charter. This charter outlines the Foundation’s goals, principles, and objectives, which focus on promoting software solutions that are sustainable, energy-efficient, and environmentally friendly. Therefore, it is necessary for the Foundation to have full ownership of the projects it supports to ensure that they align with its mission and values. The project must also comply with the licensing conditions of the Working Group eg. OSWG must use MIT.
Approval process
- Connect with one of the GSF Working Groups and its associated PM.
- Donor body submits the Donation proposal template issue to the Working Group for consensus approval.
- Working Group approves.
- GSF PM submits an issue to the Oversight Committee repo for awareness, after which point the Oversight Committee has 14 days to comment / object.
- If a proposal is deemed by the Working Group or Oversight Committee to be high risk (e.g. there is reputational, financial, legal, or greenwashing risk), it must also be reviewed by the Steering Committee.
- Upon approval, the GSF will provide support, resources, and guidance.
- Once the project is approved then, as discussed above, its proposer will no longer have any rights or control over it, and must be willing to relinquish ownership entirely.
- If the donor is not a member organisation, then the donor is expected to contribute to a donation handover period. Here, donors provide a minimum standard of documentation and training to the representative(s) of at least one member company willing to take on the project and set it up for success within the GSF.
Appendix
Project donation From a non-member
- Intellectual Property: This refers to any creations of the mind, such as inventions, literary and artistic works, symbols, designs, and names used in commerce. It’s important to review the intellectual property involved in a project to ensure that there are no infringements or conflicts with existing patents, trademarks, or copyrights.
- Source Code Copyright Agreement: This agreement outlines the terms and conditions under which the source code of a software product can be used, modified, and distributed. It’s important to review this agreement to ensure that it complies with the project’s goals and objectives.
- Dataset License Agreement: This agreement outlines the terms and conditions under which a dataset can be used, modified, and distributed. It’s important to review this agreement to ensure that the dataset is being used in compliance with any legal and ethical guidelines.
- Patent Policy: This refers to a set of guidelines that dictate how patents are managed within an organization. It’s important to review the patent policy to ensure that it aligns with the project’s goals and objectives and that any potential patent issues are addressed in a fair and consistent manner.
Non-Member Agreement to be Signed By Donating Contributor or Organization
The [Green Software Foundation] (the “Project”) would like to receive input, contributions, suggestions and other feedback (“Contributions”) on the specifications, documents, source code, data, and other artifacts being developed within its working groups (the “Materials”). By signing below, you (on behalf of yourself if you are an individual and your company if you are providing Contributions on behalf of the company) grant the Project under all applicable intellectual property rights owned or Controlled by you or your company a non-exclusive, non-transferable, worldwide, perpetual, irrevocable, royalty-free license to use, disclose, copy, publish, license, modify, sublicense or otherwise distribute and exploit Contributions you provide for the purpose of developing and promoting the Materials and in connection with any product that implements and complies with the Materials. You warrant to the best of your knowledge that you have the rights to provide this Contributions, and if you are providing Contributions on behalf of a company, you warrant that you have the rights to provide Contributions on behalf of your company. You also acknowledge that the Project is not required to incorporate your Contributions into any version of the Materials. You further agree that you and your company will not disclose it or distribute drafts of the non-public Project Materials to third parties. Unless the parties agree otherwise or the Project Materials are made publicly available by the Project, this obligation of non-disclosure will expire five (5) years from the date the material was disclosed to you.
Source Code
Any source code you provide to the Project is subject to the Developer Certificate of Origin version 1.1, available at http://developercertificate.org/ and the license indicated in the Project’s source repository for the Materials.
Dataset
Any data you provide to the Project is subject to the license agreement indicated in the Project’s source repository for the Materials.
Signature: Print Name: Title: Company Name (if applicable): Email: Address: Date:
Note: Prior to any agreement, the GSF Legal Outside Council will review all proposed project donations.