This document contains information about a future release and not the current stable version (3.1).
Be aware that information on this page may change and API's may not be stable for production use.
Any open source product is only as good as the community behind it. You can participate by sharing code, ideas, or simply helping others. No matter what your skill level is, every contribution counts.
See our high level overview on silverstripe.org on how you can help out.
Or, for more detailed guidance, read one of the following pages:
- Sharing your opinion and raising issues
- Providing code, whether it's creating a feature or fixing a bug
- Writing and translating documentation
- Translating user-interface elements
House Rules for Everybody
- Ask questions on the forum, and stick to more high-level discussions on the core mailinglist
- Make sure you know how to raise good bug reports
- Everybody can contribute to SilverStripe! If you do, ensure you can submit solid pull requests
House Rules for the Core Team
The "core team" consists of everybody with write permissions to our codebase. With great power comes great responsibility, so we have agreed on certain expectations:
- Be friendly, encouraging and constructive towards other community members
- Frequently review pull requests and new issues (in particular, respond quickly to @mentions)
- Treat issues according to our issue guidelines
- Don't commit directly to core, raise pull requests instead (except trivial fixes)
- Only merge code you have tested and fully understand. If in doubt, ask for a second opinion.
- Ensure contributions have appropriate test coverage, are documented, and pass our coding conventions
- Keep the codebase "releasable" at all times (check our release process)
- API changes and non-trivial features should not be merged into release branches.
- API changes on master should not be merged until they have the buy-in of at least two core committers (or better, through the core mailinglist)
- Be inclusive. Ensure a wide range of SilverStripe developers can obtain an understanding of your code and docs, and you're not the only one who can maintain it.
git push --force, and be careful with your git remotes (no accidental pushes)
- Use your own forks to create feature branches