FreePBX is a true Open Source development effort. Providing GNU GPL licensing (or equivalent) is all that is required to make a project Open Source. However, obtaining true community involvement is what makes a good project become great. This means transparent access to the project's activities and a development community with access to the project that is not limited to a sponsoring organization. These values are what fuel a really successful project.
The FreePBX Project uses the Atlassian JIRA application in order to tightly integrate the GIT Activity, Ticket system and Development Wiki. We have integrated this system with the main site so that you are signed on to both sites when you create an account and login to the system. Without an account, you will not be able to submit tickets but will have access to view everything.
The easiest way to get started is to simply take a look at our bug tracker. We have over 816 issues currently open for FreePBX alone.
Accessing The source
Please take a look at our development documentation for setting up a development environment here: Setting Up a Development Environment
Browser The Source
You can take a quick look at the source here: http://code.freepbx.org/project/FREEPBX
FreePBX_core (develop): FREEPBX-7174 #QA #comment Fixed
FREEPBX-13: comment by Andrew Nagy "ship it"
FREEPBX-12: closed by Bryan Walters
FreePBX_devtools (master): Cleanup any local branches which are not on the remote server. This patch is being checked in after talking with both Ro...
FREEPBX-4: Abandoned by Bryan Walters
Community Design and Development
In addition to taking input and feedback from the community at large, FreePBX tries to keep its design and road map plans transparent and accessible. This means ideas are discussed in the Forum, in the Wiki and in the #freepbx-dev IRC channel. Live interaction can also be extremely beneficial, so many phone conversations do take place (after all we are all about phones...). We try hard to document the content of these conversations into the Wiki to further benefit from community review and input.
The Development Wiki lists many ways to get involved. If you want to develop a good way to start is to contact one of the active developers. You can PM them, or you can get onto the Development IRC channel #freepbx-dev and make contact. SVN access is provided to developers similar to other Open Source projects. When a new member gets involved, they provide patches and work with existing developers. After their work is evaluated over a period of time and is found to be of good quality and judgment they are offered access.
Beyond code development there are many ways that you can help. Translations are important and you do not need to be a developer to help in this area. We are aware that there are parts of the code with some limitations today that you might run into. We will work with you on those. We are looking for a Developer who would like to take the lead on the translation subsystem and help us tie up any loose ends that may be needed.
Bug marshals and testing: As bugs get reported, it can be extremely helpful to have some testers who are able to review the bugs, confirm the issues, request additional information from the reporters and in general help us filter the bug reports and prioritize them. Get in touch with the core team if this is something you can help with.
Documentation, Documentation, Documentation
The more quality documentation that exists in a project, the more useful and valuable it becomes. This includes creating original content whether it be How-To Guides, Module Documentation or other forms. It also includes editing existing documentation for correctness and completeness and helping to get the site into a more standardized and organized form. If you have expertise in this area and would like to help drive it, please contact us.
Development Documentation is critical as well. If you are a developer, you probably know that this can be a weak point for many. There is a lot of information on the Development Wiki but it is also a priority of ours to put some effort into cleaning and updating the documentation, organizing it and augmenting it to make it easier for new developers to get involved.
A Note about Third Party Module Development