License for Community Contributions
We've made some updates to our community code contribution guidelines, which will also be in effect for our upcoming hackathon. Here's a quick rundown:
- Open Source Code: We encourage you to publish your code under the MIT License, making it freely available for anyone to use or modify.
- Ownership and Permissions: When contributing code, please ensure it's either your original work or you have explicit permission to share it. Do not include code from clients or employers without proper authorization.
A guideline we will also be using during the upcoming hackathon.
Why promote open code?
The primary goal is to facilitate collaborations during hackathons and other community events, especially when participants come from diverse employment backgrounds. When people from different employers work together, copyright can get messy real quick, we want to prevent that from happening.
If we don't use an open source license
If code is shared without a specific license, the copyright defaults to the individual creators or their employers (depending on their individual contracts). This could create complications if a team member wishes to use the code in future projects, whether for commercial purposes or otherwise.
As the one and only rms once wrote:
When a developer brings a project to a hackathon, and doesn't say whether it will be free, that is not overt opposition to the community spirit, but it undermines that spirit. Hackathons should strengthen the community spirit they are based on, by insisting that hackathon projects commit to release in accord with that spirit.
This means telling developers, “So that you deserve our support and help, you must agree to give the community the use of your project's results in freedom, if you ever consider them good enough to use or release.”
If we do use an open source license
Publishing the code under an open source license ensures that all hackathon team members , future hackathon participants and everyone else in the community can build upon those collaborative efforts and turn it into something useful.
Is This Mandatory?
No, this is not (yet) a hard requirement. You're free to decide how you'd like to release your code when starting a new community project. However, we strongly believe that using an open-source license maximizes the positive impact of your contributions.
We recommend the MIT License because of its maximal flexibility and minimal restrictions. If you have a strong opinion about promoting another open-source license, we're open to discussion. Please share your thoughts so we can consult with our legal team.
Let us know in the comments what you think!
- All Categories
- 40 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 44 Spryker News
- 721 Developer Corner
- 568 Spryker Development
- 62 Spryker Dev Environment
- 376 Spryker Releases
- 32 Propel ORM
- 49 Community Projects
- 6 Gacela Project
- 3 PHP Bridge
- 22 Hackathon
- 18 Job Opportunities
- 3.2K 📜 Slack Archives
- 115 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 29 Product & Business Questions
- 57 Spryker Safari Questions
- 46 Random