Skip to end of metadata
Go to start of metadata

FreePBX Development


 

FreePBX is a true Open Source development effort. Providing GNU GPL v2+ 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.

To participate in the FreePBX project you must agree and submit a filled out copy of our code submission agreement: http://literature.schmoozecom.com/EUA/CodeSubmissionsAgreement.pdf (For more information on this Please see our FAQ)

Getting Started

The easiest way to get started is to simply take a look at our bug tracker. We have over 975 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

Browsing The Source

You can take a quick look at the source here: http://code.freepbx.org/project/FREEPBX

Here is a list of the last 5 commits made to the FreePBX Project

Could not retrieve http://code.freepbx.org/project/FREEPBX?projectKey=FREEPBX&view=all&max=30&RSS=true - Page not permitted. Service Unavailable

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.

Getting Involved

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 on Freenode and make contact. 

We have recently transitioned to GIT which makes getting involved much easier.  To assist in bug fixes and improvements you may fork one of the submodules on Github at https://github.com/FreePBX/ or https://github.com/FreePBX-ContributedModules. Once you have your code tested and working you can submit a pull request or submit a patch after you have fully completed our CSA on file. All bug fixes and feature requests should relate to a ticket at http://issues.freepbx.org.  If you have written a module you would like included in our contributed repo (https://github.com/FreePBX-ContributedModules) simply create a repo for your module on Github then open a ticket in the bug tracker to make us aware of it and we can mirror your repo.  Remember all code submissions through the bug tracker or through git require a CSA on file.  If you are new to GIT please see our wiki for a general overview.

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. For information on translating go here.

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. 

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.

We have also created a tag in our issue tracker called "patches welcome" for things that seem like solid ideas but we do not have official resources for. A good place to get your feet wet may be in working on one of these issues.

Loading
Key Summary T Created Updated Due Assignee Reporter P Status Resolution
FREEPBX-14520 Add search field in config edit Feature Requests Apr 04, 2017 Apr 10, 2017 Unassigned Johann Zurner Minor Open Unresolved
FREEPBX-14030 Max Channels on Sip trunk. Bugs Jan 26, 2017 Feb 06, 2017 Unassigned Dusty Countryman Minor Open Unresolved
FREEPBX-13880 Blacklist Module Should Not Auto-Answer Blacklisted Calls In app-blacklist-check Macro Bugs Dec 28, 2016 Jan 21, 2017 Unassigned Michael Minor Open Unresolved
FREEPBX-13839 Add Microsoft Azure as Backup Destination Feature Requests Dec 19, 2016 Dec 19, 2016 Unassigned Matthew B Minor Open Unresolved
FREEPBX-13800 Improvement: Add Reject Call Option To ext-did-catchall Improvement Dec 10, 2016 Dec 12, 2016 Unassigned Michael Minor Open Unresolved
FREEPBX-13503 CSV export in CDR Reports doesn't export the user Bugs Oct 31, 2016 Nov 30, 2016 Unassigned easyvoip Minor Open Unresolved
FREEPBX-13494 Openldap issues Bugs Oct 31, 2016 Feb 19, 2017 Unassigned Hannes Eberhardt Minor Open Unresolved
FREEPBX-13233 Weak password detection for voicemail Improvement Sep 27, 2016 Jan 30, 2017 Unassigned Andrew Nagy Minor Open Unresolved
FREEPBX-13119 Suggest to allow outbound routes to use VMAuthenticate along with PIN Sets Improvement Sep 09, 2016 Sep 12, 2016 Unassigned Jeff Melaragno Minor Open Unresolved
FREEPBX-12931 Conferences Pro - Recordings not in CDR if 'User join/leave' enabled Bugs Aug 12, 2016 Sep 14, 2016 Andrew Nagy joshpatten Minor Closed Won't Fix
FREEPBX-12877 Add voipbl.org support Improvement Aug 04, 2016 Aug 29, 2016 Unassigned Rapper_skull Minor Open Unresolved
FREEPBX-12820 Aditional field for observation in outbound route Improvement Jul 25, 2016 Oct 05, 2016 Unassigned jasb Minor Open Unresolved
FREEPBX-12734 Username passing to gui_auth.php when no user is Bugs Jul 13, 2016 Jan 30, 2017 Rob Thomas Tyler Minor On Deck Unresolved
FREEPBX-12709 Annual Help System Suggestions Improvement Jul 10, 2016 Jul 23, 2016 Unassigned JessicaRabbit Minor Open Unresolved
FREEPBX-12705 Don't display user's login name under UCP/XMPP chat Improvement Jul 09, 2016 Jan 23, 2017 Unassigned Johann Zurner Minor Open Unresolved
FREEPBX-12622 XMPP loaded modules Feature Requests Jun 26, 2016 Jun 27, 2016 Unassigned Simon Minor Open Unresolved
FREEPBX-12597 Only allow addition of extensions not already in the directory Improvement Jun 21, 2016 Jun 27, 2016 Unassigned Addison Burnside Minor Open Unresolved
FREEPBX-12568 Add descripton for Time(s) under Time Groups Feature Requests Jun 17, 2016 Feb 08, 2017 Unassigned necits2015 Minor On Deck Unresolved
FREEPBX-12433 Reverse IP with PTR domain record Feature Requests May 28, 2016 Sep 12, 2016 Unassigned sr377 Minor Open Unresolved
FREEPBX-12315 Extension Display Name on Peers Page Feature Requests May 14, 2016 May 16, 2016 Unassigned Addison Burnside Minor Open Unresolved
Showing 20 out of 166 issues Refresh

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

New module submissions are a regularly occurring event and you will find many modules that have been submitted as tarballs in the Ticket system that are not available in the online system. Why is that?

The FreePBX project is designed as a Framework that can easily accommodate new modules and for that reason, new modules get written and submitted. This does not mean that we put every module that comes along into the project. As the project has matured and stabilized, we are putting a lot more thought into the architecting of the FreePBX as it continues to evolve and mature into a world class product. In order to do that, we need to carefully evaluate what officially enters the system since adopting a module has many implications. We try very hard once something becomes part of the project to take on the commitment of maintaining and supporting it and making sure that future upgrades of the project will continue to work with the Modules that are part of it. If you are thinking about writing a module that you would like to be part of the core project, you should talk with one of the active developers in advance.

This does not mean that the other modules are less valuable or inferior in any way, if we don't adopt them. If you have written a module you would like included in our contributed repo simply create a repo for your module on github. Open a ticket in the bug tracker to make us aware of it and we can mirror your repo.  Remember all code submissions through the bug tracker or through git require a CSA on file.  If you are new to git please see our wiki for a general overview

 

 

  • No labels