An advantage of open source projects is that developers can collaborate to assist each other and improve the overall project. There are a variety of ways that you can get involved with Broadleaf Commerce.
Participate in Forums
The Broadleaf Commerce forums provide a way for you to get help (and help others). We also encourage participation in the following forums.
- Stack Overflow (use #broadleaf hashtag)
- Spring Forums
- Hibernate Forums
Social Interaction
You can communicate with the Broadleaf Commerce team on Twitter @Broadleaf. If you'd like a steady stream of code changes as they occur in the framework, you can also follow @BroadleafDev.
We'll update you with the latest information via our Facebook and Google+ pages You'll also find our team on GitHub.
Demos and Blogging
We encourage you to fork the demo and create your own samples to share with the community. You can find the demo code along with all public forks on GitHub at BroadleafCommerceDemoSite. Notify us @Broadleaf of any BLC related blogs, whitepapers, or articles. We'll feature the best ones on our web site.
Bugs and Feature Requests
The Broadleaf Team manages releases, bugs, and features using JIRA. You can review issues, report defects, and suggest features through the tool.
IRC
Members of the Broadleaf Commerce team regularly communicate via IRC (irc.freenode.net on the #broadleaf channel). You are welcome to join us.
Contribute to the Core Framework
You are encouraged to fork the Broadleaf Commerce Framework repository in GitHub. Once you've made changes, you can submit a pull request back to the Broadleaf team. Fix a bug that's stopping your team, add a feature, or work on items identified by others in Jira. For non-trivial code submissions, our team will require updated JavaDocs, test cases, and a signed contributor agreement before your changes can be included in the core framework distribution.
