WSO2 products are 100% open source and released under the Apache License Version 2.0. WSO2 welcomes anyone who is interested in our products to get involved in the WSO2 community.
Here's how you can participate in the WSO2 community
USE WSO2 PRODUCTS
The latest binary packs that correspond to the WSO2 product releases can be downloaded freely via the respective product pages (click the Products menu at the top of this page). We recommend that you download and use WSO2 products so that you can discover the advantages of our lean middleware stack. Your feedback on our products is much appreciated, as it will help us to drive our product roadmaps and the underlying technology. For information on product releases, go to the Release Matrix. For tutorials, articles, white papers, webinars, WSO2 documentation, and other learning resources, look in the Resources menu.
JOIN WSO2 MAILING LISTS
Many WSO2 mailing lists are open to the public, so anyone interested in WSO2 products can monitor the mail threads. You can subscribe to the email@example.com and firstname.lastname@example.org mailing lists to get involved in the discussions on WSO2 development. For more information on subscribing to these mailing lists, see WSO2 Mailing Lists.
PARTICIPATE IN USER FORUMS
The WSO2 team monitors and participates in the discussions on Stack Overflow. If you have any technical or programming questions related to WSO2 products, post them on Stack Overflow. Be sure to tag your question with appropriate keywords such as WSO2 and the product name so that our team can easily find your questions and provide answers. If you cannot find an answer on the user forum, you can email the WSO2 development team directly using the relevant mailing lists described at WSO2 Mailing Lists. We also encourage you to contribute by answering your fellow users' questions on Stack Overflow.
WSO2 has a public bug-tracking system that you can use to report issues, submit enhancement requests, and track and comment on issues. You can also use this system to report issues related to WSO2 product documentation. If you find a bug, first search the dev mailing list to see if someone has faced the same issue, and also check the bug-tracking system. If you can't find any information on the issue, create an issue in the bug-tracking system with as much information as possible, including the product version you were using, how to reproduce the issue, etc.
REPORT SECURITY VULNERABILITIES
The WSO2 security team welcomes contributions from our user community, developers, and security researchers to reinforce our product security. If you find a security vulnerabilities, we strongly encourage you to report them to our private security mailing list email@example.com before disclosing them in any public forums. The security team will be more than happy to assist you in such efforts. For more information on vulnerabilities and how they are handled, visit http://wso2.com/security.
CONTRIBUTE TO THE WSO2 CODE BASE
WSO2 invites anyone (not just committers) to contribute to the code base by providing patches for bug fixes or features. For this purpose you can check out the source of the relevant GitHub repository, build the product, and make changes. You can then contribute your changes by sending a pull request for review. For more information, see Contributing to the Code Base.
A WSO2 PLATFORM EXTENSION
Using WSO2’s extensible framework, anyone can write connectors or inbound endpoints to link to applications and APIs on-premise or in the cloud. You can also implement and publish Identity Server authenticators and provisioning connectors. Check out the available extensions in our Connectors Store, and then contribute your own third-party connectors and authenticators by sending a pull request from https://github.com/wso2-extensions/.
THE WSO2 TRAINING MATERIALS
Training materials for WSO2 products are freely available under the CC by 4.0 license. You can check out the WSO2 training materials at https://github.com/wso2/WSO2-Training and submit new materials, lab exercises, and samples. To send feedback on the training content or get more information, contact firstname.lastname@example.org.
Note: When you contribute code, documentation, or training materials, please fill out and submit a contributor license agreement.