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 750 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

FreePBX_sipsettings (master): [Module Tag script: sipsettings 13.0.23.3]
Andrew Nagy committed e33fc96 on branch master, release/13.0 in FreePBX_sipsettings
[Module Tag script: sipsettings 13.0.23.3]

· /module.xml (-1, +2) | History | Source | Diff
FreePBX_sipsettings (master): proper ports
Andrew Nagy committed 1724792 on branch master, release/13.0 in FreePBX_sipsettings
proper ports

· /install.php (-4, +4) | History | Source | Diff
FreePBX_daynight (master): Translated using Weblate (Persian (Iran))...
Media Mousavi committed 694f868 on branch master in FreePBX_daynight
Translated using Weblate (Persian (Iran))

Currently translated at 100.0% (58 of 58 strings)

· /i18n/fa_IR/LC_MESSAGES/daynight.mo (binary) | History | Source | Diff
· /i18n/fa_IR/LC_MESSAGES/daynight.po (-6, +5) | History | Source | Diff
FreePBX_Framework (master): Translated using Weblate (Persian (Iran))...
Media Mousavi committed ba2d505 on branch master in FreePBX_Framework
Translated using Weblate (Persian (Iran))

Currently translated at 100.0% (2165 of 2165 strings)

· /amp_conf/htdocs/admin/i18n/fa_IR/LC_MESSAGES/amp.mo (binary) | History | Source | Diff
· /amp_conf/htdocs/admin/i18n/fa_IR/LC_MESSAGES/amp.po (-5, +5) | History | Source | Diff
FreePBX_voicemail (master): Translated using Weblate (Persian (Iran))...
Media Mousavi committed 0b5bd85 on branch master in FreePBX_voicemail
Translated using Weblate (Persian (Iran))

Currently translated at 100.0% (426 of 426 strings)

· /i18n/fa_IR/LC_MESSAGES/voicemail.mo (binary) | History | Source | Diff
· /i18n/fa_IR/LC_MESSAGES/voicemail.po (-6, +5) | History | Source | Diff

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-12315 Extension Display Name on Peers Page Feature Requests May 14, 2016 May 16, 2016 Unassigned Addison Burnside Minor Open Unresolved
FREEPBX-12289 add more line options to the framework Feature Requests May 11, 2016 May 17, 2016 Unassigned danielf Minor Reopened Unresolved
FREEPBX-12166 LDAP Integration Feature Requests Apr 27, 2016 May 02, 2016 Unassigned Diego Espitia Minor Open Unresolved
FREEPBX-12154 "Desktop View" of Google Chrome on Mobile Devices doesnt work Bugs Apr 26, 2016 May 03, 2016 Unassigned Ronny K. Minor Reopened Won't Fix
FREEPBX-12075 Unable to delete custom system recordings via GUI Bugs Apr 15, 2016 Apr 18, 2016 Unassigned ProVu Minor Open Unresolved
FREEPBX-11946 Expand/improve extensions screen Feature Requests Mar 31, 2016 Apr 04, 2016 Unassigned jlutes Minor Open Unresolved
FREEPBX-11933 custom folders and dis-allow deletion of voicemails in ucp Feature Requests Mar 30, 2016 Apr 05, 2016 Unassigned Ronny K. Minor Open Unresolved
FREEPBX-11910 Originate does not work in user and device mode Bugs Mar 26, 2016 May 12, 2016 Andrew Nagy Douglas Hammond Minor Published Unresolved
FREEPBX-11802 Unable to selectcustom context in the device in Device and user mode Bugs Mar 10, 2016 Mar 17, 2016 Unassigned philippebolduc Minor Open Unresolved
FREEPBX-11767 User manager does not like two digit extensions Bugs Mar 07, 2016 May 16, 2016 Andrew Nagy cullenl Minor Published Unresolved
FREEPBX-11723 inconsistent use of NULL and zero-length-string Bugs Mar 01, 2016 Mar 07, 2016 Unassigned dirk Minor Open Unresolved
FREEPBX-11720 Directory module, prefer TTS over spelling Improvement Feb 29, 2016 Mar 07, 2016 Unassigned dirk Minor Open Unresolved
FREEPBX-11673 Remove sliding animation from sidebar Feature Requests Feb 24, 2016 Feb 29, 2016 Unassigned cullenl Minor Open Unresolved
FREEPBX-11669 System Recordings Feature Requests Feb 24, 2016 Feb 29, 2016 Unassigned prryjs Minor Open Unresolved
FREEPBX-11618 UCP Append Notes to Voicemail Messages Feature Requests Feb 18, 2016 Feb 22, 2016 Unassigned Tim Stauffer Minor Open Unresolved
FREEPBX-11493 Don't show progress meter without a terminal Bugs Feb 05, 2016 Feb 11, 2016 Unassigned miken32 Minor Open Unresolved
FREEPBX-11472 Usermanager - ability to specify the DN for users and groups Improvement Feb 02, 2016 May 10, 2016 Andrew Nagy Dmitry Shipovalov Minor Open Unresolved
FREEPBX-11214 Sysadmin VPN Clients are not backed up Bugs Jan 03, 2016 Feb 10, 2016 Unassigned Rob Thomas Minor Open Unresolved
FREEPBX-11187 Update System Status Module Bugs Dec 28, 2015 Feb 10, 2016 Unassigned Keith Ferguson Minor Open Unresolved
FREEPBX-11178 Firewall page not supprt mobile browser Bugs Dec 24, 2015 Apr 24, 2016 Rob Thomas sr377 Minor Open Unresolved
Showing 20 out of 139 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