Producing a world-leading software product like Joomla requires the contribution of time and attention from a large number of different people. One of the issues we come across repeatedly is how to direct potential contributors to areas of the project where they can have the most rewarding and fun experience by being able to work on stuff that matters to them. The Production Working Groups idea is a scheme to encourage groups of people to come together to work on specific areas that we think require particular attention and work. Each of these teams will be led by one or more community members who will foster collaboration within the group and communicate on a regular basis with the Production Leadership Team (PLT).
If you are interested in helping out with the work of any of the teams listed, then simply contact the relevant coordinator.
Community members are free to propose new working groups by following the procedure outlined on this page. The PLT will review the proposal and probably ask further questions. If approved, the new working group will be listed here and you are all set to go. Each group can choose to use whatever resources and communications channels that make sense for them and this page may include links to further information, ongoing communications or other items of relevance to the team.
Working groups will exist until the job they were set up to do has been completed. Which means that some teams, like the Bug Squad, will be permanent, while others will form and disband in the space of a single release cycle.
These working groups must follow our expected values of openness, inclusion and collaboration. They must follow the mission, vision and values of the Joomla project and additionally we would need the working group coordinators to sign the Joomla Contributor Agreement (JCA). Ordinary working group members would not be required to sign, although they are welcome to do so of course. Regular communication between the working group coordinators and the PLT is expected and it would be great if the teams could blog periodically so that the wider community can be kept in touch with progress.
The following is a list of all current production working groups in alphabetical order under their specific type, Permanent Working Groups or Teams and the Current Working Groups.
The Documentation Working Group is a standing team of people dedicated to improving Joomla's documentation. This includes both user and developer documentation. Our primary focus is this wiki, but we are also responsible for maintaining api.joomla.org and other resources.
This team is responsible for maintaining the Joomla Framework. For further information see Joomla Framework on GitHub
This team is for experienced Joomla users and developers who want to help test and fix reported security issues. If you are interested in helping, please contact David Hurley or Don Gilbert. Thanks!
The Rapid Application Development for CMS Working Group is a standing team focused on maintaining and improving Joomla's Rapid Application Development layer.
For further information see Translations Working Group.
The User Experience Working Group is a standing team focused on the Joomla User Experience. This includes the Joomla administrator user interface, sample templates, sample data and any other related aspects. For further information see The Joomla User Experience Portal.
The Unit Tests for CMS Working Group is a standing team focused on improving the unit test coverage of Joomla's codebase. Although primarily focused on the CMS, efforts are encouraged to assist with the Framework as well.
For further information see...
For further information see https://github.com/joomla-cms/start-here
This group is currently inactive. If you are interested in working on this issue, contact David Hurley.
For further information see Multi-site Working Group
Now that Finder has been integrated into Joomla 2.5 in the form of Smart Search, the time has come to look forward to Joomla 3.x and how we want search to work in that series.
For further information see Search Working Group
For further information see Web Services Working Group