Joomla! Documentation - User contributions [en]

Bug Squad

2012-11-17T05:30:59Z

Sueter:

[[Image:workgroups_bugsquad.jpg|right]]

The Joomla! Bug Squad (JBS) is a team within the production working group. Their job is to identify and fix bugs in Joomla. This includes the following:

* Scan the [http://forum.joomla.org/viewforum.php?f=199 Joomla! Bug Reporting Forum] and [http://forum.joomla.org/viewforum.php?f=579 Joomla! 2.5 Bug Reporting Forum] for reported issues and help community members with solving these issues.
* Maintaining the [[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=11410 Version 2.5x only Bug Tracker]] and [[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 Joomla 3.x Issue Tracker]] .
* Fix reported bugs and resolve reported issues according to the [[Bug Tracking Process]].

The Bug Squad is also supporting with testing and quality assurance when a new major or minor version is developed. Generally speaking the bug-squad is in the lead when a version switches from beta-stage to the stable-stage within the development cycle of Joomla!

The Bug Squad was created in December 2007. As of May 2010, JBS has been organised into the following teams:
* Tracker Team - monitors the forums and trackers
* Coding Team - creates patches for Confirmed Issues
* Testing Team - tests Pending issues
* Automated Testing Team - creates automated system and unit tests for tracker issues
* Migration / Upgrade Team - responsible for supporting migration and upgrading from the prior version to the current version.

These teams are not rigid, and JBS members can participate in whatever activities they wish. The purpose of the teams is to make it easier for JBS members to focus their efforts and learn the skills required to successfully contribute to the project.

If you are a member of the JBS, you might also like to join the JBS group at [http://people.joomla.org/groups/viewgroup/95-Joomla+Bug+Squad.html people.joomla.org].

===Tracker Team===
This team has the very important and sometimes difficult job of filtering all of the forum posts and bug reports and sorting out which ones are real bugs that are ready to be worked on. From the standpoint of the tracker, their job is to move issues from Open status to Confirmed status. Of course, many issues will also be put into other status codes, including Information Required, Needs Review, Duplicate, Not a Bug, and so on.

Before an issue is marked Confirmed, it needs to be reproduced and documented so that others can reproduce the problem.

The Tracker Team should also make sure the issue has the correct Type and Priority. Remember, many users reporting bugs are not familiar with all of the fields and terminology. In many cases, this could be the user's first contribution or interaction with the project.

It is critically important that all JBS members follow the Code of Conduct and show courtesy and respect in all tracker comments. Remember, we are the ambassadors of the Joomla! project, and the way we behave reflects on the whole project. People will naturally be unhappy if an issue they report is not taken seriously or if they feel that it was closed improperly. So we need to be sensitive to that fact, while of course making the what we believe to be the correct decision. For example, if you close an issue as Not a Bug, please put a comment in telling the reporter why in a nice way.

Also, if someone is not following the Code of Conduct in a tracker comment, please point this out in a respectful way and remind the person that we need to follow the CoC at all times. If there is a persistent problem, please let your Team Leader or a JBS Coordinator know so we can take action. We absolutely do not want to tolerate rude or disrespectful behavior in the tracker or forum.

For more information see the [[Tracker Team]] page.

===Coding Team===
The coding team works with Confirmed issues and creates patches to correct these issues if they haven't already been provided. When a patch is completed, and when a test plan has been added that tells the testers how to test the patch, the issue is changed to Pending status.

Many times the first patch submitted for an issue will not be the actual patch that is committed to the SVN. There are many reasons for this. Someone else may have a different approach to the solving the issue, a tester might find a problem, or the person who submitted the patch will think of a better way to do it.

It is important to be positive and flexible and not expect that every patch you submit will go straight into the SVN. That does not mean the work is not helpful or valuable. In many cases, it is not possible to get to the end result without going through one or more tries.

For more information see the [[Bug Squad Coding Team]] page.

===Testing Team===
This team tests Pending issues and, when tests are successful, documents this and moves the issue to Ready to Commit status. At this point, one of the JBS coordinators will commit the patch to the SVN.

Over time, we plan to include more automated testing into the process. Eventually, we would like every Ready to Commit issue have both a code patch and an automated system or unit test. Accordingly, it will be important for members of the testing team to be learning how to write and use system tests.

There are some tips for testing in the wiki in the [[Testing Checklists]] article.

===Automated Testing Team===
Automated testing is a key technology that we will incorporate into the workings of JBS. At the present, this is a somewhat specialized skill, so we will start by developing a separate team of people who are familiar with this and can help write automated tests and train other JBS members on automated testing. Our aim is to eventually make automated testing a routine part of fixing issues.

For more information see the [[Automated Testing Team]] page.

===Migration / Upgrade Team===
This team is responsible for coding and documenting the upgrade process for users migrating sites or extensions from one version to the next (for example, from version 1.5 to 1.6). They will be responsible for creating and fixing issues in this area of the code.

===Contacts===
;Joomla! Bug Squad Coordinators : [mailto:mark.dexter@community.joomla.org Mark Dexter]

;To request to join the Bug Squad :[mailto:mark.dexter@community.joomla.org Mark Dexter]
;Tracker Team Leaders: [mailto:elin.waring@gmail.com Elin Waring]
;Coding Team Leaders:
: to be announced
;Testing Team Leaders : [mailto:marijkestuivenberg@gmail.com Marijke Stuivenberg]
;Automated Testing Team Leaders : to be announced
<noinclude>[[Category:Development Working Group]][[Category:Bug Squad]]</noinclude>
[[Category:Working Groups]]

Bug Squad

2012-11-17T05:29:58Z

Sueter:

[[Image:workgroups_bugsquad.jpg|right]]

The Joomla! Bug Squad (JBS) is a team within the production working group. Their job is to identify and fix bugs in Joomla. This includes the following:

* Scan the [http://forum.joomla.org/viewforum.php?f=199 Joomla! Bug Reporting Forum] and [http://forum.joomla.org/viewforum.php?f=579 Joomla! 2.5 Bug Reporting Forum] for reported issues and help community members with solving these issues.
* Maintaining the [[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=11410 Version 2.5x only Bug Tracker]] and [[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS 3 Tracker]] .
* Fix reported bugs and resolve reported issues according to the [[Bug Tracking Process]].

The Bug Squad is also supporting with testing and quality assurance when a new major or minor version is developed. Generally speaking the bug-squad is in the lead when a version switches from beta-stage to the stable-stage within the development cycle of Joomla!

The Bug Squad was created in December 2007. As of May 2010, JBS has been organised into the following teams:
* Tracker Team - monitors the forums and trackers
* Coding Team - creates patches for Confirmed Issues
* Testing Team - tests Pending issues
* Automated Testing Team - creates automated system and unit tests for tracker issues
* Migration / Upgrade Team - responsible for supporting migration and upgrading from the prior version to the current version.

These teams are not rigid, and JBS members can participate in whatever activities they wish. The purpose of the teams is to make it easier for JBS members to focus their efforts and learn the skills required to successfully contribute to the project.

If you are a member of the JBS, you might also like to join the JBS group at [http://people.joomla.org/groups/viewgroup/95-Joomla+Bug+Squad.html people.joomla.org].

===Tracker Team===
This team has the very important and sometimes difficult job of filtering all of the forum posts and bug reports and sorting out which ones are real bugs that are ready to be worked on. From the standpoint of the tracker, their job is to move issues from Open status to Confirmed status. Of course, many issues will also be put into other status codes, including Information Required, Needs Review, Duplicate, Not a Bug, and so on.

Before an issue is marked Confirmed, it needs to be reproduced and documented so that others can reproduce the problem.

The Tracker Team should also make sure the issue has the correct Type and Priority. Remember, many users reporting bugs are not familiar with all of the fields and terminology. In many cases, this could be the user's first contribution or interaction with the project.

It is critically important that all JBS members follow the Code of Conduct and show courtesy and respect in all tracker comments. Remember, we are the ambassadors of the Joomla! project, and the way we behave reflects on the whole project. People will naturally be unhappy if an issue they report is not taken seriously or if they feel that it was closed improperly. So we need to be sensitive to that fact, while of course making the what we believe to be the correct decision. For example, if you close an issue as Not a Bug, please put a comment in telling the reporter why in a nice way.

Also, if someone is not following the Code of Conduct in a tracker comment, please point this out in a respectful way and remind the person that we need to follow the CoC at all times. If there is a persistent problem, please let your Team Leader or a JBS Coordinator know so we can take action. We absolutely do not want to tolerate rude or disrespectful behavior in the tracker or forum.

For more information see the [[Tracker Team]] page.

===Coding Team===
The coding team works with Confirmed issues and creates patches to correct these issues if they haven't already been provided. When a patch is completed, and when a test plan has been added that tells the testers how to test the patch, the issue is changed to Pending status.

Many times the first patch submitted for an issue will not be the actual patch that is committed to the SVN. There are many reasons for this. Someone else may have a different approach to the solving the issue, a tester might find a problem, or the person who submitted the patch will think of a better way to do it.

It is important to be positive and flexible and not expect that every patch you submit will go straight into the SVN. That does not mean the work is not helpful or valuable. In many cases, it is not possible to get to the end result without going through one or more tries.

For more information see the [[Bug Squad Coding Team]] page.

===Testing Team===
This team tests Pending issues and, when tests are successful, documents this and moves the issue to Ready to Commit status. At this point, one of the JBS coordinators will commit the patch to the SVN.

Over time, we plan to include more automated testing into the process. Eventually, we would like every Ready to Commit issue have both a code patch and an automated system or unit test. Accordingly, it will be important for members of the testing team to be learning how to write and use system tests.

There are some tips for testing in the wiki in the [[Testing Checklists]] article.

===Automated Testing Team===
Automated testing is a key technology that we will incorporate into the workings of JBS. At the present, this is a somewhat specialized skill, so we will start by developing a separate team of people who are familiar with this and can help write automated tests and train other JBS members on automated testing. Our aim is to eventually make automated testing a routine part of fixing issues.

For more information see the [[Automated Testing Team]] page.

===Migration / Upgrade Team===
This team is responsible for coding and documenting the upgrade process for users migrating sites or extensions from one version to the next (for example, from version 1.5 to 1.6). They will be responsible for creating and fixing issues in this area of the code.

===Contacts===
;Joomla! Bug Squad Coordinators : [mailto:mark.dexter@community.joomla.org Mark Dexter]

;To request to join the Bug Squad :[mailto:mark.dexter@community.joomla.org Mark Dexter]
;Tracker Team Leaders: [mailto:elin.waring@gmail.com Elin Waring]
;Coding Team Leaders:
: to be announced
;Testing Team Leaders : [mailto:marijkestuivenberg@gmail.com Marijke Stuivenberg]
;Automated Testing Team Leaders : to be announced
<noinclude>[[Category:Development Working Group]][[Category:Bug Squad]]</noinclude>
[[Category:Working Groups]]

Production Working Groups

2012-11-14T23:19:38Z

Sueter: /* Unified Content Model Working Group */

{{RightTOC}}
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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

=Production Working Groups=
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.

==Permanent Working Groups (Teams)==
====Bug Squad====
For further information see the [[Portal:Bug Squad|Bug Squad]] Portal.

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Documentation Working Group====
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

====Joomla Security Strike Team====
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Translations Working Group====
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

====User Experience Working Group====
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

==Current Working Groups==
====Database Working Group====
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

* Coordinator: Open.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Internet of Things Working Group====
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

====JavaScript Working Group====

* Coordinator: Joe LeBlanc
* PLT Contact: Andy Tarr (mailto:andrea.tarr@joomla.org)

For further information see [[JavaScript Working Group]]

====Multi-site Working Group====

* Coordinator: Open
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

For further information see [[Multi-site Working Group]]

====Message Queue Working Group====

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

For further information see: [[Message Queue Working Group]].

====Search Working Group====
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: Open.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

====Unified Content Model Working Group====
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: Elin Waring
* PLT Contact: To be determined.

For further information see [[Unified Content Model Working Group]]

====Unit Tests for CMS Working Group====

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

====Update and Migration Working Group====
The Update and Migration Working Group looks to solve the immediate problem of Joomla 1.5 to 2.5+ core migration with extensibility to extensions of all types.

* Coordinator: Robert Jacobi (mailto:robert.jacobi@arctg.com)
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org)

For further information see [[Update and Migration Working Group]]

====Web Services Working Group====

* Coordinator: Ashwin Date (mailto:coolbung@gmail.com)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Web Services Working Group]]

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Production Working Groups

2012-11-14T23:19:06Z

Sueter: /* Unified Content Model Working Group */

{{RightTOC}}
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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

=Production Working Groups=
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.

==Permanent Working Groups (Teams)==
====Bug Squad====
For further information see the [[Portal:Bug Squad|Bug Squad]] Portal.

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Documentation Working Group====
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

====Joomla Security Strike Team====
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Translations Working Group====
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

====User Experience Working Group====
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

==Current Working Groups==
====Database Working Group====
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

* Coordinator: Open.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Internet of Things Working Group====
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

====JavaScript Working Group====

* Coordinator: Joe LeBlanc
* PLT Contact: Andy Tarr (mailto:andrea.tarr@joomla.org)

For further information see [[JavaScript Working Group]]

====Multi-site Working Group====

* Coordinator: Open
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

For further information see [[Multi-site Working Group]]

====Message Queue Working Group====

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

For further information see: [[Message Queue Working Group]].

====Search Working Group====
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: Open.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

====Unified Content Model Working Group====
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: Elin Waring (mailto:elin.waring@gmail.com)
* PLT Contact: To be determined.

For further information see [[Unified Content Model Working Group]]

====Unit Tests for CMS Working Group====

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

====Update and Migration Working Group====
The Update and Migration Working Group looks to solve the immediate problem of Joomla 1.5 to 2.5+ core migration with extensibility to extensions of all types.

* Coordinator: Robert Jacobi (mailto:robert.jacobi@arctg.com)
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org)

For further information see [[Update and Migration Working Group]]

====Web Services Working Group====

* Coordinator: Ashwin Date (mailto:coolbung@gmail.com)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Web Services Working Group]]

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Production Working Groups

2012-11-14T23:17:22Z

Sueter: /* Unified Content Model Working Group */

{{RightTOC}}
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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

=Production Working Groups=
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.

==Permanent Working Groups (Teams)==
====Bug Squad====
For further information see the [[Portal:Bug Squad|Bug Squad]] Portal.

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Documentation Working Group====
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

====Joomla Security Strike Team====
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Translations Working Group====
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

====User Experience Working Group====
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

==Current Working Groups==
====Database Working Group====
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

* Coordinator: Open.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Internet of Things Working Group====
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

====JavaScript Working Group====

* Coordinator: Joe LeBlanc
* PLT Contact: Andy Tarr (mailto:andrea.tarr@joomla.org)

For further information see [[JavaScript Working Group]]

====Multi-site Working Group====

* Coordinator: Open
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

For further information see [[Multi-site Working Group]]

====Message Queue Working Group====

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

For further information see: [[Message Queue Working Group]].

====Search Working Group====
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: Open.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

====Unified Content Model Working Group====
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: Elin Waring [[mailto:elin.waring@gmail.com]]
* PLT Contact: To be determined.

For further information see [[Unified Content Model Working Group]]

====Unit Tests for CMS Working Group====

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

====Update and Migration Working Group====
The Update and Migration Working Group looks to solve the immediate problem of Joomla 1.5 to 2.5+ core migration with extensibility to extensions of all types.

* Coordinator: Robert Jacobi (mailto:robert.jacobi@arctg.com)
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org)

For further information see [[Update and Migration Working Group]]

====Web Services Working Group====

* Coordinator: Ashwin Date (mailto:coolbung@gmail.com)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Web Services Working Group]]

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Production Working Groups

2012-11-14T23:14:29Z

Sueter: /* Search Working Group */

{{RightTOC}}
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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

=Production Working Groups=
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.

==Permanent Working Groups (Teams)==
====Bug Squad====
For further information see the [[Portal:Bug Squad|Bug Squad]] Portal.

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Documentation Working Group====
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

====Joomla Security Strike Team====
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Translations Working Group====
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

====User Experience Working Group====
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

==Current Working Groups==
====Database Working Group====
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

* Coordinator: Open.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Internet of Things Working Group====
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

====JavaScript Working Group====

* Coordinator: Joe LeBlanc
* PLT Contact: Andy Tarr (mailto:andrea.tarr@joomla.org)

For further information see [[JavaScript Working Group]]

====Multi-site Working Group====

* Coordinator: Open
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

For further information see [[Multi-site Working Group]]

====Message Queue Working Group====

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

For further information see: [[Message Queue Working Group]].

====Search Working Group====
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: Open.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

====Unified Content Model Working Group====
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: To be determined.
* PLT Contact: To be determined.

For further information see [[Unified Content Model Working Group]]

====Unit Tests for CMS Working Group====

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

====Update and Migration Working Group====
The Update and Migration Working Group looks to solve the immediate problem of Joomla 1.5 to 2.5+ core migration with extensibility to extensions of all types.

* Coordinator: Robert Jacobi (mailto:robert.jacobi@arctg.com)
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org)

For further information see [[Update and Migration Working Group]]

====Web Services Working Group====

* Coordinator: Ashwin Date (mailto:coolbung@gmail.com)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Web Services Working Group]]

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Production Working Groups

2012-11-14T23:14:06Z

Sueter: /* Message Queue Working Group */

{{RightTOC}}
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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

=Production Working Groups=
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.

==Permanent Working Groups (Teams)==
====Bug Squad====
For further information see the [[Portal:Bug Squad|Bug Squad]] Portal.

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Documentation Working Group====
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

====Joomla Security Strike Team====
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Translations Working Group====
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

====User Experience Working Group====
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

==Current Working Groups==
====Database Working Group====
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

* Coordinator: Open.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Internet of Things Working Group====
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

====JavaScript Working Group====

* Coordinator: Joe LeBlanc
* PLT Contact: Andy Tarr (mailto:andrea.tarr@joomla.org)

For further information see [[JavaScript Working Group]]

====Multi-site Working Group====

* Coordinator: Open
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

For further information see [[Multi-site Working Group]]

====Message Queue Working Group====

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

For further information see: [[Message Queue Working Group]].

====Search Working Group====
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: To be determined.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

====Unified Content Model Working Group====
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: To be determined.
* PLT Contact: To be determined.

For further information see [[Unified Content Model Working Group]]

====Unit Tests for CMS Working Group====

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

====Update and Migration Working Group====
The Update and Migration Working Group looks to solve the immediate problem of Joomla 1.5 to 2.5+ core migration with extensibility to extensions of all types.

* Coordinator: Robert Jacobi (mailto:robert.jacobi@arctg.com)
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org)

For further information see [[Update and Migration Working Group]]

====Web Services Working Group====

* Coordinator: Ashwin Date (mailto:coolbung@gmail.com)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Web Services Working Group]]

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Production Working Groups

2012-11-14T23:12:37Z

Sueter: /* Database Working Group */

{{RightTOC}}
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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

=Production Working Groups=
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.

==Permanent Working Groups (Teams)==
====Bug Squad====
For further information see the [[Portal:Bug Squad|Bug Squad]] Portal.

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Documentation Working Group====
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

====Joomla Security Strike Team====
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Translations Working Group====
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

====User Experience Working Group====
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

==Current Working Groups==
====Database Working Group====
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

* Coordinator: Open.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Internet of Things Working Group====
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

====JavaScript Working Group====

* Coordinator: Joe LeBlanc
* PLT Contact: Andy Tarr (mailto:andrea.tarr@joomla.org)

For further information see [[JavaScript Working Group]]

====Multi-site Working Group====

* Coordinator: Open
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

For further information see [[Multi-site Working Group]]

====Message Queue Working Group====

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see: [[Message Queue Working Group]].

====Search Working Group====
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: To be determined.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

====Unified Content Model Working Group====
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: To be determined.
* PLT Contact: To be determined.

For further information see [[Unified Content Model Working Group]]

====Unit Tests for CMS Working Group====

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

====Update and Migration Working Group====
The Update and Migration Working Group looks to solve the immediate problem of Joomla 1.5 to 2.5+ core migration with extensibility to extensions of all types.

* Coordinator: Robert Jacobi (mailto:robert.jacobi@arctg.com)
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org)

For further information see [[Update and Migration Working Group]]

====Web Services Working Group====

* Coordinator: Ashwin Date (mailto:coolbung@gmail.com)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Web Services Working Group]]

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Production Working Groups

2012-11-14T23:12:14Z

Sueter: /* Multi-site Working Group */

{{RightTOC}}
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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

=Production Working Groups=
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.

==Permanent Working Groups (Teams)==
====Bug Squad====
For further information see the [[Portal:Bug Squad|Bug Squad]] Portal.

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Documentation Working Group====
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

====Joomla Security Strike Team====
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Translations Working Group====
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

====User Experience Working Group====
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

==Current Working Groups==
====Database Working Group====
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Internet of Things Working Group====
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

====JavaScript Working Group====

* Coordinator: Joe LeBlanc
* PLT Contact: Andy Tarr (mailto:andrea.tarr@joomla.org)

For further information see [[JavaScript Working Group]]

====Multi-site Working Group====

* Coordinator: Open
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

For further information see [[Multi-site Working Group]]

====Message Queue Working Group====

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see: [[Message Queue Working Group]].

====Search Working Group====
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: To be determined.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

====Unified Content Model Working Group====
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: To be determined.
* PLT Contact: To be determined.

For further information see [[Unified Content Model Working Group]]

====Unit Tests for CMS Working Group====

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

====Update and Migration Working Group====
The Update and Migration Working Group looks to solve the immediate problem of Joomla 1.5 to 2.5+ core migration with extensibility to extensions of all types.

* Coordinator: Robert Jacobi (mailto:robert.jacobi@arctg.com)
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org)

For further information see [[Update and Migration Working Group]]

====Web Services Working Group====

* Coordinator: Ashwin Date (mailto:coolbung@gmail.com)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Web Services Working Group]]

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Production Working Groups

2012-11-14T23:11:40Z

Sueter: /* Multi-site Working Group */

{{RightTOC}}
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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

=Production Working Groups=
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.

==Permanent Working Groups (Teams)==
====Bug Squad====
For further information see the [[Portal:Bug Squad|Bug Squad]] Portal.

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Documentation Working Group====
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

====Joomla Security Strike Team====
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Translations Working Group====
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

====User Experience Working Group====
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

==Current Working Groups==
====Database Working Group====
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Internet of Things Working Group====
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

====JavaScript Working Group====

* Coordinator: Joe LeBlanc
* PLT Contact: Andy Tarr (mailto:andrea.tarr@joomla.org)

For further information see [[JavaScript Working Group]]

====Multi-site Working Group====

* Coordinator: Open
* PLT Contact:

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

For further information see [[Multi-site Working Group]]

====Message Queue Working Group====

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see: [[Message Queue Working Group]].

====Search Working Group====
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: To be determined.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

====Unified Content Model Working Group====
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: To be determined.
* PLT Contact: To be determined.

For further information see [[Unified Content Model Working Group]]

====Unit Tests for CMS Working Group====

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

====Update and Migration Working Group====
The Update and Migration Working Group looks to solve the immediate problem of Joomla 1.5 to 2.5+ core migration with extensibility to extensions of all types.

* Coordinator: Robert Jacobi (mailto:robert.jacobi@arctg.com)
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org)

For further information see [[Update and Migration Working Group]]

====Web Services Working Group====

* Coordinator: Ashwin Date (mailto:coolbung@gmail.com)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Web Services Working Group]]

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Production Working Groups

2012-11-14T23:11:06Z

Sueter: /* Multi-site Working Group */

{{RightTOC}}
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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

=Production Working Groups=
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.

==Permanent Working Groups (Teams)==
====Bug Squad====
For further information see the [[Portal:Bug Squad|Bug Squad]] Portal.

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Documentation Working Group====
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

====Joomla Security Strike Team====
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Translations Working Group====
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

====User Experience Working Group====
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

==Current Working Groups==
====Database Working Group====
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Internet of Things Working Group====
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

====JavaScript Working Group====

* Coordinator: Joe LeBlanc
* PLT Contact: Andy Tarr (mailto:andrea.tarr@joomla.org)

For further information see [[JavaScript Working Group]]

====Multi-site Working Group====

* Coordinator:
* PLT Contact:

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

For further information see [[Multi-site Working Group]]

====Message Queue Working Group====

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see: [[Message Queue Working Group]].

====Search Working Group====
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: To be determined.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

====Unified Content Model Working Group====
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: To be determined.
* PLT Contact: To be determined.

For further information see [[Unified Content Model Working Group]]

====Unit Tests for CMS Working Group====

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

====Update and Migration Working Group====
The Update and Migration Working Group looks to solve the immediate problem of Joomla 1.5 to 2.5+ core migration with extensibility to extensions of all types.

* Coordinator: Robert Jacobi (mailto:robert.jacobi@arctg.com)
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org)

For further information see [[Update and Migration Working Group]]

====Web Services Working Group====

* Coordinator: Ashwin Date (mailto:coolbung@gmail.com)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Web Services Working Group]]

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Production Working Groups

2012-11-14T23:06:52Z

Sueter: /* Internet of Things Working Group */

{{RightTOC}}
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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

=Production Working Groups=
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.

==Permanent Working Groups (Teams)==
====Bug Squad====
For further information see the [[Portal:Bug Squad|Bug Squad]] Portal.

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Documentation Working Group====
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

====Joomla Security Strike Team====
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Translations Working Group====
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

====User Experience Working Group====
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

==Current Working Groups==
====Database Working Group====
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Internet of Things Working Group====
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

====JavaScript Working Group====

* Coordinator: Joe LeBlanc
* PLT Contact: Andy Tarr (mailto:andrea.tarr@joomla.org)

For further information see [[JavaScript Working Group]]

====Multi-site Working Group====

* Coordinator: Christophe Demko (mailto:christophe.demko@joomla.org).
* PLT Contact: Christophe Demko (mailto:christophe.demko@joomla.org).

For further information see [[Multi-site Working Group]]

====Message Queue Working Group====

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see: [[Message Queue Working Group]].

====Search Working Group====
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: To be determined.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

====Unified Content Model Working Group====
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: To be determined.
* PLT Contact: To be determined.

For further information see [[Unified Content Model Working Group]]

====Unit Tests for CMS Working Group====

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

====Update and Migration Working Group====
The Update and Migration Working Group looks to solve the immediate problem of Joomla 1.5 to 2.5+ core migration with extensibility to extensions of all types.

* Coordinator: Robert Jacobi (mailto:robert.jacobi@arctg.com)
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org)

For further information see [[Update and Migration Working Group]]

====Web Services Working Group====

* Coordinator: Ashwin Date (mailto:coolbung@gmail.com)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Web Services Working Group]]

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Production Working Groups

2012-11-14T23:05:38Z

Sueter: /* Database Working Group */

{{RightTOC}}
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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

=Production Working Groups=
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.

==Permanent Working Groups (Teams)==
====Bug Squad====
For further information see the [[Portal:Bug Squad|Bug Squad]] Portal.

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Documentation Working Group====
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

====Joomla Security Strike Team====
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Translations Working Group====
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

====User Experience Working Group====
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

==Current Working Groups==
====Database Working Group====
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Internet of Things Working Group====
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

====JavaScript Working Group====

* Coordinator: Joe LeBlanc
* PLT Contact: Andy Tarr (mailto:andrea.tarr@joomla.org)

For further information see [[JavaScript Working Group]]

====Multi-site Working Group====

* Coordinator: Christophe Demko (mailto:christophe.demko@joomla.org).
* PLT Contact: Christophe Demko (mailto:christophe.demko@joomla.org).

For further information see [[Multi-site Working Group]]

====Message Queue Working Group====

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see: [[Message Queue Working Group]].

====Search Working Group====
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: To be determined.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

====Unified Content Model Working Group====
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: To be determined.
* PLT Contact: To be determined.

For further information see [[Unified Content Model Working Group]]

====Unit Tests for CMS Working Group====

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

====Update and Migration Working Group====
The Update and Migration Working Group looks to solve the immediate problem of Joomla 1.5 to 2.5+ core migration with extensibility to extensions of all types.

* Coordinator: Robert Jacobi (mailto:robert.jacobi@arctg.com)
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org)

For further information see [[Update and Migration Working Group]]

====Web Services Working Group====

* Coordinator: Ashwin Date (mailto:coolbung@gmail.com)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Web Services Working Group]]

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Production Working Groups

2012-11-14T23:05:10Z

Sueter: /* Database Working Group */

{{RightTOC}}
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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

=Production Working Groups=
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.

==Permanent Working Groups (Teams)==
====Bug Squad====
For further information see the [[Portal:Bug Squad|Bug Squad]] Portal.

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Documentation Working Group====
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

====Joomla Security Strike Team====
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

====Translations Working Group====
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

====User Experience Working Group====
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

==Current Working Groups==
====Database Working Group====
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

====Internet of Things Working Group====
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

====JavaScript Working Group====

* Coordinator: Joe LeBlanc
* PLT Contact: Andy Tarr (mailto:andrea.tarr@joomla.org)

For further information see [[JavaScript Working Group]]

====Multi-site Working Group====

* Coordinator: Christophe Demko (mailto:christophe.demko@joomla.org).
* PLT Contact: Christophe Demko (mailto:christophe.demko@joomla.org).

For further information see [[Multi-site Working Group]]

====Message Queue Working Group====

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see: [[Message Queue Working Group]].

====Search Working Group====
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: To be determined.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

====Unified Content Model Working Group====
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: To be determined.
* PLT Contact: To be determined.

For further information see [[Unified Content Model Working Group]]

====Unit Tests for CMS Working Group====

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

====Update and Migration Working Group====
The Update and Migration Working Group looks to solve the immediate problem of Joomla 1.5 to 2.5+ core migration with extensibility to extensions of all types.

* Coordinator: Robert Jacobi (mailto:robert.jacobi@arctg.com)
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org)

For further information see [[Update and Migration Working Group]]

====Web Services Working Group====

* Coordinator: Ashwin Date (mailto:coolbung@gmail.com)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Web Services Working Group]]

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Pizza Bugs and Fun September 15, 2012

2012-09-07T13:49:24Z

Sueter: /* Europe */

[[Image:pbf.png|right]]
{{RightTOC}}

We are announcing a Joomla! Pizza, Bugs and Fun event scheduled for Saturday, September 15, 2012. The event is global for virtual participants with local venues wherever they are organized. Joomla 3 is scheduled to be released on September 27th, so hopefully this Bug Squish will play a big part in squashing the remaining bugs.

This is also a birthday celebration for Joomla! so it's actually a Pizza Bugs Birthday Cake and Fun event. Be sure to add birthday cake, ice cream or stroopwafels to your party!

'''See the section [http://docs.joomla.org/Pizza_Bugs_and_Fun_September_15,_2012#General_Instructions General Instructions] below for instructions.'''

This wiki will be used as the central resource for coordinating efforts and accumulating results from this event.

The '''twitter''' hash tag is #jpbf12.

== Goals ==

* '''Bugs''' : We will be working through the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] where there are bug reports needing patches and/or testing.

* '''Documentation''' : We still have documentation that needs to be done. If you want to help out writing documentation, you're also more than welcome.

== Organization, logistics and communications ==

=== Communication ===
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only and you are all invited. This is the same chat we used for the PBF in March. To get an invitation, email your Skype name to Andy Tarr (andrea.tarr@joomla.org). To make sure you can get in, get your invitation and log in before the day of the PBF. This Skype chat will be in English, but other languages can set up their own chat groups as well.

=== General Instructions ===

These instructions may change as we get closer to the event.

==== If you want to test bug fixes (i.e. patches) ====
* Look for issues with a status of Pending. We want at least 2 testers and more on complex issues, so you can test what others have tested already.
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, which means you download the patch from the tracker and apply it to a current SVN copy of Joomla.
* Most of the issues should have test instructions with them.
* Once you have tested, add comments to the tracker on your results. Start your comment with @test so you will get counted in the stats as a tester.
* Note: You don't have to delete the installation folder when you are using the development version of Joomla. This allows you to reinstall just by deleting the configuration.php file.
* Note: See the [http://docs.joomla.org/Pizza_Bug_and_Fun_September_15,_2012#FAQ FAQ] on how to apply a Git pull request as an SVN patch.

===== Helpful Documentation =====
* [[Git for Testers and Trackers]] - We'd recommend beginners to use TortoiseGit
* [[Tortoise SVN]] - This is only if you're using SVN. We'd recommend using Git instead (see above) though.

==== If you want to code bug fixes ====
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, looking for the issues with a status of Confirmed.
* When you have a patch, add it to the tracker and change the status to Pending if you are able to. Add testing instructions if they don't already exist.

* If you want to just put your toe in the water at first, you could see if any of the older patches with a Pending status need updating to the newest build. When you find one that won't apply, you can manually apply it as necessary and then recreate the patch. Uploading to the tracker as a later version and note that you've updated it to the current build. Just make sure that you are using Unix End of Line and create that patch at the project level.

Helpful documentation:
* [[Setting up your workstation for Joomla! development]]. A step-by-step guide to installing the Eclipse IDE on your local workstation for Joomla! development.
* [http://community.joomla.org/blogs/community/828-webinar-using-eclipse-for-joomla-development.html Using Eclipse for Joomla! Development] Video webinar demonstrating overview of Eclipse features for Joomla! development
* [[Git for Testers and Trackers]]
* [[Working with git and github/My first pull request]]
* [[Secure coding guidelines]]
* [[Development Best Practices]]

==== If you want to work on Documentation ====
* To edit this Documentation Wiki, you will need a user account on the wiki. If you don't already have one, you may register on [[Special:UserLogin]]. You only need a valid email address and once registered you will have immediate permission to edit any page except for a few that are protected because they are high profile spam targets.
* Get your user account a few days before and make sure that you are able to sign in since the automatic authorization system can lock some people out.
* If you'd like something to be edited, but you're not sure what to write exactly, use talk pages to add comments to pages.
* During the PBF, several experienced Wiki editors will be available in the Skype chat to help you.

You are free to work on any aspect of the documentation that takes your fancy, but here are some suggestions for stuff that really needs some love and attention:
* Help screens for Joomla 3.0.
*: I would suggest you pick a particular part of the help screens and propagate that through all the help screens, rather than trying to complete a single help screen. For example, make sure every page has an up-to-date screenshot or make sure every page has a correct and up-to-date description, and so on. [[Help30:Help screens]] is a complete list of all the help screens.
* [[Getting Started with Joomla!]]
* [[Administrators]]
*: The plan is for this page to become the entry point into a comprehensive, task-orientated Administrators Manual. As you can see, there are plenty of gaps that need filling, so please fill away :P
* [[Secure coding guidelines]]
*: This needs to be updated, or perhaps a new version created, following the introduction of JInput and the deprecation of JRequest.
* [[Developers]]
*: A re-organisation of the [[Developers]] page is long overdue and suggestions are welcome. Rather than editing this page directly, I would suggest adding a new sub-page under your user page (eg. [[User:Jane Doe/Developers]] so that it can be reviewed and improved before committing a major change to this important page).

=== Pizza ===
We are offering pizza (or any comparable locally popular main course) and soda for pre-registered groups. Be sure to also get some birthday cake to celebrate Joomla's birthday. We are not setting a specific maximum, but please don’t go crazy with it. Get enough so there’s plenty for everyone, but not a week’s worth of pizza and soda leftovers for everyone. Contact Andrea Tarr (andrea.tarr@joomla.org) before the event to register and get details.

== Locations ==

If you want to get people together and have a venue to share, please add it below. Share as much as possible details like exact location, url for more information about the venue, ways to register, date and time the venue is available etc.

If you set up a location please send contact information to Andy Tarr (andrea.tarr@joomla.org). Feel free to contact her with any questions.

===Virtual===
====Skype Chat====
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only. This is the same Skype chat we used in March. To get an invitation, email your Skype name to Andy Tarr (andrea.tarr@joomla.org). To make sure you can get in, get your invitation and log in before the day of the PBF.

If you don't already have Skype, you can download it for free from [http://skype.com Skype].

=== Europe ===
[http://www.joomla.fr/actualites-de-joomlaorg/session-pizza-bugs-and-fun-2012-participez-a-la-stabilisation-de-joomla-30 Joomla User Group France]
B5Prod agency
31 rue des Tuiliers
69008 Lyon
10:00 - 18:00 GMT
Contact: [mailto:marc.studer@joomla.fr Marc Studer]

[http://www.joomla.fr/les-news-joomla/31-evenements-francophones/1143-session-pizza-bugs-and-fun-2012-participez-a-la-stabilisation-de-joomla-25 Joomla User Group France]
Le Node
12 rue des Faussets
33100 Bordeaux
9:00 - 18:00 GMT
Contact: [mailto:eric.lamy@joomla.fr Eric Lamy]

=== North America ===

=== South America ===

=== Asia/Pacific ===

=== Africa ===

=== Middle East ===

== Registration ==
=== For write access to this wiki ===
To get write access to this wiki you will need to [[Special:Userlogin|register here first]]. Please be aware that the registration process requires a valid email address. This is the same login for updating Joomla documentation.

=== At a physical location ===
If you wish to be present at one of the physical locations listed above then you must register in advance because space most likely is limited. Registrations are the responsibility of the individual location organizers and you should click on the appropriate link above for more information.

=== Taking bugs, tasks and pizza ===

Please check the [http://docs.joomla.org/Pizza_Bug_and_Fun_September_15,_2012#Organization.2C_logistics_and_communications Organization, logistics and communications section] for details on how to get involved in working on tasks.

==Requirements==
* All code must be made available under the [http://www.gnu.org/licenses/gpl-2.0.html General Public Licence version 2].
* All documentation contributions must be made available under the [[JEDL|Joomla! Electronic Documentation License]]. Further information on the JEDL is available in the [[JEDL/FAQ|JEDL Frequently Asked Questions]]
* No advertising or self-promotion will be allowed. This includes back links to your website or anyone else's. The one exception is that if you have made a contribution then feel free to add your name and an optional link to your website to the [[Pizza Bugs and Fun September 15, 2012/Contributors List|Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British English.

== FAQ ==
Q: Where is the code for Joomla?

A: The current Joomla code can be found either on Joomlacode or GitHub.

*GitHub - https://github.com/joomla/joomla-cms
*SVN - http://joomlacode.org/svn/joomla/development/trunk

Q: Which one is 3.0?

A: On GitHub, it is the master branch. For SVN, it is the main trunk.

Q: Any known issues with JForge and Chrome on Windows?

A: It have been seen that browsing the JForge tracker, Chrome may ask for a missing plugin (windows media player). No workaround for this is yet known.

Q: How do I apply a Git pull request as an SVN Patch?

A: Git & SVN are two different ways of doing version control for software. Joomla is in a transition stage of moving from SVN to Git. Many of the patches will be SVN patches which you'll find in the files tab at the bottom of the tracker. Some trackers will have Git "pull requests" instead.

These git pull requests can still usually be applied like SVN patches if you only have SVN. Take the URL of the pull request, add ".patch" to the end of it and use that as a URL to the patch.

[[Image:eclipse-pull-request-1.png]]

Many of this pull requests will also have extra folders on the internal file names like a/ and b/.

[[Image:eclipse-pull-request-3.png]]

In Eclipse, to remove those automatically, change Ignore Leading Path Name Segments to 1.

[[Image:eclipse-pull-request-2.png]]

==Contributors==
{{:Pizza Bugs and Fun September 15, 2012/Contributors List}}

<noinclude>[[Category:Bug Squad]]
[[Category:Development]][[Category:Events]]</noinclude>

Pizza Bugs and Fun September 15, 2012

2012-09-07T03:51:04Z

Sueter: /* Europe */

[[Image:pbf.png|right]]
{{RightTOC}}

We are announcing a Joomla! Pizza, Bugs and Fun event scheduled for Saturday, September 15, 2012. The event is global for virtual participants with local venues wherever they are organized. Joomla 3 is scheduled to be released on September 27th, so hopefully this Bug Squish will play a big part in squashing the remaining bugs.

This is also a birthday celebration for Joomla! so it's actually a Pizza Bugs Birthday Cake and Fun event. Be sure to add birthday cake, ice cream or stroopwafels to your party!

'''See the section [http://docs.joomla.org/Pizza_Bugs_and_Fun_September_15,_2012#General_Instructions General Instructions] below for instructions.'''

This wiki will be used as the central resource for coordinating efforts and accumulating results from this event.

The '''twitter''' hash tag is #jpbf12.

== Goals ==

* '''Bugs''' : We will be working through the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] where there are bug reports needing patches and/or testing.

* '''Documentation''' : We still have documentation that needs to be done. If you want to help out writing documentation, you're also more than welcome.

== Organization, logistics and communications ==

=== Communication ===
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only and you are all invited. This is the same chat we used for the PBF in March. To get an invitation, email your Skype name to Andy Tarr (andrea.tarr@joomla.org). To make sure you can get in, get your invitation and log in before the day of the PBF. This Skype chat will be in English, but other languages can set up their own chat groups as well.

=== General Instructions ===

These instructions may change as we get closer to the event.

==== If you want to test bug fixes (i.e. patches) ====
* Look for issues with a status of Pending. We want at least 2 testers and more on complex issues, so you can test what others have tested already.
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, which means you download the patch from the tracker and apply it to a current SVN copy of Joomla.
* Most of the issues should have test instructions with them.
* Once you have tested, add comments to the tracker on your results. Start your comment with @test so you will get counted in the stats as a tester.
* Note: You don't have to delete the installation folder when you are using the development version of Joomla. This allows you to reinstall just by deleting the configuration.php file.
* Note: See the [http://docs.joomla.org/Pizza_Bug_and_Fun_September_15,_2012#FAQ FAQ] on how to apply a Git pull request as an SVN patch.

===== Helpful Documentation =====
* [[Git for Testers and Trackers]] - We'd recommend beginners to use TortoiseGit
* [[Tortoise SVN]] - This is only if you're using SVN. We'd recommend using Git instead (see above) though.

==== If you want to code bug fixes ====
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, looking for the issues with a status of Confirmed.
* When you have a patch, add it to the tracker and change the status to Pending if you are able to. Add testing instructions if they don't already exist.

* If you want to just put your toe in the water at first, you could see if any of the older patches with a Pending status need updating to the newest build. When you find one that won't apply, you can manually apply it as necessary and then recreate the patch. Uploading to the tracker as a later version and note that you've updated it to the current build. Just make sure that you are using Unix End of Line and create that patch at the project level.

Helpful documentation:
* [[Setting up your workstation for Joomla! development]]. A step-by-step guide to installing the Eclipse IDE on your local workstation for Joomla! development.
* [http://community.joomla.org/blogs/community/828-webinar-using-eclipse-for-joomla-development.html Using Eclipse for Joomla! Development] Video webinar demonstrating overview of Eclipse features for Joomla! development
* [[Git for Testers and Trackers]]
* [[Working with git and github/My first pull request]]
* [[Secure coding guidelines]]
* [[Development Best Practices]]

==== If you want to work on Documentation ====
* To edit this Documentation Wiki, you will need a user account on the wiki. If you don't already have one, you may register on [[Special:UserLogin]]. You only need a valid email address and once registered you will have immediate permission to edit any page except for a few that are protected because they are high profile spam targets.
* Get your user account a few days before and make sure that you are able to sign in since the automatic authorization system can lock some people out.
* If you'd like something to be edited, but you're not sure what to write exactly, use talk pages to add comments to pages.
* During the PBF, several experienced Wiki editors will be available in the Skype chat to help you.

You are free to work on any aspect of the documentation that takes your fancy, but here are some suggestions for stuff that really needs some love and attention:
* Help screens for Joomla 3.0.
*: I would suggest you pick a particular part of the help screens and propagate that through all the help screens, rather than trying to complete a single help screen. For example, make sure every page has an up-to-date screenshot or make sure every page has a correct and up-to-date description, and so on. [[Help30:Help screens]] is a complete list of all the help screens.
* [[Getting Started with Joomla!]]
* [[Administrators]]
*: The plan is for this page to become the entry point into a comprehensive, task-orientated Administrators Manual. As you can see, there are plenty of gaps that need filling, so please fill away :P
* [[Secure coding guidelines]]
*: This needs to be updated, or perhaps a new version created, following the introduction of JInput and the deprecation of JRequest.
* [[Developers]]
*: A re-organisation of the [[Developers]] page is long overdue and suggestions are welcome. Rather than editing this page directly, I would suggest adding a new sub-page under your user page (eg. [[User:Jane Doe/Developers]] so that it can be reviewed and improved before committing a major change to this important page).

=== Pizza ===
We are offering pizza (or any comparable locally popular main course) and soda for pre-registered groups. Be sure to also get some birthday cake to celebrate Joomla's birthday. We are not setting a specific maximum, but please don’t go crazy with it. Get enough so there’s plenty for everyone, but not a week’s worth of pizza and soda leftovers for everyone. Contact Andrea Tarr (andrea.tarr@joomla.org) before the event to register and get details.

== Locations ==

If you want to get people together and have a venue to share, please add it below. Share as much as possible details like exact location, url for more information about the venue, ways to register, date and time the venue is available etc.

If you set up a location please send contact information to Andy Tarr (andrea.tarr@joomla.org). Feel free to contact her with any questions.

===Virtual===
====Skype Chat====
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only. This is the same Skype chat we used in March. To get an invitation, email your Skype name to Andy Tarr (andrea.tarr@joomla.org). To make sure you can get in, get your invitation and log in before the day of the PBF.

If you don't already have Skype, you can download it for free from [http://skype.com Skype].

=== Europe ===
[http://www.joomla.fr/actualites-de-joomlaorg/session-pizza-bugs-and-fun-2012-participez-a-la-stabilisation-de-joomla-30 Joomla User Group France]
B5Prod agency
31 rue des Tuiliers
69008 Lyon
10:00 - 18:00 GMT
Contact: [mailto:marc.studer@joomla.fr Marc Studer]

[http://www.joomla.fr/les-news-joomla/31-evenements-francophones/1143-session-pizza-bugs-and-fun-2012-participez-a-la-stabilisation-de-joomla-25 Joomla User Group France]
Agerix agency
25 rue Fernand Belliard
33100 Bordeaux
9:00 - 18:00 GMT
Contact: [mailto:eric.lamy@joomla.fr Eric Lamy]

=== North America ===

=== South America ===

=== Asia/Pacific ===

=== Africa ===

=== Middle East ===

== Registration ==
=== For write access to this wiki ===
To get write access to this wiki you will need to [[Special:Userlogin|register here first]]. Please be aware that the registration process requires a valid email address. This is the same login for updating Joomla documentation.

=== At a physical location ===
If you wish to be present at one of the physical locations listed above then you must register in advance because space most likely is limited. Registrations are the responsibility of the individual location organizers and you should click on the appropriate link above for more information.

=== Taking bugs, tasks and pizza ===

Please check the [http://docs.joomla.org/Pizza_Bug_and_Fun_September_15,_2012#Organization.2C_logistics_and_communications Organization, logistics and communications section] for details on how to get involved in working on tasks.

==Requirements==
* All code must be made available under the [http://www.gnu.org/licenses/gpl-2.0.html General Public Licence version 2].
* All documentation contributions must be made available under the [[JEDL|Joomla! Electronic Documentation License]]. Further information on the JEDL is available in the [[JEDL/FAQ|JEDL Frequently Asked Questions]]
* No advertising or self-promotion will be allowed. This includes back links to your website or anyone else's. The one exception is that if you have made a contribution then feel free to add your name and an optional link to your website to the [[Pizza Bugs and Fun September 15, 2012/Contributors List|Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British English.

== FAQ ==
Q: Where is the code for Joomla?

A: The current Joomla code can be found either on Joomlacode or GitHub.

*GitHub - https://github.com/joomla/joomla-cms
*SVN - http://joomlacode.org/svn/joomla/development/trunk

Q: Which one is 3.0?

A: On GitHub, it is the master branch. For SVN, it is the main trunk.

Q: Any known issues with JForge and Chrome on Windows?

A: It have been seen that browsing the JForge tracker, Chrome may ask for a missing plugin (windows media player). No workaround for this is yet known.

Q: How do I apply a Git pull request as an SVN Patch?

A: Git & SVN are two different ways of doing version control for software. Joomla is in a transition stage of moving from SVN to Git. Many of the patches will be SVN patches which you'll find in the files tab at the bottom of the tracker. Some trackers will have Git "pull requests" instead.

These git pull requests can still usually be applied like SVN patches if you only have SVN. Take the URL of the pull request, add ".patch" to the end of it and use that as a URL to the patch.

[[Image:eclipse-pull-request-1.png]]

Many of this pull requests will also have extra folders on the internal file names like a/ and b/.

[[Image:eclipse-pull-request-3.png]]

In Eclipse, to remove those automatically, change Ignore Leading Path Name Segments to 1.

[[Image:eclipse-pull-request-2.png]]

==Contributors==
{{:Pizza Bugs and Fun September 15, 2012/Contributors List}}

<noinclude>[[Category:Bug Squad]]
[[Category:Development]][[Category:Events]]</noinclude>

Pizza Bugs and Fun September 15, 2012

2012-09-04T03:44:42Z

Sueter:

[[Category:Bug Squad]]
[[Category:Development]]
[[Image:pbf.png|right]]
{{RightTOC}}

We are announcing a Joomla! Pizza, Bugs and Fun event scheduled for Saturday, September 15, 2012. The event is global for virtual participants with local venues wherever they are organized. Joomla 3 is scheduled to be released on September 27th, so hopefully this Bug Squish will play a big part in squashing the remaining bugs.

This is also a birthday celebration for Joomla! so it's actually a Pizza Bugs Birthday Cake and Fun event. Be sure to add birthday cake, ice cream or stroopwafels to your party!

'''See the section [http://docs.joomla.org/Pizza_Bugs_and_Fun_September_15,_2012#General_Instructions General Instructions] below for instructions.'''

This wiki will be used as the central resource for coordinating efforts and accumulating results from this event.

The '''twitter''' hash tag is #jpbf12.

== Goals ==

* '''Bugs''' : We will be working through the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] where there are bug reports needing patches and/or testing.

* '''Documentation''' : We still have documentation that needs to be done. If you want to help out writing documentation, you're also more than welcome.

== Organization, logistics and communications ==

=== Communication ===
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only and you are all invited. This is the same chat we used for the PBF in March. To get an invitation, email your Skype name to Andy Tarr (andrea.tarr@joomla.org). To make sure you can get in, get your invitation and log in before the day of the PBF. This Skype chat will be in English, but other languages can set up their own chat groups as well.

=== General Instructions ===

These instructions may change as we get closer to the event.

==== If you want to test bug fixes (i.e. patches) ====
* Look for issues with a status of Pending. We want at least 2 testers and more on complex issues, so you can test what others have tested already.
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, which means you download the patch from the tracker and apply it to a current SVN copy of Joomla.
* Most of the issues should have test instructions with them.
* Once you have tested, add comments to the tracker on your results. Start your comment with @test so you will get counted in the stats as a tester.
* Note: You don't have to delete the installation folder when you are using the development version of Joomla. This allows you to reinstall just by deleting the configuration.php file.
* Note: See the [http://docs.joomla.org/Pizza_Bug_and_Fun_September_15,_2012#FAQ FAQ] on how to apply a Git pull request as an SVN patch.

===== Helpful Documentation =====
* [[Git for Testers and Trackers]] - We'd recommend beginners to use TortoiseGit
* [[Tortoise SVN]] - This is only if you're using SVN. We'd recommend using Git instead (see above) though.

==== If you want to code bug fixes ====
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, looking for the issues with a status of Confirmed.
* When you have a patch, add it to the tracker and change the status to Pending if you are able to. Add testing instructions if they don't already exist.

* If you want to just put your toe in the water at first, you could see if any of the older patches with a Pending status need updating to the newest build. When you find one that won't apply, you can manually apply it as necessary and then recreate the patch. Uploading to the tracker as a later version and note that you've updated it to the current build. Just make sure that you are using Unix End of Line and create that patch at the project level.

Helpful documentation:
* [[Setting up your workstation for Joomla! development]]. A step-by-step guide to installing the Eclipse IDE on your local workstation for Joomla! development.
* [http://community.joomla.org/blogs/community/828-webinar-using-eclipse-for-joomla-development.html Using Eclipse for Joomla! Development] Video webinar demonstrating overview of Eclipse features for Joomla! development
* [[Git for Testers and Trackers]]
* [[Working with git and github/My first pull request]]
* [[Secure coding guidelines]]
* [[Development Best Practices]]

==== If you want to work on Documentation ====
* To edit this Documentation Wiki, you will need a user account on the wiki. If you don't already have one, you may register on [[Special:UserLogin]]. You only need a valid email address and once registered you will have immediate permission to edit any page except for a few that are protected because they are high profile spam targets.
* Get your user account a few days before and make sure that you are able to sign in since the automatic authorization system can lock some people out.
* If you'd like something to be edited, but you're not sure what to write exactly, use talk pages to add comments to pages.
* During the PBF, several experienced Wiki editors will be available in the Skype chat to help you.

You are free to work on any aspect of the documentation that takes your fancy, but here are some suggestions for stuff that really needs some love and attention:
* Help screens for Joomla 3.0.
*: I would suggest you pick a particular part of the help screens and propagate that through all the help screens, rather than trying to complete a single help screen. For example, make sure every page has an up-to-date screenshot or make sure every page has a correct and up-to-date description, and so on. [[Help30:Help screens]] is a complete list of all the help screens.
* [[Getting Started with Joomla!]]
* [[Administrators]]
*: The plan is for this page to become the entry point into a comprehensive, task-orientated Administrators Manual. As you can see, there are plenty of gaps that need filling, so please fill away :P
* [[Secure coding guidelines]]
*: This needs to be updated, or perhaps a new version created, following the introduction of JInput and the deprecation of JRequest.
* [[Developers]]
*: A re-organisation of the [[Developers]] page is long overdue and suggestions are welcome. Rather than editing this page directly, I would suggest adding a new sub-page under your user page (eg. [[User:Jane Doe/Developers]] so that it can be reviewed and improved before committing a major change to this important page).

=== Pizza ===
We are offering pizza (or any comparable locally popular main course) and soda for pre-registered groups. Be sure to also get some birthday cake to celebrate Joomla's birthday. We are not setting a specific maximum, but please don’t go crazy with it. Get enough so there’s plenty for everyone, but not a week’s worth of pizza and soda leftovers for everyone. Contact Andrea Tarr (andrea.tarr@joomla.org) before the event to register and get details.

== Locations ==

If you want to get people together and have a venue to share, please add it below. Share as much as possible details like exact location, url for more information about the venue, ways to register, date and time the venue is available etc.

If you set up a location please send contact information to Andy Tarr (andrea.tarr@joomla.org). Feel free to contact her with any questions.

===Virtual===
====Skype Chat====
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only. This is the same Skype chat we used in March. To get an invitation, email your Skype name to Andy Tarr (andrea.tarr@joomla.org). To make sure you can get in, get your invitation and log in before the day of the PBF.

If you don't already have Skype, you can download it for free from [http://skype.com Skype].

=== Europe ===

=== North America ===

=== South America ===

=== Asia/Pacific ===

=== Africa ===

=== Middle East ===

== Registration ==
=== For write access to this wiki ===
To get write access to this wiki you will need to [[Special:Userlogin|register here first]]. Please be aware that the registration process requires a valid email address. This is the same login for updating Joomla documentation.

=== At a physical location ===
If you wish to be present at one of the physical locations listed above then you must register in advance because space most likely is limited. Registrations are the responsibility of the individual location organizers and you should click on the appropriate link above for more information.

=== Taking bugs, tasks and pizza ===

Please check the [http://docs.joomla.org/Pizza_Bug_and_Fun_September_15,_2012#Organization.2C_logistics_and_communications Organization, logistics and communications section] for details on how to get involved in working on tasks.

==Requirements==
* All code must be made available under the [http://www.gnu.org/licenses/gpl-2.0.html General Public Licence version 2].
* All documentation contributions must be made available under the [[JEDL|Joomla! Electronic Documentation License]]. Further information on the JEDL is available in the [[JEDL/FAQ|JEDL Frequently Asked Questions]]
* No advertising or self-promotion will be allowed. This includes back links to your website or anyone else's. The one exception is that if you have made a contribution then feel free to add your name and an optional link to your website to the [[Pizza Bugs and Fun September 15, 2012/Contributors List|Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British English.

== FAQ ==
Q: Where is the code for Joomla?

A: The current Joomla code can be found either on Joomlacode or GitHub.

*GitHub - https://github.com/joomla/joomla-cms
*SVN - http://joomlacode.org/svn/joomla/development/trunk

Q: Which one is 3.0?

A: On GitHub, it is the master branch. For SVN, it is the main trunk.

Q: Any known issues with JForge and Chrome on Windows?

A: It have been seen that browsing the JForge tracker, Chrome may ask for a missing plugin (windows media player). No workaround for this is yet known.

Q: How do I apply a Git pull request as an SVN Patch?

A: Git & SVN are two different ways of doing version control for software. Joomla is in a transition stage of moving from SVN to Git. Many of the patches will be SVN patches which you'll find in the files tab at the bottom of the tracker. Some trackers will have Git "pull requests" instead.

These git pull requests can still usually be applied like SVN patches if you only have SVN. Take the URL of the pull request, add ".patch" to the end of it and use that as a URL to the patch.

[[Image:eclipse-pull-request-1.png]]

Many of this pull requests will also have extra folders on the internal file names like a/ and b/.

[[Image:eclipse-pull-request-3.png]]

In Eclipse, to remove those automatically, change Ignore Leading Path Name Segments to 1.

[[Image:eclipse-pull-request-2.png]]

==Contributors==
{{:Pizza Bugs and Fun September 15, 2012/Contributors List}}

Pizza Bug and Fun September 15, 2012

2012-09-04T03:37:38Z

Sueter: Replaced content with " See Pizza Bugs and Fun September 15, 2012"

See [[Pizza Bugs and Fun September 15, 2012]]

Pizza Bugs and Fun September 15, 2012

2012-09-04T03:30:22Z

Sueter: Created page with "Category:Bug Squad Category:Development right {{RightTOC}} We are announcing a Joomla! Pizza, Bugs and Fun event scheduled for Saturday, September 1..."

[[Category:Bug Squad]]
[[Category:Development]]
[[Image:pbf.png|right]]
{{RightTOC}}

We are announcing a Joomla! Pizza, Bugs and Fun event scheduled for Saturday, September 15, 2012. The event is global for virtual participants with local venues wherever they are organized. Joomla 3 is scheduled to be released on September 26th, so hopefully this Bug Squish will play a big part in squashing the remaining bugs.

'''See the section [http://docs.joomla.org/Pizza_Bugs_and_Fun_September_15,_2012#General_Instructions General Instructions] below for instructions.'''

This wiki will be used as the central resource for coordinating efforts and accumulating results from this event.

The '''twitter''' hash tag is #jpbf12.

== Goals ==

* '''Bugs''' : We will be working through the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] where there are bug reports needing patches and/or testing.

* '''Documentation''' : We still have documentation that needs to be done. If you want to help out writing documentation, you're also more than welcome.

== Organization, logistics and communications ==

=== Communication ===
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only and you are all invited. This is the same chat we used for the PBF in March. To get an invitation, email your Skype name to Andy Tarr (andrea.tarr@joomla.org). To make sure you can get in, get your invitation and log in before the day of the PBF. This Skype chat will be in English, but other languages can set up their own chat groups as well.

=== General Instructions ===

These instructions may change as we get closer to the event.

==== If you want to test bug fixes (i.e. patches) ====
* Look for issues with a status of Pending. We want at least 2 testers and more on complex issues, so you can test what others have tested already.
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, which means you download the patch from the tracker and apply it to a current SVN copy of Joomla.
* Most of the issues should have test instructions with them.
* Once you have tested, add comments to the tracker on your results. Start your comment with @test so you will get counted in the stats as a tester.
* Note: You don't have to delete the installation folder when you are using the development version of Joomla. This allows you to reinstall just by deleting the configuration.php file.
* Note: See the [http://docs.joomla.org/Pizza_Bug_and_Fun_September_15,_2012#FAQ FAQ] on how to apply a Git pull request as an SVN patch.

===== Helpful Documentation =====
* [[Git for Testers and Trackers]] - We'd recommend beginners to use TortoiseGit
* [[Tortoise SVN]] - This is only if you're using SVN. We'd recommend using Git instead (see above) though.

==== If you want to code bug fixes ====
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, looking for the issues with a status of Confirmed.
* When you have a patch, add it to the tracker and change the status to Pending if you are able to. Add testing instructions if they don't already exist.

* If you want to just put your toe in the water at first, you could see if any of the older patches with a Pending status need updating to the newest build. When you find one that won't apply, you can manually apply it as necessary and then recreate the patch. Uploading to the tracker as a later version and note that you've updated it to the current build. Just make sure that you are using Unix End of Line and create that patch at the project level.

Helpful documentation:
* [[Setting up your workstation for Joomla! development]]. A step-by-step guide to installing the Eclipse IDE on your local workstation for Joomla! development.
* [http://community.joomla.org/blogs/community/828-webinar-using-eclipse-for-joomla-development.html Using Eclipse for Joomla! Development] Video webinar demonstrating overview of Eclipse features for Joomla! development
* [[Git for Testers and Trackers]]
* [[Working with git and github/My first pull request]]
* [[Secure coding guidelines]]
* [[Development Best Practices]]

==== If you want to work on Documentation ====
* To edit this Documentation Wiki, you will need a user account on the wiki. If you don't already have one, you may register on [[Special:UserLogin]]. You only need a valid email address and once registered you will have immediate permission to edit any page except for a few that are protected because they are high profile spam targets.
* Get your user account a few days before and make sure that you are able to sign in since the automatic authorization system can lock some people out.
* If you'd like something to be edited, but you're not sure what to write exactly, use talk pages to add comments to pages.
* During the PBF, several experienced Wiki editors will be available in the Skype chat to help you.

You are free to work on any aspect of the documentation that takes your fancy, but here are some suggestions for stuff that really needs some love and attention:
* Help screens for Joomla 3.0.
*: I would suggest you pick a particular part of the help screens and propagate that through all the help screens, rather than trying to complete a single help screen. For example, make sure every page has an up-to-date screenshot or make sure every page has a correct and up-to-date description, and so on. [[Help30:Help screens]] is a complete list of all the help screens.
* [[Getting Started with Joomla!]]
* [[Administrators]]
*: The plan is for this page to become the entry point into a comprehensive, task-orientated Administrators Manual. As you can see, there are plenty of gaps that need filling, so please fill away :P
* [[Secure coding guidelines]]
*: This needs to be updated, or perhaps a new version created, following the introduction of JInput and the deprecation of JRequest.
* [[Developers]]
*: A re-organisation of the [[Developers]] page is long overdue and suggestions are welcome. Rather than editing this page directly, I would suggest adding a new sub-page under your user page (eg. [[User:Jane Doe/Developers]] so that it can be reviewed and improved before committing a major change to this important page).

=== Pizza ===
We are offering pizza and soda for pre-registered groups. We are not setting a specific maximum, but please don’t go crazy with it. Get enough so there’s plenty for everyone, but not a week’s worth of pizza and soda leftovers for everyone. Contact Andrea Tarr (andrea.tarr@joomla.org) before the event to register and get details.

== Locations ==

If you want to get people together and have a venue to share, please add it below. Share as much as possible details like exact location, url for more information about the venue, ways to register, date and time the venue is available etc.

If you set up a location please send contact information to Andy Tarr (andrea.tarr@joomla.org). Feel free to contact her with any questions.

===Virtual===
====Skype Chat====
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only. This is the same Skype chat we used in March. To get an invitation, email your Skype name to Andy Tarr (andrea.tarr@joomla.org). To make sure you can get in, get your invitation and log in before the day of the PBF.

If you don't already have Skype, you can download it for free from [http://skype.com Skype].

=== Europe ===

=== North America ===

=== South America ===

=== Asia/Pacific ===

=== Africa ===

=== Middle East ===

== Registration ==
=== For write access to this wiki ===
To get write access to this wiki you will need to [[Special:Userlogin|register here first]]. Please be aware that the registration process requires a valid email address. This is the same login for updating Joomla documentation.

=== At a physical location ===
If you wish to be present at one of the physical locations listed above then you must register in advance because space most likely is limited. Registrations are the responsibility of the individual location organizers and you should click on the appropriate link above for more information.

=== Taking bugs, tasks and pizza ===

Please check the [http://docs.joomla.org/Pizza_Bug_and_Fun_September_15,_2012#Organization.2C_logistics_and_communications Organization, logistics and communications section] for details on how to get involved in working on tasks.

==Requirements==
* All code must be made available under the [http://www.gnu.org/licenses/gpl-2.0.html General Public Licence version 2].
* All documentation contributions must be made available under the [[JEDL|Joomla! Electronic Documentation License]]. Further information on the JEDL is available in the [[JEDL/FAQ|JEDL Frequently Asked Questions]]
* No advertising or self-promotion will be allowed. This includes back links to your website or anyone else's. The one exception is that if you have made a contribution then feel free to add your name and an optional link to your website to the [[Pizza Bugs and Fun September 15, 2012/Contributors List|Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British English.

== FAQ ==
Q: Where is the code for Joomla?

A: The current Joomla code can be found either on Joomlacode or GitHub.

*GitHub - https://github.com/joomla/joomla-cms
*SVN - http://joomlacode.org/svn/joomla/development/trunk

Q: Which one is 3.0?

A: On GitHub, it is the master branch. For SVN, it is the main trunk.

Q: Any known issues with JForge and Chrome on Windows?

A: It have been seen that browsing the JForge tracker, Chrome may ask for a missing plugin (windows media player). No workaround for this is yet known.

Q: How do I apply a Git pull request as an SVN Patch?

A: Git & SVN are two different ways of doing version control for software. Joomla is in a transition stage of moving from SVN to Git. Many of the patches will be SVN patches which you'll find in the files tab at the bottom of the tracker. Some trackers will have Git "pull requests" instead.

These git pull requests can still usually be applied like SVN patches if you only have SVN. Take the URL of the pull request, add ".patch" to the end of it and use that as a URL to the patch.

[[Image:eclipse-pull-request-1.png]]

Many of this pull requests will also have extra folders on the internal file names like a/ and b/.

[[Image:eclipse-pull-request-3.png]]

In Eclipse, to remove those automatically, change Ignore Leading Path Name Segments to 1.

[[Image:eclipse-pull-request-2.png]]

==Contributors==
{{:Pizza Bugs and Fun September 15, 2012/Contributors List}}

Pizza, Bugs and Fun

2012-09-04T03:29:43Z

Sueter: /* Pizza Bugs and Fun September 15, 2012 */

==Forthcoming Events==
===Pizza Bugs and Fun September 15, 2012===
[[Pizza_Bugs_and_Fun_September_15,_2012| Pizza Bugs and Fun September 15, 2012]] is planned for Saturday, September 15, 2012. This will be a virtual party with assorted live venues. It's a Joomla! birthday so come celebrate with birthday cake, ice cream or stroopwafels!

==History==
===Pizza Bugs and Fun March 3, 2012===
[[Pizza_Bugs_and_Fun_March_3,_2012| Pizza, Bugs and Fun March 3, 2012]] was held Saturday, March 3, 2012. It was a virtual party with assorted live venues.

===Pizza Bugs and Fun 2011===
[[Pizza_Bugs_and_Fun_2011| Pizza, Bugs and Fun 2011]] is planned for Saturday, December 10, 2011. This will be a virtual party with assorted live venues.

===Pizza Bugs and Fun 2===
Something for everyone at the Joomla! Bazaar: coding, documentation, testing and other fun stuff. This event took place on two consecutive weekends, 21/22 and 28/29 June 2008. For more information see [[Pizza Bugs and Fun 2]].

Pizza Bug and Fun September 15, 2012

2012-09-04T03:27:36Z

Sueter:

[[Category:Bug Squad]]
[[Category:Development]]
[[Image:pbf.png|right]]
{{RightTOC}}

We are announcing a Joomla! Pizza, Bugs and Fun event scheduled for Saturday, September 15, 2012. The event is global for virtual participants with local venues wherever they are organized. Joomla 3 is scheduled to be released on September 26th, so hopefully this Bug Squish will play a big part in squashing the remaining bugs.

'''See the section [http://docs.joomla.org/Pizza_Bugs_and_Fun_September_15,_2012#General_Instructions General Instructions] below for instructions.'''

This wiki will be used as the central resource for coordinating efforts and accumulating results from this event.

The '''twitter''' hash tag is #jpbf12.

== Goals ==

* '''Bugs''' : We will be working through the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] where there are bug reports needing patches and/or testing.

* '''Documentation''' : We still have documentation that needs to be done. If you want to help out writing documentation, you're also more than welcome.

== Organization, logistics and communications ==

=== Communication ===
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only and you are all invited. This is the same chat we used for the PBF in March. To get an invitation, email your Skype name to Andy Tarr (andrea.tarr@joomla.org). To make sure you can get in, get your invitation and log in before the day of the PBF. This Skype chat will be in English, but other languages can set up their own chat groups as well.

=== General Instructions ===

These instructions may change as we get closer to the event.

==== If you want to test bug fixes (i.e. patches) ====
* Look for issues with a status of Pending. We want at least 2 testers and more on complex issues, so you can test what others have tested already.
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, which means you download the patch from the tracker and apply it to a current SVN copy of Joomla.
* Most of the issues should have test instructions with them.
* Once you have tested, add comments to the tracker on your results. Start your comment with @test so you will get counted in the stats as a tester.
* Note: You don't have to delete the installation folder when you are using the development version of Joomla. This allows you to reinstall just by deleting the configuration.php file.
* Note: See the [http://docs.joomla.org/Pizza_Bug_and_Fun_September_15,_2012#FAQ FAQ] on how to apply a Git pull request as an SVN patch.

===== Helpful Documentation =====
* [[Git for Testers and Trackers]] - We'd recommend beginners to use TortoiseGit
* [[Tortoise SVN]] - This is only if you're using SVN. We'd recommend using Git instead (see above) though.

==== If you want to code bug fixes ====
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, looking for the issues with a status of Confirmed.
* When you have a patch, add it to the tracker and change the status to Pending if you are able to. Add testing instructions if they don't already exist.

* If you want to just put your toe in the water at first, you could see if any of the older patches with a Pending status need updating to the newest build. When you find one that won't apply, you can manually apply it as necessary and then recreate the patch. Uploading to the tracker as a later version and note that you've updated it to the current build. Just make sure that you are using Unix End of Line and create that patch at the project level.

Helpful documentation:
* [[Setting up your workstation for Joomla! development]]. A step-by-step guide to installing the Eclipse IDE on your local workstation for Joomla! development.
* [http://community.joomla.org/blogs/community/828-webinar-using-eclipse-for-joomla-development.html Using Eclipse for Joomla! Development] Video webinar demonstrating overview of Eclipse features for Joomla! development
* [[Git for Testers and Trackers]]
* [[Working with git and github/My first pull request]]
* [[Secure coding guidelines]]
* [[Development Best Practices]]

==== If you want to work on Documentation ====
* To edit this Documentation Wiki, you will need a user account on the wiki. If you don't already have one, you may register on [[Special:UserLogin]]. You only need a valid email address and once registered you will have immediate permission to edit any page except for a few that are protected because they are high profile spam targets.
* Get your user account a few days before and make sure that you are able to sign in since the automatic authorization system can lock some people out.
* If you'd like something to be edited, but you're not sure what to write exactly, use talk pages to add comments to pages.
* During the PBF, several experienced Wiki editors will be available in the Skype chat to help you.

You are free to work on any aspect of the documentation that takes your fancy, but here are some suggestions for stuff that really needs some love and attention:
* Help screens for Joomla 3.0.
*: I would suggest you pick a particular part of the help screens and propagate that through all the help screens, rather than trying to complete a single help screen. For example, make sure every page has an up-to-date screenshot or make sure every page has a correct and up-to-date description, and so on. [[Help30:Help screens]] is a complete list of all the help screens.
* [[Getting Started with Joomla!]]
* [[Administrators]]
*: The plan is for this page to become the entry point into a comprehensive, task-orientated Administrators Manual. As you can see, there are plenty of gaps that need filling, so please fill away :P
* [[Secure coding guidelines]]
*: This needs to be updated, or perhaps a new version created, following the introduction of JInput and the deprecation of JRequest.
* [[Developers]]
*: A re-organisation of the [[Developers]] page is long overdue and suggestions are welcome. Rather than editing this page directly, I would suggest adding a new sub-page under your user page (eg. [[User:Jane Doe/Developers]] so that it can be reviewed and improved before committing a major change to this important page).

=== Pizza ===
We are offering pizza and soda for pre-registered groups. We are not setting a specific maximum, but please don’t go crazy with it. Get enough so there’s plenty for everyone, but not a week’s worth of pizza and soda leftovers for everyone. Contact Andrea Tarr (andrea.tarr@joomla.org) before the event to register and get details.

== Locations ==

If you want to get people together and have a venue to share, please add it below. Share as much as possible details like exact location, url for more information about the venue, ways to register, date and time the venue is available etc.

If you set up a location please send contact information to Andy Tarr (andrea.tarr@joomla.org). Feel free to contact her with any questions.

===Virtual===
====Skype Chat====
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only. This is the same Skype chat we used in March. To get an invitation, email your Skype name to Andy Tarr (andrea.tarr@joomla.org). To make sure you can get in, get your invitation and log in before the day of the PBF.

If you don't already have Skype, you can download it for free from [http://skype.com Skype].

=== Europe ===

=== North America ===

=== South America ===

=== Asia/Pacific ===

=== Africa ===

=== Middle East ===

== Registration ==
=== For write access to this wiki ===
To get write access to this wiki you will need to [[Special:Userlogin|register here first]]. Please be aware that the registration process requires a valid email address. This is the same login for updating Joomla documentation.

=== At a physical location ===
If you wish to be present at one of the physical locations listed above then you must register in advance because space most likely is limited. Registrations are the responsibility of the individual location organizers and you should click on the appropriate link above for more information.

=== Taking bugs, tasks and pizza ===

Please check the [http://docs.joomla.org/Pizza_Bug_and_Fun_September_15,_2012#Organization.2C_logistics_and_communications Organization, logistics and communications section] for details on how to get involved in working on tasks.

==Requirements==
* All code must be made available under the [http://www.gnu.org/licenses/gpl-2.0.html General Public Licence version 2].
* All documentation contributions must be made available under the [[JEDL|Joomla! Electronic Documentation License]]. Further information on the JEDL is available in the [[JEDL/FAQ|JEDL Frequently Asked Questions]]
* No advertising or self-promotion will be allowed. This includes back links to your website or anyone else's. The one exception is that if you have made a contribution then feel free to add your name and an optional link to your website to the [[Pizza Bugs and Fun September 15, 2012/Contributors List|Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British English.

== FAQ ==
Q: Where is the code for Joomla?

A: The current Joomla code can be found either on Joomlacode or GitHub.

*GitHub - https://github.com/joomla/joomla-cms
*SVN - http://joomlacode.org/svn/joomla/development/trunk

Q: Which one is 3.0?

A: On GitHub, it is the master branch. For SVN, it is the main trunk.

Q: Any known issues with JForge and Chrome on Windows?

A: It have been seen that browsing the JForge tracker, Chrome may ask for a missing plugin (windows media player). No workaround for this is yet known.

Q: How do I apply a Git pull request as an SVN Patch?

A: Git & SVN are two different ways of doing version control for software. Joomla is in a transition stage of moving from SVN to Git. Many of the patches will be SVN patches which you'll find in the files tab at the bottom of the tracker. Some trackers will have Git "pull requests" instead.

These git pull requests can still usually be applied like SVN patches if you only have SVN. Take the URL of the pull request, add ".patch" to the end of it and use that as a URL to the patch.

[[Image:eclipse-pull-request-1.png]]

Many of this pull requests will also have extra folders on the internal file names like a/ and b/.

[[Image:eclipse-pull-request-3.png]]

In Eclipse, to remove those automatically, change Ignore Leading Path Name Segments to 1.

[[Image:eclipse-pull-request-2.png]]

==Contributors==
{{:Pizza Bugs and Fun September 15, 2012/Contributors List}}

Pizza, Bugs and Fun

2012-09-04T03:24:59Z

Sueter: /* Pizza Bugs and Fun March 3, 2012 */

==Forthcoming Events==
===Pizza Bugs and Fun September 15, 2012===
[[Pizza_Bugs_and_Fun_September_15,_2012| Pizza, Bugs and Fun September 15, 2012]] is planned for Saturday, September 15, 2012. This will be a virtual party with assorted live venues. It's a Joomla! birthday so come celebrate with birthday cake, ice cream or stroopwafels!

==History==
===Pizza Bugs and Fun March 3, 2012===
[[Pizza_Bugs_and_Fun_March_3,_2012| Pizza, Bugs and Fun March 3, 2012]] was held Saturday, March 3, 2012. It was a virtual party with assorted live venues.

===Pizza Bugs and Fun 2011===
[[Pizza_Bugs_and_Fun_2011| Pizza, Bugs and Fun 2011]] is planned for Saturday, December 10, 2011. This will be a virtual party with assorted live venues.

===Pizza Bugs and Fun 2===
Something for everyone at the Joomla! Bazaar: coding, documentation, testing and other fun stuff. This event took place on two consecutive weekends, 21/22 and 28/29 June 2008. For more information see [[Pizza Bugs and Fun 2]].

Pizza, Bugs and Fun

2012-09-04T03:23:17Z

Sueter: /* History */

==Forthcoming Events==
===Pizza Bugs and Fun March 3, 2012===
[[Pizza_Bugs_and_Fun_March_3,_2012| Pizza, Bugs and Fun March 3, 2012]] is planned for Saturday, March 3, 2012. This will be a virtual party with assorted live venues.

==History==
===Pizza Bugs and Fun March 3, 2012===
[[Pizza_Bugs_and_Fun_March_3,_2012| Pizza, Bugs and Fun March 3, 2012]] was held Saturday, March 3, 2012. It was a virtual party with assorted live venues.

===Pizza Bugs and Fun 2011===
[[Pizza_Bugs_and_Fun_2011| Pizza, Bugs and Fun 2011]] is planned for Saturday, December 10, 2011. This will be a virtual party with assorted live venues.

===Pizza Bugs and Fun 2===
Something for everyone at the Joomla! Bazaar: coding, documentation, testing and other fun stuff. This event took place on two consecutive weekends, 21/22 and 28/29 June 2008. For more information see [[Pizza Bugs and Fun 2]].

Potential backward compatibility issues in Joomla 3 and Joomla Platform 12.2

2012-08-24T02:34:08Z

Sueter: /* General changes */

{{incomplete}}{{RightTOC}}This document tracks potential backward compatibility issues for Joomla 3.0 and Joomla Platform 12.1, which is included in Joomla 3.0. Listed are issues which potentially break extensions.
Please help make this document complete.

The base of this comparison is Joomla 2.5/Platform 11.4.

Backwards compatibility issues were also tracked for Joomla 2.5: [[Potential backward compatibility issues in Joomla 2.5 and Joomla Platform 11.4]]

= Platform =
The platform removed a larger number of deprecated classes and methods. For most extensions written for Joomla 2.5, the required changes should be reasonably small. Note that there are still deprecated classes in the platform that will be removed in future versions -- developers should stop using them where possible.

== Updated System Requirements ==
The system requirements have changed in the following points:
*PHP 5.3.1
*register_globals must be off
*magic_quotes_gpc must be off

== General changes ==
*Almost all functions, methods, members and classed marked as deprecated in Platform 11.4 have been removed. They won't be listed in this document.
*Appending ?no_html to an URL to get a RAW view is not supported anymore (this was an old Joomla 1.0 feature).
*The DS constant has been removed. If you really need it you can use DIRECTORY_SEPARATOR instead.
*Many more function arguments have been type hinted, including existing classes. Make sure you're always passing values of the correct type.
*The name of modules now have to start with "mod_".
*Extensions need to set the registeredurlparams now, the fall back on the URL has been removed.
*Some cookies are only accessible through HTTP (not via JavaScript). For example; the session cookie.
*Due to upcoming changes to the MVC implementation in the platform, JModel, JView, and JController are re-used as the names of the new interfaces. For now, use JModelLegacy, JViewLegacy and JControllerLegacy instead.
*JFolder and JFile now require you to do your own jimport statement

== Changes to extension installation ==
*Use of the <install> base tag (from 1.5) is no longer supported; use <extension> instead.
*Suppport for install_script and uninstall_script, and the methods com_install and com_uninstall in these scripts, has been removed; use scriptfile instead.
*In language extensions, support for client="both" has been removed; prepare each client as a separate extension and optionally bundle them as a package extension instead.
*File paths for plugins no longer support the old 1.5 method (i.e. plugins/system/cache.php); each plugin must now be in its own folder (i.e. plugins/system/cache/cache.php).

== Changes to Components ==
*In admin components the admin.*.php and toolbar.*.php are not automatically included anymore (this was a Joomla 1.0 legacy feature).

== Moved files ==
All classes listed here should now be autoloadable. Explicit requires and includes have to be modified or removed.

=== Classes moved to the CMS ===
*JFormFieldHelpsite
*JFormFieldMedia
*JFormFieldMenuitem
*JFormFieldUser
*JHelp
*JTableContent

=== Classes moved within the platform ===
*JDatabaseQuery subclasses
*JInput (and all subclasses)
*JTable (and all subclasses)
*JArchive (and all subclasses)

== Renamed classes ==
*JFTP is now called JClientFtp
*JLDAP is now called JClientLdap
*JWebClient is now called JApplicationWebClient

== Removed classes ==
*JParameter (use JForm instead)
*JElement and its subclasses
*JFormFieldEditors (use JFormFieldPlugins instead)
*JHtmlImage
*JSimpleXML
*JPane

== Changes to classes ==

=== Base classes ===

==== JFactory ====
*JFactory::getXMLParser() has been removed. For RSS and Atom use cases, use JFactory::getFeedParser() instead. To read XML files or strings use JFactory::getXML().
*JFactory::_createConfig() has been removed. Use JFactory::createConfig() instead.
*JFactory::_createSession() has been removed. Use JFactory::createSession() instead.
*JFactory::_createDbo() has been removed. Use JFactory::createDbo() instead.
*JFactory::_createMailer() has been removed. Use JFactory::createMailer() instead.
*JFactory::_createDocument() has been removed. Use JFactory::createDocument() instead.

=== Application ===

==== JApplicationHelper ====
*JApplicationHelper::getPath() has been removed. No replacement.
*JApplicationHelper::_checkPath() has been removed. No replacement.

==== JController ====
*JController::$_acoSection has been removed.
*JController::$_acoSectionValue has been removed.
*JController::authorize() has been removed. Use JController::authorise() instead.
*JController::setAccessControl() has been removed. Use JAccess.

==== JControllerLegacy ====
* JControllerLegacy::display() needs an extra parameter: ($cachable = false, $urlparams = false).

=== Archive ===

==== Adapters ====
*JArchiveBzip2 does not extend JObject anymore. You must not use any of JObject's methods.
*JArchiveGzip does not extend JObject anymore. You must not use any of JObject's methods.
*JArchiveTar does not extend JObject anymore. You must not use any of JObject's methods.
*JArchiveZip does not extend JObject anymore. You must not use any of JObject's methods.

=== Base ===

==== JObject ====
*JObject::toString() has been removed. Use JObject::__toString() instead.

=== Client ===

==== JClientLdap (formerly JLDAP) ====
*JClientLdap does not extend JObject anymore. You must not use any of JObject's methods.

=== Database ===
JDatabase had been renamed JDatabaseDriver. JDatabase is still around (but deprecated) and is the base of JDatabaseDriver, this way type hints and instance of checks keep working.

Due to lazy-connecting, a connection is only opened when running a query or explicitly calling JDatabaseDriver::connected(). Beware of that when checking JDatabaseDriver::connected().

==== JDatabase ====
*JDatabase::$hasQuoted has been removed.
*JDatabase::$quoted has been removed.
*JDatabase::addQuoted() has been removed.
*JDatabase::hasUTF() has been removed.
*JDatabase::debug() has been removed. Use JDatabase::setDebug() instead.
*JDatabase::explain() has been removed.
*JDatabase::getEscaped() has been removed. Use JDatabase::escape() instead.
*JDatabase::getTableFields() has been removed. Use JDatabase::getTableColumns() instead.
*JDatabase::getTicker() has been removed. Use JDatabase::count() instead.
*JDatabase::isQuoted() has been removed.
*JDatabase::loadResultArray() has been removed. Use JDatabase::loadColumn() instead.
*JDatabase::nameQuote() has been removed. Use JDatabase::quoteName() instead.
*JDatabase::queryBatch() has been removed.

=== Document ===

==== JDocument ====
*JDocument::setMetaData() the $sync argument has been removed. It was broken beyond repair.

==== JDocumentRenderer ====
*JDocumentRenderer does not extend JObject anymore. You must not use any of JObject's methods.

==== JDocumentFeed ====
*JFeedItem does not extend JObject anymore. You must not use any of JObject's methods.
*JFeedEnclosure does not extend JObject anymore. You must not use any of JObject's methods.
*JFeedImage does not extend JObject anymore. You must not use any of JObject's methods.

==== JDocumentOpenSearch ====
*JOpenSearchUrl does not extend JObject anymore. You must not use any of JObject's methods.
*JOpenSearchImage does not extend JObject anymore. You must not use any of JObject's methods.

==== JDocumentXml ====
*JDocumentXml::$_name has been renamed to JDocumentXml::$name.

=== Environment ===

==== JBrowser ====
*JBrowser does not extend JObject anymore. You must not use any of JObject's methods.
*JBrowser::setQuirk() has been removed.
*JBrowser::hasQuirk() has been removed.
*JBrowser::getQuirk() has been removed.
*JBrowser::setFeature() has been removed.
*JBrowser::hasFeature() has been removed.
*JBrowser::getFeature() has been removed.
*JBrowser::$_majorVersion has been renamed to JBrowser::$majorVersion.
*JBrowser::$_minorVersion has been renamed to JBrowser::$minorVersion.
*JBrowser::$_browser has been renamed to JBrowser::$browser.
*JBrowser::$_agent has been renamed to JBrowser::$agent.
*JBrowser::$_lowerAgent has been renamed to JBrowser::$lowerAgent.
*JBrowser::$_accept has been renamed to JBrowser::$accept.
*JBrowser::$_accept_parsed has been renamed to JBrowser::$acceptParsed.
*JBrowser::$_platform has been renamed to JBrowser::$platform.
*JBrowser::$_robots has been renamed to JBrowser::$robots.
*JBrowser::$_mobile has been renamed to JBrowser::$mobile.
*JBrowser::$_images has been renamed to JBrowser::$images.

==== JRequest ====
*JRequest::clean() has been removed.
*JRequest::_cleanVar() is now protected.

==== JURI ====
*JURI does not extend JObject anymore. You must not use any of JObject's methods.
*JUri::$_uri has been renamed to JUri::$uri.
*JUri::$_scheme has been renamed to JUri::$scheme.
*JUri::$_host has been renamed to JUri::$host.
*JUri::$_port has been renamed to JUri::$port.
*JUri::$_user has been renamed to JUri::$user.
*JUri::$_pass has been renamed to JUri::$pass.
*JUri::$_path has been renamed to JUri::$path.
*JUri::$_query has been renamed to JUri::$query.
*JUri::$_fragment has been renamed to JUri::$fragment.
*JUri::$_vars has been renamed to JUri::$vars.

=== Error ===

==== JError ====
*JError::isError() has been removed. Use instance of Exception instead.

==== JProfiler ====
*JProfiler does not extend JObject anymore. You must not use any of JObject's methods.
*JProfiler::$_start has been renamed to JProfiler::$start.
*JProfiler::$_prefix has been renamed to JProfiler::$prefix.
*JProfiler::$_buffer has been renamed to JProfiler::$buffer.
*JProfiler::$_previous_time has been renamed to JProfiler::$previousTime.
*JProfiler::$_previous_mem has been renamed to JProfiler::$previousMem.
*JProfiler::$_iswin has been renamed to JProfiler::$isWin.

=== Filesystem ===

==== JStream ====
*JStream::$_fh has been renamed to JStream::$fh.
*JStream::$_filesize has been renamed to JStream::$filesize.
*JStream::$_context has been renamed to JStream::$context.
*JStream::$_contextOptions has been renamed to JStream::$contextOptions.
*JStream::$_openmode has been renamed to JStream::$openmode.

==== JStreamString ====
*JStream::$_currentstring has been renamed to JStream::$currentString.
*JStream::$_path has been renamed to JStream::$path.
*JStream::$_mode has been renamed to JStream::$mode.
*JStream::$_options has been renamed to JStream::$options.
*JStream::$_opened_path has been renamed to JStream::$openedPath.
*JStream::$_pos has been renamed to JStream::$pos.
*JStream::$_len has been renamed to JStream::$len.
*JStream::$_stat has been renamed to JStream::$stat.

=== Filter ===

==== JFilterInput ====
*JFilterInput does not extend JObject anymore. You must not use any of JObject's methods.

=== HTML ===

==== JHtml ====
*JHtml::_includeRelativeFiles() has been removed. Use JHtml::includeRelativeFiles() instead.
*JHtml::core() has been removed. Use JHtmlBehavior::framework() instead.
*JHtml::script() doesn't support a string as the second parameter anymore. This used to be the path to the file in Joomla 1.5 and has been removed now.
*JHtml::stylesheet() doesn't support a string as the second parameter anymore. This used to be the path to the file in Joomla 1.5 and has been removed now.

==== JHtmlAccess ====
*JHtmlAccess::assetgroups() the argument $config has been removed. It was previously unused.

==== JHtmlBehavior ====
*JHtmlBehavior::mootools() has been removed. Use JHtmlBehavior::framework() instead.
*JHtmlBehavior::noframes() the argument $location has been removed. It was previously unused.

==== JHtmlList ====
*JHtmlList::ordering() the argument $chop has been removed. It was previously unused.
*JHtmlList::users(), the argument $reg has been removed.

==== JHtmlSelect ====
*JHtmlSelect::$_optionDefaults has been renamed to JHtmlSelect::$optionDefaults.

==== JToolBar ====
*JToolBar does not extend JObject anymore. You must not use any of JObject's methods.

==== JButton ====
*JButton does not extend JObject anymore. You must not use any of JObject's methods.

==== JPagination ====
*JPagination::$_viewall has been renamed to JPagination::$viewall.
*JPagination::$_additionalUrlParams has been renamed to JPagination::$additionalUrlParams.

=== Installer ===

==== JInstaller ====
*JInstaller::getOverwrite() has been removed. Use JInstaller::isOverwrite() instead.
*JInstaller::getUpgrade() has been removed. Use JInstaller::isUpgrade() instead.
*JInstaller::$_paths has been renamed to JInstaller::$paths.
*JInstaller::$_upgrade has been renamed to JInstaller::$upgrade.
*JInstaller::$_overwrite has been renamed to JInstaller::$overwrite.
*JInstaller::$_stepStack has been renamed to JInstaller::$stepStack.

==== JInstallerLanguage ====
*JInstallerLanguage::$_core as been renamed to JInstallerLanguage::$core.

=== Language ===

==== JLanguage ====
*JLanguage::getPluralSufficesCallback() has been removed. Use JLanguage::getPluralSuffixesCallback() instead.
*JLanguage::_parseLanguageFiles() has been removed. Use JLanguage::parseLanguageFiles() instead.
*JLanguage::_parseXMLLanguageFiles() has been removed. Use JLanguage::parseXMLLanguageFiles() instead.
*JLanguage::_parseXMLLanguageFile() has been removed. Use JLanguage::parseXMLLanguageFile() instead.
*JLanguage::loadLanguage() the argument $overwrite has been removed. It was previously unused.

=== Registry ===

==== JRegistry ====
*JRegistry::loadXML() has been removed. Use JRegistry::loadString() instead.
*JRegistry::loadINI() has been removed. Use JRegistry::loadString() instead.
*JRegistry::loadJSON() has been removed. Use JRegistry::loadString() instead.
*JRegistry::makeNameSpace() has been removed. No replacement.
*JRegistry::getNameSpaces() has been removed. No replacement.
*JRegistry::getValue() has been removed. Use JRegistry::get() instead.
*JRegistry::setValue() has been removed. Use JRegistry::set() instead.
*JRegistry::loadSetupFile() has been removed. No replacement.

==== JRegistryFormatINI ====
*JRegistryFormatINI::stringToObject() the second argument ($option) may not be a boolean anymore.

==== JRegistryFormatJSON ====
*JRegistryFormatJSON::stringToObject() the second argument ($option) may not be a boolean anymore.

=== Session ===

==== JSessionStorageDatabase ====
*JSessionStorageDatabase::$_data has been renamed to JSessionStorageDatabase::$data.

=== Table ===

==== JTable ====
*JTable::canDelete() has been removed.
*JTable::toXML() has been removed.

=== Updater ===

==== JUpdate ====
*JUpdate::$_xml_parser has been renamed to JUpdate::$xmlParser.
*JUpdate::$_stack has been renamed to JUpdate::$stack.
*JUpdate::$_state_store has been renamed to JUpdate::$stateStore.
*JUpdate::$_current_update has been renamed to JUpdate::$currentUpdate.

==== JUpdater ====
*JUpdater::arrayUnique() has been removed. Use JArrayHelper::arrayUnique() instead.

=== User ===

==== JAuthentication ====
*The constant JAUTHENTICATE_STATUS_SUCCESS has been removed. Use JAuthentication::STATUS_SUCCESS instead.
*The constant JAUTHENTICATE_STATUS_CANCEL has been removed. No replacement.
*The constant JAUTHENTICATE_STATUS_FAILURE has been removed. Use JAuthentication::STATUS_FAILURE instead.
*JAuthentication::$_observers has been renamed to JAuthentication::$observers.
*JAuthentication::$_state has been renamed to JAuthentication::$state.
*JAuthentication::$_methods has been renamed to JAuthentication::$methods.

==== JUser ====
*JUser::getParameters() has been removed.
*Juser::authorisedLevels() has been removed. Use JUser::getAuthorisedViewLevels() instead.
*Juser::authorize() has been removed. Use JUser::authorise() instead.
*JUser::$usertype has been removed.

=== Utility ===

==== JBuffer ====
*JBuffer::$_buffers has been renamed to JBuffer::$buffers.

==== JDate ====
*JDate::toMysql() has been removed. Use JDate::toSql() instead.
*JDate::toFormat() has been removed. Use JDate::format() instead.
*JDate::setOffset() has been removed.
*JDate::$offsets has been removed.
*JDate::__construct() doesn't accept an numeric value for $tz anymore.
*JDate::$_tz has been renamed to JDate::$tz.

==== JUtility ====
*JUtility::sendMail() has been removed. Use JMail::sendMail() instead.
*JUtility::sendAdminMail() has been removed. Use JMail::sendAdminMail() instead.
*JUtility::getHash() has been removed. Use JApplication::getHash() instead.
*JUtility::getToken() has been removed. Use JSession::getFormToken() instead.
*JUtility::isWinOS() has been removed. Use JApplication::isWinOS() instead.
*JUtility::dump() has been removed. No replacement.
*JUtility::array_unshift_ref() has been removed. No replacement.
*JUtility::array_unshift_ref() has been removed. No replacement.

==== JXMLElement ====
*JXMLElement::data() has been removed.
*JXMLElement::getAttribute() has been removed. Use SimpleXMLElement::attributes() instead.

== JavaScript ==
*Compatibility with MooTools 1.2 has been removed.
*Forms that have name="adminForm" now also require id="adminForm".
*checkAll() has been removed. Use Joomla.checkAll() instead.
*isChecked() has been removed. Use Joomla.isChecked() instead.
*popupWindow() has been removed. Use Joomla.popupWindow() instead.
*tableOrdering() has been removed. Use Joomla.tableOrdering() instead.

= CMS =

== General changes ==
*JUtility is not always loaded. If you need it you have to add jimport('joomla.utilities.utility'); to your code.

== Changes to classes ==

=== Component Classes ===
*MenusModelItem::getItem() no longer returns a JObject but a stdClass.

=== Help ===

==== JHelp ====
*JHelp::createSiteList() the argument $selected has been removed. It was unused.

[[Category:Compatibility]]
[[Category:Development]]
[[Category:Framework]]

JoomlaDays/History

2012-07-19T02:39:55Z

Sueter:

The Joomla! community has a long history of Joomla!Day events from around the world. Let's document these here, so we can ensure we have a historical timeline of Joomla!Days. See current events at [http://events.joomla.org/joomla-days.html Joomla Days]

Instructions: please add the name, date, location, and if possible the web address, of any Joomla!Days that have happened in the past. Please use the following format: Name_of_Joomla!Day - Month DD-DD, YYYY - City, Country

== 2006 ==

(5 Events)

Joomla!Day Netherlands (1) - April 22, 2006 - Breda, Netherlands

Joomla!Day UK (1) - July 30, 2006 - Leeds, United Kingdom [http://web.archive.org/web/20060709173546/http://www.joomlatraining.org.uk/joomla-day/ programme] [http://web.archive.org/web/20060814225232/http://www.joomlatraining.org.uk/content/view/297/36/ Day 1] [http://web.archive.org/web/20060813123831/http://www.joomlatraining.org.uk/content/view/298/36/ Day 2]

Joomla!Day Sweden - October 6-7, 2006 - Västerås, Sweden

Joomla!Day Netherlands (2) - December 8-9 2006 - Den Bosch, Netherlands

Joomla!Day Germany - September 29-30, 2006 - Bonn, Germany [http://www.joomladay.de/fakten/historie/joomladay-2006.html Report in German]

== 2007 ==

(17 Events)

Joomla!Day Melbourne - January 24, 2007 - Melbourne, Australia [http://forum.joomla.org/viewtopic.php?f=306&t=116577&start=150] and [http://forum.joomla.org/viewtopic.php?t=134393]

Joomla!Day France - March 25, 2007 - Paris, France

Joomla!Day Norway - June 2, 2007 - Drammen, Norway

Joomla!Day Cape Town (South Africa) - June 16, 2007 [http://www.joomladay.org.za/archive/2007-cape-town-june-16-2007.html programme]

Joomla!Day Johannesburg (South Africa) - July 14, 2007 [http://www.joomladay.org.za/archive/2007-johannesburg-july-14-2007.html programme]

Joomla!Day (Central) USA and Mexico - July 21, 2007 - Austin, Texas, USA

Joomla!Day Bangkok - August 4, 2008 - Bangkok , Thailand [http://www.flickr.com/photos/laithaiphoto/sets/72157601327115053/]

Joomla!Day Brasil - August 18, 2007 - São Paulo/SP, Brazil

Joomla!Day USA West - May 12-13, 2007 - Mountain View, California, USA

Joomla!Day NYC - October 13, 2007 - New York, New York, USA

Joomla!Day Hungary - October 21, 2007 - Budapest, Hungary

Joomla!Day Sweden - November 3, 2007 - Västerås, Sweden

Joomla!Day Helsinki - November 12, 2007 - Helsinki, Finland

Joomla!Day Cape Town (South Africa) - December 10, 2007 [http://www.joomladay.org.za/archive/2007-cape-town-december-10-2007.html programme]

Joomla!Day Nigeria - date unknown

Joomla!Day Serbia - November 17, 2007 - Belgrade, Serbia

Joomla!Day New Zealand - December 15, 2007

== 2008 ==

(20 Events)

Joomla!Day Italy - January 19, 2008 - Rome, Italy

Joomla!Day Melbourne - February 2, 2008 - Melbourne, Australia [http://forum.joomla.org/viewtopic.php?p=1184586]

Joomla!Day Spain (1) - April 19, 2008 - Madrid[http://www.joomladay.info/2008/]

Joomla!Day Netherlands (3), April 4-5, 2008 - Utrecht, Netherlands

Joomla!Day Norway - April 26, 2008 - Drammen, Norway

Joomla!Day France - April 27, 2008 - Paris, France

Joomla!Day Bangkok - May 10, 2008 - Bangkok, Thailand [http://www.flickr.com/photos/laithaiphoto/sets/72157605299681211/]

Joomla!Day Byron Bay - May 11, 2008 - Byron Bay, NSW, Australia]] [http://forum.joomla.org/viewtopic.php?f=306&t=262909]

Joomla!Day Sydney - May 19, 2008 - Sydney, Australia [http://forum.joomla.org/viewtopic.php?p=1304388]

Joomla!Day Vancouver - June 14, 2008 - Vancouver, British Columbia, Canada]] [http://community.joomla.org/events/joomla-days/400-joomla-day-vancouver-2008.html]

Joomla!Day Philippines - June 14, 2008

Joomla!Day Hungary - June 20-21, 2008

Joomla!Day Durban - June 20-21, 2008 - Durban, South Africa

Joomla!Day Brasil - August 16, 2008 - São Paulo/SP, Brazil

Joomla!Day San Francisco - September 20, 2008 - San Francisco, California, USA

Joomla!Day Johannesburg - October 18, 2008 - Johannesburg, South Africa

Joomla!Day Turkey - October 25, 2008

Joomla!Day Switzerland - November 15, 2008

Joomla!Day Sweden - November 15, 2008

Joomla!Day Nigeria - November 19, 2008

== 2009 ==

(23 Events)

Joomla!Day Turkey - January 10, 2009

Joomla!Day Melbourne - February 7-8, 2009 - Melbourne, Australia [http://community.joomla.org/events/joomla-days/641-joomladay-melbourne-2009.html]

Joomla!Day UK (2) - March 13-14, 2009 - Maidstone, England, United Kingdom

Joomla!Day Las Vegas - April 4, 2009 - Las Vegas, Nevada, USA [http://lasvegas.joomladayusa.org/]

Joomla!Day India - April 25, 2009 - Pune, India [http://community.joomla.org/blogs/community/811-joomla-day-pune-india-a-big-success.html]

Joomla!Day Sweden - May 15-16, 2009 - Stockholm, Sweden

Joomla!Day France - May 24, 2009 - Paris, France

Joomla!Day New England - May 30, 2009 - Brattleboro, Vermont, USA [http://community.joomla.org/events/joomla-days/771-joomladay-new-england-2009.html]

Joomla!Day Netherlands (4) - June 12-13, 2009 - Nieuwegein, Netherlands

Joomla!Day Cape Town - August 14, 2009 - Cape Town, South Africia

Joomla!Day Bangkok - August 22-23, 2009 - Bangkok, Thailand [http://www.flickr.com/photos/laithaiphoto/sets/72157622115004400/]

Joomla!Day Brasil - September, 12, 2009 - Rio de Janeiro/RJ, Brazil

Joomla!Day Germany - September, 24 - 26, 2009 - Bad Nauheim, Germany

Joomla!Day Mongolia - September 29-30, 2009 - Ulan Bataar, Mongolia

Joomla!Day Norway - October ?, 2009 - Drammen, Norway

Joomla!Day Gauteng - October 8-10, 2009 - Gauteng, South Africa

Joomla!Day Hungary - October 10, 2009 - Budapest, Hungary

Joomla!Day New York - October 12, 2009 - New York, New York, USA [http://community.joomla.org/events/joomla-days/912-joomla-day-new-york.html]

Joomla!Day Sydney - October 17-18, 2009 - Sydney, Australia [http://sydney.joomladay.org.au/groups/viewgroup/5-Welcome+to+Sydney+JoomlaDay+17%2B18+Oct+2009]

Joomla!Day Vietnam - November 1, 2009 - Hồ Chí Minh City, Vietnam [http://community.joomla.org/events/joomla-days/1056-joomladay-vietnam-2009.html]

Joomla!Day Italy - November 21, 2009 - Rome, Italy

Joomla!Day Spain (2) - December 11-12, 2009 - Barcelona, Spain [http://www.joomladay.info/2009/]

Joomla!Day Nigeria - December 12, 2009 - Lagos, Nigeria

== 2010 ==

(17 Events)

Joomla!Day Melbourne - February 12-14, 2010 - Melbourne, Australia [http://community.joomla.org/events/joomla-days/1102-joomladay-melbourne-2010.html]

Joomla!Day France - March 21, 2010 - Bordeaux, France

Joomla!Day Spain (3) - April 9-10, 2010 - Mallorca, Spain [http://www.joomladay.cat/]

Joomla!Day Netherlands (5) - April 23-24, 2010 - Utrecht, Netherlands [http://www.joomladagen.nl/]

Joomla!Day Sweden - April 23-24, 2010 - Stockholm, Sweden [http://www.joomladay.se/]

Joomla!Day Norway - June 4-5, 2010 - Drammen, Norway [http://www.joomladay.no/]

Joomla!Day New England - June 5, 2010 - Marlboro, Vermont, USA

Joomla!Day Brisbane - June 18-19, 2010 - Brisbane, Australia

Joomla!Day Brasil - September 11-12, 2010 - Brasília/DF, Brazil [http://www.joomladaybrasil.org/2010]

Joomla!Day USA West - October 1-3, 2010 - San Jose, California, USA [http://www.joomladaywest.com/]

Joomla!Day Italy - October 9, 2010 - Verona, Italy

Joomla!Day DC - October 16, 2010 - Chevy Chase, Maryland, USA [http://www.joomladaydc.com]

Joomla!Day Denmark - October 29-30, 2010 - Kolding, Denmark [http://www.joomladay.dk]

Joomla!Day UK (3) - October 30-31, 2010 - Ipswich, England, United Kingdom

Joomla!Day Bangkok - November 13-14, 2010 - Bangkok, Thailand [http://www.joomladay.in.th/]

Joomla!Day Spain (4) - November 26-27, 2010 - Valencia, Spain [http://www.joomladay2010.es/]

Joomla!Day NYC - December 4-5, 2010 - New York City, New York, USA

Joomla!Day Nigeria - December 11, 2010 - Lagos, Nigeria

== 2011 ==

(29 Events)

Joomla!Day Chile - January 18, 2011 - Santiago, Chile [http://www.joomladay-chile.cl/]

Joomla!Night Stockholm - February 4, 2011 - Stockholm, Sweden

Joomla!Day India - March 12-13, 2011 - Pune, Maharashtra, India [http://www.joomladay.co.in]

Joomla!Day Netherlands (6) - April 2-3, 2011 - Doorn, Netherlands [http://www.joomladagen.nl/]

Joomla!Day New England - April 2, 2011 - Brattleboro, Vermont, USA [http://www.joomladaynewengland.org]
[[Media:JoomlaDayNEProgram2011-schedule.jpg]]
[[Media:JoomlaDayNEProgram2011-speakers.jpg]]

Joomla!Day France - April 2-3, 2011 - Lyon, France [http://www.joomladay.fr/]

Joomla!Day Algeria - April 19 2011 - Alger, Algeria [http://www.joomladayalgerie.com/]

Joomla!Day Greece - May 28-29, 2011 - Athens, Greece [http://joomladay.gr/]

Joomla!Day Malaysia - June 25, 2011 - Kuala Lumpur, Malaysia [http://www.joomla-day.org.my/2011/]

Joomla!Night Chile - July 6, 2011 - Santiago, Chile [http://joomlanight-chile.cl/]

Joomla!Day Chicago - August 5-6, 2011 - Chicago, Illinois, USA [http://www.joomladaychicago.com]

Joomla!Day Norway - August 12-13, 2011 - Drammen, Norway [http://www.joomladay.no/]

Joomla!Day Bosnia and Herzegovina - August 12-14, 2011 - Tesanj, Bosnia [http://www.joomla.ba/konferencija]

Joomla!Day Cape Town - August 19-20, 2011 - Cape Town, South Africa [http://www.joomladay.org.za/] [http://www.joomladay.org.za/talks-sessions/programme.html programme]

Joomla!Day Germany - September 2-3, 2011 - Hamburg, Germany [http://www.joomladay.de]

Joomla!Day Brasil - September 2-4, 2011 - Florianópolis/SC, Brazil [http://www.joomladaybrasil.org/2011]

Joomla!Day Austin - September 15, 2011 - Austin, Texas, USA [http://www.joomladayaustin.com]

Joomla!Day UK - September 24-25, 2011 - London, England [http://www.joomladayuk2011.org]

Joomla!Day Israel - October 10, 2011 - Tel Aviv, Israel [http://jday11.joomla.org.il]

Joomla!Day Italy - October 22, 2011 - Florence, Italy [http://www.joomladay.it]

Joomla!Day NYC - October 22-23, 2011 - New York City, New York, USA [http://www.joomladaynyc.com]

Joomla!Day Denmark - October 28-29, 2011 - Kolding, Denmark [http://www.joomladay.dk]

Joomla!Day Australia - November 5-6, 2011 - Sydney, Australia [http://sydney.joomladay.org.au/]

Joomla!Day Finland - November 5, 2011 - Helsinki, Finland [http://joomladayfinland.com/]

Joomla!Day Spain - November 9-10, 2011 - Zaragoza, Spain [http://www.joomladay2011.es/]

Joomla!Day Midwest - November 12, 2011 - Milwaukee, Wisconsin, USA [http://www.joomladaymidwest.org]

Joomla!Day Algeria - November 19, 2011 - Oran, Algeria [http://www.joomladayoran.com/]

Joomla!Day Los Angeles - December 3, 2011 - Los Angeles, California, USA [http://www.jdayla.com]

Joomla!Day Lagos - December 17, 2011 - Lagos, Nigeria [http://joomlang.com/]

== 2012 ==

Joomla!Day Bangkok - February 25, 2012 - Bangkok, Thailand [http://www.joomladay.in.th]

Joomla!Day Guatemala - February 29 - March 3, 2012 - Guatemala City, Guatemala [http://www.joomlagt.org/joomladay2012/]

Joomla!Day France - March 24, 2012 - Strasbourg, France [http://www.joomladay.fr/]

Joomla!Day New England - March 31, 2012 - Brattleboro, Vermont, USA [http://www.joomladaynewengland.org/]

Joomla!Day Iran - April 12, 2012 - Mashhad, Iran [http://www.joomladay.ir]

Joomla!Day Netherlands (7) - April 21-22, 2012 - Zeist, Netherlands [http://www.joomladagen.nl/]

Joomla!Day Ribeirão Preto - May 11-12, 2012 - Ribeirão Preto, Brasil [http://jdrp.unaerp.br/]

Joomla!Day Greece 2012 - June 2-3, 2012 - Athens, Greece [http://joomladay.gr]

Joomla!Day Togo - June 14, 2012 - Assahoun, Togo

Joomla!Day Mexico - June 22-23, 2012 - Mexico City, Mexico [http://www.joomladaymexico.org/]

Joomla!Day Brasil - September 07-08, 2012 - Belo Horizonte, Minas Gerais, Brasil [http://www.joomladaybrasil.org/]

Joomla!Day Poland - September 22-23, 2012 - Poznań, Poland [http://www.joomla-day.pl/]

Joomla!Day Spain - September 28-29, 2012 - Mérida, Spain [http://www.joomladayspain.com/]

Joomla!Day Germany - October 05-06, 2012 - Berlin, Germany [http://www.joomladay.de/]

Joomla!Day Israel - October 10, 2012- Tel Aviv, Israel [http://jday.joomla.org.il]

Joomla World Conference - November 16-18, 2012 - San Jose, California, USA [http://conference.joomla.org]

== 2013 ==

Joomla!Day New England - April 13, 2013 - Brattleboro, Vermont, USA [http://www.joomladaynewengland.org/]

Configuring Xdebug for PHP development/Windows

2012-07-09T20:47:36Z

Sueter: /* Enable Xdebug */

{{incomplete}}

Configuring Xdebug is spitted into two parts:

== Serverside (extension in PHP) ==

=== Installation ===
First check if this extension is already installed. Create a new file with the content ''<?php phpinfo(); ?>'', save it in your webfolder (f.e. C:\xampp\htdocs\phpinfo.php) and call it using your browser (f.e. http://localhost/phpinfo.php). The command PHPINFO will show you all information about installed plugins, their configuration and so on. If you see a headline called Xdebug, it is already downloaded and enabled.

On a linux-system it depends on your distribution. Most of the distribution have packages ready that you can just download and install right-away. An example is Debian (or Ubunut). The package there is called ''php5-xdebug''. This command will download and enable the plugin.

To get the extension for a Windows-System, you have to download the DLL-file from http://xdebug.org/download.php that fit's to your PHP version, move it into the ''ext'' folder of your PHP-installation. If the file php_xdebug.dll exists, leave it there. It's most likely the right version, just that it's not enabled. This was f.e. the case for the last XAMPP package I used.

=== Enable Xdebug ===

On windows-systems you most likely just have one ''php.ini'' file for all configuration whereas on several Linux distributions you have a directory called ''conf.d'' in addition. If you have installed Xdebug on a Linux based system, you'll probably find a file xdebug.ini in there. Use this file instead if you have it (just not to mess-up the main config-file).

You enable the plugin by adding (or uncommenting) the following line to your config-file:
<source lang="ini">
; Example for XAMPP
zend_extension = "\xampp\php\ext\php_xdebug.dll"

; Example on Linux Debian
zend_extension=/usr/lib/php5/20090626/xdebug.so

; Example on Mac OS X for XAMPP
zend_extension="/Applications/XAMPP/xamppfiles/lib/php/php-5.3.1/extensions/no-debug-non-zts-20090626/xdebug.so"
</source>

Please make sure you use ''zend_extension'' instead of ''extension'' which (not as extension) requires the full path to the extension-file.

=== Configuration ===
Please also read this introduction for configuration-details: http://xdebug.org/docs/remote

Here is an example of the configuration I use and some comments around that:
<source lang="ini">
; location of my configuration-file
zend_extension=/usr/lib/php5/20090626/xdebug.so

; Enables colors if you use xdebug on the console
xdebug.cli_color=1

; Enable profiler by a trigger (f.e. cookie or GET-param)
xdebug.profiler_enable_trigger=1
xdebug.profiler_output_dir=/var/www/log/

; Debugger will try to connect back to the machine sending the HTTP-Request
xdebug.remote_connect_back=1

; Enables the debugger
xdebug.remote_enable=1
</source>

== Clientside (configure your IDE) ==

If your IDE is not listed on http://xdebug.org/docs/remote#clients, you'll probably find a tutorial in the manual of your IDE.
Feel free to add helpful tutorials here.

Joomla Update Missing in from Admin Menu

2012-06-19T20:45:02Z

Sueter:

Starting with version 2.5.4, the Joomla core is updated with the new component Joomla Update instead of in Extensions/Install/Update.

If Joomla Update does not shows as an installed component use the Discover function to add it as a component.

If Joomla Update shows as an installed component but is not in the Admin Menu under Components, you are missing the entry in the database table #__menu.

<source>
INSERT INTO `#__menu` (`id`, `menutype`, `title`, `alias`, `note`, `path`, `link`, `type`, `published`,
`parent_id`, `level`, `component_id`, `ordering`, `checked_out`, `checked_out_time`, `browserNav`,
`access`, `img`, `template_style_id`, `params`, `lft`, `rgt`, `home`, `language`, `client_id`)
VALUES (22, 'menu', 'com_joomlaupdate', 'Joomla! Update', '', 'Joomla! Update',
'index.php?option=com_joomlaupdate', 'component', 0, 1, 1, 28, 0, 0,
'0000-00-00 00:00:00', 0, 0, 'class:joomlaupdate', 0, '', 41, 42, 0, '*', 1);
</source>

Replace #__menu with the name of your database table. Under VALUES you need to change the id, component_id, lft and rgt to the appropriate values for your system.

[[Category:Version 2.5 FAQ]]
[[Category:Version 2.5.4 FAQ]]
[[Category:Version 2.5.5 FAQ]]
[[Category:Version 2.5.6 FAQ]]

Where is the auto update for Joomla?

2012-06-19T20:00:42Z

Sueter:

Starting with version 2.5.4, the auto update for Joomla is now located in Components→Joomla! Update, as shown here: [[File:Version-2-5-5-faq-screenshot.png|frame|none]] Extensions are still updated using the Extension Manager (Extensions→Extension Manager). If you click on the Joomla! Update icon in the Control Panel, it will link you to the Joomla! Update component automatically.

[[Category:Version 2.5 FAQ]]
[[Category:Version 2.5.5 FAQ]]
[[Category:Version 2.5.6 FAQ]]

Category:Version 2.5.6 FAQ

2012-06-19T19:59:47Z

Sueter: Created page with "These FAQs are specific to the Joomla 2.5.6 release. Only issues that are specific to this release will be listed here, together with suggested resolutions. Please add informati..."

These FAQs are specific to the Joomla 2.5.6 release. Only issues that are specific to this release will be listed here, together with suggested resolutions. Please add information to this resource. The Joomla Bug Squad will watch over this page to ensure any new bugs are added to the tracker and resolved. Continue to use the Joomla forums for support requests as this is not a substitute for posting there, but rather a common location for the community to gather release issues.

[[Category:Version 2.5 FAQ]]
[[Category:Joomla! 2.5]]

J2.5:Updating from an existing version

2012-06-19T00:32:28Z

Sueter: /* Step 2a: Find and install updates */

{{RightTOC}}
=Overview=
Starting with version 1.6, there are three ways to update your Joomla Website to versions 1.6, 1.7 or 2.5.

* Extension Manager: Update
* Extension Manager: Install
* Manually Copy Program Files

Each of these is discussed below.
==Upgrade from version earlier than 1.6.x to Joomla 1.7? ==
This page does not contain the instructions for migrating a Website from Joomla versions earlier than 1.6. See the [[Upgrading and Migrating Joomla]] page.

==Upgrade from version 1.6.x to Joomla 1.7? ==
Note: To upgrade from version 1.6.x to Joomla 1.7 please follow this [[Upgrade 1.6.5 to 1.7|guide]].

==Upgrade to Joomla 2.5 on shared hosts==
'''Important note as of 28 January 2012:''' ''On some shared host environments (GoDaddy.com and perhaps others), the normal Joomla update from 1.7 to 2.5 can intermittently fail with the error "Internal Server Error". In some cases, this can happen in the middle of the file transfer process and cause errors on the site. On GoDaddy.com, this appears to happen when the server is under a heavy load and the update takes longer than 2 minutes to complete.''
''Based on recent testing, sites on these slower shared hosts can safely be updated using a free third-party extension called [http://tinyurl.com/7d9odse Admin Tools]. If you are updating a site on a shared host, please consider using Admin Tools or else use the Manually Copy Program Files method outlined below.''
''If you have experienced an error during the update, there is a process for repairing the site.''

'''Steps and actions:'''
It is recommended that you follow these steps when updating a production site:
# Back up your site before upgrading to a new version. That way, if something goes wrong during the upgrade process, you can easily restore your site to the earlier version.
# Review the release notes for the new version to be familiar with what was changed.
# Update using one of the recommended methods outlined in this document. These methods install the new program files, delete unneeded old program files, and update the database as needed for the new Joomla version.
# Check that the update was successful, using the steps outlined in [[#Checking Your Site]].

=Method A - Extension Manager: Update Method=
{{JVer|1.6}}{{JVer|1.7}}{{JVer|2.5}}
This is the easier way, also called ''One click update''

==Step 1: Make sure you have a current backup of your site==
In many cases, your host will make periodic site backups.

==Step 2a: Find and install updates==
# '''If your site is prior to 2.5.4, see Step 2b instead'''
# In the back end of your Joomla site, navigate to Components → Joomla Update.
# Click on Install the Update [[Image:Update-screenshot-20120618-01.png|frame|center]]
# '''IMPORTANT:''' This process will take a few minutes. Wait until the process completes and it tells you that you are already on the current release, similar to the screen shown below. [[Image:Update-screenshot-20120618-02.png|frame|center]]
# Congratulations! At this point, your site is updated.
'''Important:''' You need now to check that your site is working correctly. See below Checking Your Site

==Step 2b: Find and install updates (Prior to updating 2.5.4)==
# In the back end of your Joomla site, navigate to Extensions → Extension Manager and open the Update tab.
# Click on the Purge Cache icon to clear out the cache.
# Click on the Find Updates icon in the toolbar. If there is an available update, the screen will list it, similar to the screen shown below. [[Image:Update-screenshot-20120124-01.png|frame|center]] Note that available upgrades for extensions used in the site will also show in the list.
# Select the update (using the checkbox) and click on the Update icon in the toolbar.
# '''IMPORTANT:''' This process will take a few minutes. Wait until the process completes and the success message shows, similar to the screen shown below. [[Image:Update-screenshot-20120124-02.png|frame|center]]
# Congratulations! At this point, your site is updated.
'''Important:''' You need now to check that your site is working correctly. See below Checking Your Site

=Method B - Extension Manager: Install Method=
{{JVer|1.6}}{{JVer|1.7}}{{JVer|2.5}}
In some cases it may not be possible to use the Extension Manager: Update method to update your site. One reason for this might be that you are using a non-standard distribution (for example, a distribution with a different default language installed). Another reason might be that your don't have a reliable enough internet connection to support automatic installation.

In this case, you can still do an easy installation using the Extension Manager: Install screen. Like the Update screen, this method will do the database updates automatically and will completely update your system without any further steps.

==Step 1: Make sure you have a current backup of your site==
In many cases, your host will make periodic site backups.

==Step 2: Locate the update file==
Locate the required archive file (for example, .zip, .tag.gz, or tar.bz2 archive) for your version. If you are updating to an x.x.0 release (for example, from 1.7.3 to 2.5.0), this will normally be a file like Joomla_2.5.0-Stable-Update_Package.zip. If you are updating within the same release series (for example, 2.5.0 to 2.5.1), then the file will be named something like Joomla_2.5.0_to_2.5.1-Stable-Patch_Package.zip.

At this point, you have three options:
# Install from URL
# Install from Directory
# Upload Package File

Install from URL is the easiest to do. With this option, the upgrade archive is loaded directly by the server, so it works well even if your local computer has a slow or unreliable internet connection.

Install from Directory is the safest method if the server itself has a slow internet connection. With this method, you use FTP to load the unpacked update files into a temporary folder on the server. Then you point to that directory on the server for the installation.

Upload Package File is fairly simple, but it requires that you have a good connection between your local computer and the server.

The screen below shows the Extension Manager: Install screen with the three options labeled.
[[Image:Update-screenshot-20120124-03.png|frame|center]]

===Install from URL===
This option is the easiest, if the archive file is available on a website.
# In the Extension Manager: Install screen, enter the URL for the archive file in the Install URL field.
# Press the Install button.
The system will work for a period of time, up to two minutes or more for a full version update. Then a message indicating a successful installation will display.

===Install from Directory===
This option requires that you unpack the archive file in a directory on your server. This is the best method if you have a slow internet connection or you are experiencing timeouts during the update process.
# Unpack the archive file in a temporary directory on your local machine.
# Upload all the files in this directory (for example, using FTP) to a temporary directory that is visible to the web server. For example, you can create a sub-directory under the tmp directory in your Joomla root. For this example, let's say the directory on the server is <code>/home/myuser/myjoomla/tmp/upgrade250</code>).
# In the Extension Manager: Install screen, enter the full path of the temporary directory (on the server) from step 2 (for example, <code>/home/myuser/myjoomla/tmp/upgrade250</code>).
# Press the Install button.
The system will work for a short time (perhaps a minute or less, depending on your server). Then a message indicating a successful installation will display.

===Upload Package File===
This option requires that you first download the archive file to your local machine.
# Download the file to your local computer.
# In the Extension Manager: Install screen, click the Browse button next to the Package File field and browse to the archive file.
# Press the Install button.
The system will work for a period of time, up to two minutes or more for a full version update. Then a message indicating a successful installation will display.

# Congratulations! At this point, your site is updated.
'''Important:''' You need now to check that your site is working correctly. See below Checking Your Site.

=Method C - Manually Copy New Program Files=
This method is similar to the old method for updating Joomla versions. Here we want to replace the existing program files with the files from the update archive. The advantage of this method is that it will work on slower shared hosts. The disadvantage is that it requires more work by the system administrator.

''Important: This method can also be used to repair a site where the automatic update failed due to a server timeout.''

==Copy the New Program Files to Your Site==
There are two ways you can do this.
# Copy the archive file to the root directory of your site and unpack the archive. The update archive will be named something like <code>Joomla_2.5.0-Stable-Update_Package.zip</code>. Note that you need to tell the system to replace any existing files. For example, in GoDaddy.com, use the FTP File Manager to upload the update file and then use "Unarchive" to unpack it. Check the box "Overwrite existing files".
# If you don't have the ability to unpack the archive on the server, create a temporary directory on your local machine and unpack the archive file there. Then FTP these files to the root directory of your site, overwriting the existing files.

==Update the Database==
At this point, you should be able to log into the back end of your site with the new version installed. However, you are not done. Navigate to Extension Manager: Database. You will initially have Database problems when you check the Database, similar to the screen below.
[[Image:Update-screenshot-20120124-08.png|frame|center|Database Screen Before Fix]]
This is expected. Click on the Fix icon to correct the problems. Now the screen should show that the database is up to date.

==Install New Extensions==
Navigate to Extension Manager: Discover and click on the Discover icon in the toolbar. If the updated version has new core extensions, new extensions will be listed, as shown below.
[[Image:Update-screenshot-20120124-09.png|frame|center|Discover Screen Before Install]]
Select all the extensions and click on the Install icon in the toolbar. The system should display a success message similar to the screen below.
[[Image:Update-screenshot-20120124-10.png|frame|center|Discover Screen After Install]]

==Update the #__extensions Table==
At this point, your site is updated. However, there is one more thing to do. The site will think it needs to be updated because a value in the #__extensions table is wrong. To fix this:
* Using phpMyAdmin or a similar tool, edit the row of the #__extensions table where the id column is '700'. (Note that the table prefix will be different in your site. For example, if your table prefix is "jos_", then the table will be called "jos_extensions".
* In the manifest_cache column, you will see the old version in the text (for example, <code>"version":"1.7.3"</code>). Change this to the new version (for example, <code>"version":"2.5.0"</code>). Be careful to not change anything else in this column.
* To check that this was successful, navigate to Extension Manager: Update and click Check for Updates. You should '''not''' see the current Joomla version in the list.

At this point, your site should be updated correctly.

=Checking Your Site=
'''This is required for method A and B!'''
After an update, it is a good idea to check your site to make sure the update was successful. There are two quick checks you can do from the Extension Manager.
==Extension Manager: Check Database==
{{JVer|2.5}} This feature was added in version 2.5.0. It checks that your database is up to date with your Joomla programs.

Navigate to Extension Manager: Database. If your database is up to date, you should see a screen similar to the one below:
[[Image:Update-screenshot-20120124-04.png|frame|center|Database Screen With No Problems]]

If your database is not up to date, you will see a screen listing the problems found, similar to the one below:
[[Image:Update-screenshot-20120124-05.png|frame|center|Database Screen With 3 Database Problems]]
In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.

'''N.B.''' If any errors fail to fix then make sure all the database Tables are checked in.

==Extension Manager: Discover==
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to Extension Manager: Discover. Then click on the Discover icon in the toolbar. The screen should show as follows:
[[Image:Update-screenshot-20120124-06.png|frame|center|Discover Screen With No Extensions To Install]]
If so, you know that any new extensions added during the udpate were correctly installed in the database.

If there are uninstalled extensions, they will show similar to the following screen:
[[Image:Update-screenshot-20120124-07.png|frame|center|Discover Screen With Two Extensions To Install]]
In this case, check the check boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.

=Troubleshooting Update Problems=
If you have any questions before, during, or after the upgrade then please ask them on the [http://forum.joomla.org/viewforum.php?f=625&sid=259a29d8e21242b6770f86026f6c9c3a Joomla! 1.6 Migrating and Upgrading Forum].

If you have problems or errors during the update process, here are some tips.
* If any database error messages show after the update, be sure to check the Extension Manager: Database tab followed by the Extension Manager: Discover tab. In some cases, if a database error occurs it will prevent all the database updates from running. In this case, you can run them from the Database tab and then use the Discover→Install method to check and install any new extensions.
* If you encounter any errors or problems during or after the update, be sure to check the FAQ for the version you updated to. For example, for version 2.5.0, this will be an article entitled [http://docs.joomla.org/Category:Version_2.5.0_FAQ http://docs.joomla.org/Category:Version_2.5.0_FAQ].

[[Category:Upgrading]]

J2.5:Updating from an existing version

2012-06-19T00:31:37Z

Sueter: /* Method A - Extension Manager: Update Method */

{{RightTOC}}
=Overview=
Starting with version 1.6, there are three ways to update your Joomla Website to versions 1.6, 1.7 or 2.5.

* Extension Manager: Update
* Extension Manager: Install
* Manually Copy Program Files

Each of these is discussed below.
==Upgrade from version earlier than 1.6.x to Joomla 1.7? ==
This page does not contain the instructions for migrating a Website from Joomla versions earlier than 1.6. See the [[Upgrading and Migrating Joomla]] page.

==Upgrade from version 1.6.x to Joomla 1.7? ==
Note: To upgrade from version 1.6.x to Joomla 1.7 please follow this [[Upgrade 1.6.5 to 1.7|guide]].

==Upgrade to Joomla 2.5 on shared hosts==
'''Important note as of 28 January 2012:''' ''On some shared host environments (GoDaddy.com and perhaps others), the normal Joomla update from 1.7 to 2.5 can intermittently fail with the error "Internal Server Error". In some cases, this can happen in the middle of the file transfer process and cause errors on the site. On GoDaddy.com, this appears to happen when the server is under a heavy load and the update takes longer than 2 minutes to complete.''
''Based on recent testing, sites on these slower shared hosts can safely be updated using a free third-party extension called [http://tinyurl.com/7d9odse Admin Tools]. If you are updating a site on a shared host, please consider using Admin Tools or else use the Manually Copy Program Files method outlined below.''
''If you have experienced an error during the update, there is a process for repairing the site.''

'''Steps and actions:'''
It is recommended that you follow these steps when updating a production site:
# Back up your site before upgrading to a new version. That way, if something goes wrong during the upgrade process, you can easily restore your site to the earlier version.
# Review the release notes for the new version to be familiar with what was changed.
# Update using one of the recommended methods outlined in this document. These methods install the new program files, delete unneeded old program files, and update the database as needed for the new Joomla version.
# Check that the update was successful, using the steps outlined in [[#Checking Your Site]].

=Method A - Extension Manager: Update Method=
{{JVer|1.6}}{{JVer|1.7}}{{JVer|2.5}}
This is the easier way, also called ''One click update''

==Step 1: Make sure you have a current backup of your site==
In many cases, your host will make periodic site backups.

==Step 2a: Find and install updates==
# '''If your site is prior to 2.5.4, see Step 2b instead'''
# In the back end of your Joomla site, navigate to Components → Joomla Update.
# Click on Install the Update [[Image:Update-screenshot-20120618-01|frame|center]]
# '''IMPORTANT:''' This process will take a few minutes. Wait until the process completes and it tells you that you are already on the current release, similar to the screen shown below. [[Image:Update-screenshot-20120618-02|frame|center]]
# Congratulations! At this point, your site is updated.
'''Important:''' You need now to check that your site is working correctly. See below Checking Your Site

==Step 2b: Find and install updates (Prior to updating 2.5.4)==
# In the back end of your Joomla site, navigate to Extensions → Extension Manager and open the Update tab.
# Click on the Purge Cache icon to clear out the cache.
# Click on the Find Updates icon in the toolbar. If there is an available update, the screen will list it, similar to the screen shown below. [[Image:Update-screenshot-20120124-01.png|frame|center]] Note that available upgrades for extensions used in the site will also show in the list.
# Select the update (using the checkbox) and click on the Update icon in the toolbar.
# '''IMPORTANT:''' This process will take a few minutes. Wait until the process completes and the success message shows, similar to the screen shown below. [[Image:Update-screenshot-20120124-02.png|frame|center]]
# Congratulations! At this point, your site is updated.
'''Important:''' You need now to check that your site is working correctly. See below Checking Your Site

=Method B - Extension Manager: Install Method=
{{JVer|1.6}}{{JVer|1.7}}{{JVer|2.5}}
In some cases it may not be possible to use the Extension Manager: Update method to update your site. One reason for this might be that you are using a non-standard distribution (for example, a distribution with a different default language installed). Another reason might be that your don't have a reliable enough internet connection to support automatic installation.

In this case, you can still do an easy installation using the Extension Manager: Install screen. Like the Update screen, this method will do the database updates automatically and will completely update your system without any further steps.

==Step 1: Make sure you have a current backup of your site==
In many cases, your host will make periodic site backups.

==Step 2: Locate the update file==
Locate the required archive file (for example, .zip, .tag.gz, or tar.bz2 archive) for your version. If you are updating to an x.x.0 release (for example, from 1.7.3 to 2.5.0), this will normally be a file like Joomla_2.5.0-Stable-Update_Package.zip. If you are updating within the same release series (for example, 2.5.0 to 2.5.1), then the file will be named something like Joomla_2.5.0_to_2.5.1-Stable-Patch_Package.zip.

At this point, you have three options:
# Install from URL
# Install from Directory
# Upload Package File

Install from URL is the easiest to do. With this option, the upgrade archive is loaded directly by the server, so it works well even if your local computer has a slow or unreliable internet connection.

Install from Directory is the safest method if the server itself has a slow internet connection. With this method, you use FTP to load the unpacked update files into a temporary folder on the server. Then you point to that directory on the server for the installation.

Upload Package File is fairly simple, but it requires that you have a good connection between your local computer and the server.

The screen below shows the Extension Manager: Install screen with the three options labeled.
[[Image:Update-screenshot-20120124-03.png|frame|center]]

===Install from URL===
This option is the easiest, if the archive file is available on a website.
# In the Extension Manager: Install screen, enter the URL for the archive file in the Install URL field.
# Press the Install button.
The system will work for a period of time, up to two minutes or more for a full version update. Then a message indicating a successful installation will display.

===Install from Directory===
This option requires that you unpack the archive file in a directory on your server. This is the best method if you have a slow internet connection or you are experiencing timeouts during the update process.
# Unpack the archive file in a temporary directory on your local machine.
# Upload all the files in this directory (for example, using FTP) to a temporary directory that is visible to the web server. For example, you can create a sub-directory under the tmp directory in your Joomla root. For this example, let's say the directory on the server is <code>/home/myuser/myjoomla/tmp/upgrade250</code>).
# In the Extension Manager: Install screen, enter the full path of the temporary directory (on the server) from step 2 (for example, <code>/home/myuser/myjoomla/tmp/upgrade250</code>).
# Press the Install button.
The system will work for a short time (perhaps a minute or less, depending on your server). Then a message indicating a successful installation will display.

===Upload Package File===
This option requires that you first download the archive file to your local machine.
# Download the file to your local computer.
# In the Extension Manager: Install screen, click the Browse button next to the Package File field and browse to the archive file.
# Press the Install button.
The system will work for a period of time, up to two minutes or more for a full version update. Then a message indicating a successful installation will display.

# Congratulations! At this point, your site is updated.
'''Important:''' You need now to check that your site is working correctly. See below Checking Your Site.

=Method C - Manually Copy New Program Files=
This method is similar to the old method for updating Joomla versions. Here we want to replace the existing program files with the files from the update archive. The advantage of this method is that it will work on slower shared hosts. The disadvantage is that it requires more work by the system administrator.

''Important: This method can also be used to repair a site where the automatic update failed due to a server timeout.''

==Copy the New Program Files to Your Site==
There are two ways you can do this.
# Copy the archive file to the root directory of your site and unpack the archive. The update archive will be named something like <code>Joomla_2.5.0-Stable-Update_Package.zip</code>. Note that you need to tell the system to replace any existing files. For example, in GoDaddy.com, use the FTP File Manager to upload the update file and then use "Unarchive" to unpack it. Check the box "Overwrite existing files".
# If you don't have the ability to unpack the archive on the server, create a temporary directory on your local machine and unpack the archive file there. Then FTP these files to the root directory of your site, overwriting the existing files.

==Update the Database==
At this point, you should be able to log into the back end of your site with the new version installed. However, you are not done. Navigate to Extension Manager: Database. You will initially have Database problems when you check the Database, similar to the screen below.
[[Image:Update-screenshot-20120124-08.png|frame|center|Database Screen Before Fix]]
This is expected. Click on the Fix icon to correct the problems. Now the screen should show that the database is up to date.

==Install New Extensions==
Navigate to Extension Manager: Discover and click on the Discover icon in the toolbar. If the updated version has new core extensions, new extensions will be listed, as shown below.
[[Image:Update-screenshot-20120124-09.png|frame|center|Discover Screen Before Install]]
Select all the extensions and click on the Install icon in the toolbar. The system should display a success message similar to the screen below.
[[Image:Update-screenshot-20120124-10.png|frame|center|Discover Screen After Install]]

==Update the #__extensions Table==
At this point, your site is updated. However, there is one more thing to do. The site will think it needs to be updated because a value in the #__extensions table is wrong. To fix this:
* Using phpMyAdmin or a similar tool, edit the row of the #__extensions table where the id column is '700'. (Note that the table prefix will be different in your site. For example, if your table prefix is "jos_", then the table will be called "jos_extensions".
* In the manifest_cache column, you will see the old version in the text (for example, <code>"version":"1.7.3"</code>). Change this to the new version (for example, <code>"version":"2.5.0"</code>). Be careful to not change anything else in this column.
* To check that this was successful, navigate to Extension Manager: Update and click Check for Updates. You should '''not''' see the current Joomla version in the list.

At this point, your site should be updated correctly.

=Checking Your Site=
'''This is required for method A and B!'''
After an update, it is a good idea to check your site to make sure the update was successful. There are two quick checks you can do from the Extension Manager.
==Extension Manager: Check Database==
{{JVer|2.5}} This feature was added in version 2.5.0. It checks that your database is up to date with your Joomla programs.

Navigate to Extension Manager: Database. If your database is up to date, you should see a screen similar to the one below:
[[Image:Update-screenshot-20120124-04.png|frame|center|Database Screen With No Problems]]

If your database is not up to date, you will see a screen listing the problems found, similar to the one below:
[[Image:Update-screenshot-20120124-05.png|frame|center|Database Screen With 3 Database Problems]]
In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.

'''N.B.''' If any errors fail to fix then make sure all the database Tables are checked in.

==Extension Manager: Discover==
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to Extension Manager: Discover. Then click on the Discover icon in the toolbar. The screen should show as follows:
[[Image:Update-screenshot-20120124-06.png|frame|center|Discover Screen With No Extensions To Install]]
If so, you know that any new extensions added during the udpate were correctly installed in the database.

If there are uninstalled extensions, they will show similar to the following screen:
[[Image:Update-screenshot-20120124-07.png|frame|center|Discover Screen With Two Extensions To Install]]
In this case, check the check boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.

=Troubleshooting Update Problems=
If you have any questions before, during, or after the upgrade then please ask them on the [http://forum.joomla.org/viewforum.php?f=625&sid=259a29d8e21242b6770f86026f6c9c3a Joomla! 1.6 Migrating and Upgrading Forum].

If you have problems or errors during the update process, here are some tips.
* If any database error messages show after the update, be sure to check the Extension Manager: Database tab followed by the Extension Manager: Discover tab. In some cases, if a database error occurs it will prevent all the database updates from running. In this case, you can run them from the Database tab and then use the Discover→Install method to check and install any new extensions.
* If you encounter any errors or problems during or after the update, be sure to check the FAQ for the version you updated to. For example, for version 2.5.0, this will be an article entitled [http://docs.joomla.org/Category:Version_2.5.0_FAQ http://docs.joomla.org/Category:Version_2.5.0_FAQ].

[[Category:Upgrading]]

File:Update-screenshot-20120618-02.png

2012-06-19T00:31:03Z

Sueter:

File:Update-screenshot-20120618-01.png

2012-06-19T00:29:31Z

Sueter:

== Licensing ==
{{JEDL}}

Joomla Update Missing in from Admin Menu

2012-06-18T19:12:37Z

Sueter:

Starting with version 2.5.4, the Joomla core is updated with the new component Joomla Update instead of in Extensions/Install/Update. If Joomla Update shows as an installed component but is not in the Admin Menu under Components, you are missing the entry in the database table #__menu.

<source>
INSERT INTO `#__menu` (`id`, `menutype`, `title`, `alias`, `note`, `path`, `link`, `type`, `published`,
`parent_id`, `level`, `component_id`, `ordering`, `checked_out`, `checked_out_time`, `browserNav`,
`access`, `img`, `template_style_id`, `params`, `lft`, `rgt`, `home`, `language`, `client_id`)
VALUES (22, 'menu', 'com_joomlaupdate', 'Joomla! Update', '', 'Joomla! Update',
'index.php?option=com_joomlaupdate', 'component', 0, 1, 1, 28, 0, 0,
'0000-00-00 00:00:00', 0, 0, 'class:joomlaupdate', 0, '', 41, 42, 0, '*', 1);
</source>

Replace #__menu with the name of your database table. Under VALUES you need to change the id, component_id, lft and rgt to the appropriate values for your system.

[[Category:Version 2.5 FAQ]]
[[Category:Version 2.5.4 FAQ]]
[[Category:Version 2.5.5 FAQ]]

Joomla Update Missing in from Admin Menu

2012-06-18T19:04:30Z

Sueter:

Starting with version 2.5.4, the Joomla core is updated with the new component Joomla Update instead of in Extensions/Install/Update. If Joomla Update shows as an installed component but is not in the Admin Menu under Components, you are missing the entry in the database table #__menus.

<source>
INSERT INTO `#__menu` (`id`, `menutype`, `title`, `alias`, `note`, `path`, `link`, `type`, `published`, `parent_id`, `level`, `component_id`, `ordering`, `checked_out`, `checked_out_time`, `browserNav`, `access`, `img`, `template_style_id`, `params`, `lft`, `rgt`, `home`, `language`, `client_id`) VALUES
(22, 'menu', 'com_joomlaupdate', 'Joomla! Update', '', 'Joomla! Update', 'index.php?option=com_joomlaupdate', 'component', 0, 1, 1, 28, 0, 0, '0000-00-00 00:00:00', 0, 0, 'class:joomlaupdate', 0, '', 41, 42, 0, '*', 1);
</source>

[[Category:Version 2.5 FAQ]]
[[Category:Version 2.5.4 FAQ]]
[[Category:Version 2.5.5 FAQ]]

Joomla Update Missing in from Admin Menu

2012-06-18T18:55:50Z

Sueter: Created page with "Starting with version 2.5.4, the Joomla core is updated with the new component Joomla Update instead of in Extensions/Install/Update. If Joomla Update shows as an installed compo..."

Multi-site Working Group

2012-05-08T22:38:29Z

Sueter: /* Coordinators & PLT Contact */

The Multi-site Working Group is a Production Working Group.

==Coordinators & PLT Contact==
The coordinator & PLT Contact for this working group is Christophe Demko (mailto:christophe.demko@joomla.org).

==Announcements==

==External resources==

==Deliverables==

==Technical Work produced by this group==

==Communications==

==Roadmap==

==Meetings==

[[Category:Documentation Working Group]]
[[Category:Working Groups]]

Multi-site Working Group

2012-05-08T22:37:02Z

Sueter: Created page with "The Multi-site Working Group is a Production Working Group. ==Coordinators & PLT Contact== The coordinator & PLT Contact for this working group is Christophe Demko. ==Announcem..."

The Multi-site Working Group is a Production Working Group.

==Coordinators & PLT Contact==
The coordinator & PLT Contact for this working group is Christophe Demko.

==Announcements==

==External resources==

==Deliverables==

==Technical Work produced by this group==

==Communications==

==Roadmap==

==Meetings==

[[Category:Documentation Working Group]]
[[Category:Working Groups]]

Production Working Groups

2012-05-08T22:36:06Z

Sueter: /* Multi-site Working Group */

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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

==Current Production Working Groups==
The following is a list of all current production working groups in alphabetical order.

===Bug Squad===
For further information see [[Bug Squad|Bug Squad]].

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Database Working Group===
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Documentation Working Group===
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

===Internet of Things Working Group===
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

===JavaScript Working Group===

* Coordinator: Joe LeBlanc
* PLT Contact: To be determined.

For further information see [[JavaScript Working Group]]

===Joomla Security Strike Team===
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Multi-site Working Group===

* Coordinator: Christophe Demko (mailto:christophe.demko@joomla.org).
* PLT Contact: Christophe Demko (mailto:christophe.demko@joomla.org).

For further information see [[Multi-site Working Group]]

===Message Queue Working Group===

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see: [[Message Queue Working Group]].

===Search Working Group===
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: To be determined.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

===Translations Working Group===
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

===Unified Content Model Working Group===
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: To be determined.
* PLT Contact: To be determined.

For further information see [[Unified Content Model Working Group]]

===Unit Tests for CMS Working Group===

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

===Update and Migration Working Group===

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

For further information see [[Update and Migration Working Group]]

===User Experience Working Group===
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

===Web Services Working Group===

* Coordinator: To be determined.
* PLT Contact: To be determined.

For further information see [[Web Services Working Group]]

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Production Working Groups

2012-05-08T22:34:12Z

Sueter: /* Unified Content Model Working Group */

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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

==Current Production Working Groups==
The following is a list of all current production working groups in alphabetical order.

===Bug Squad===
For further information see [[Bug Squad|Bug Squad]].

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Database Working Group===
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Documentation Working Group===
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

===Internet of Things Working Group===
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

===JavaScript Working Group===

* Coordinator: Joe LeBlanc
* PLT Contact: To be determined.

For further information see [[JavaScript Working Group]]

===Joomla Security Strike Team===
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Multi-site Working Group===

* Coordinator: Christophe Demko (mailto:christophe.demko@joomla.org).
* PLT Contact: Christophe Demko (mailto:christophe.demko@joomla.org).

===Message Queue Working Group===

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see: [[Message Queue Working Group]].

===Search Working Group===
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: To be determined.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

===Translations Working Group===
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

===Unified Content Model Working Group===
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: To be determined.
* PLT Contact: To be determined.

For further information see [[Unified Content Model Working Group]]

===Unit Tests for CMS Working Group===

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

===Update and Migration Working Group===

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

For further information see [[Update and Migration Working Group]]

===User Experience Working Group===
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

===Web Services Working Group===

* Coordinator: To be determined.
* PLT Contact: To be determined.

For further information see [[Web Services Working Group]]

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Production Working Groups

2012-05-08T22:33:52Z

Sueter: /* Unified Content Model Working Group */

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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

==Current Production Working Groups==
The following is a list of all current production working groups in alphabetical order.

===Bug Squad===
For further information see [[Bug Squad|Bug Squad]].

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Database Working Group===
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Documentation Working Group===
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

===Internet of Things Working Group===
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

===JavaScript Working Group===

* Coordinator: Joe LeBlanc
* PLT Contact: To be determined.

For further information see [[JavaScript Working Group]]

===Joomla Security Strike Team===
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Multi-site Working Group===

* Coordinator: Christophe Demko (mailto:christophe.demko@joomla.org).
* PLT Contact: Christophe Demko (mailto:christophe.demko@joomla.org).

===Message Queue Working Group===

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see: [[Message Queue Working Group]].

===Search Working Group===
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: To be determined.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

===Translations Working Group===
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

===Unified Content Model Working Group===
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: To be determined.
* PLT Contact: To be determined.

For further information see [[Unified Content Model Working Group]]

===Unit Tests for CMS Working Group===

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

===Update and Migration Working Group===

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

For further information see [[Update and Migration Working Group]]

===User Experience Working Group===
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

===Web Services Working Group===

* Coordinator: To be determined.
* PLT Contact: To be determined.

For further information see [[Web Services Working Group]]

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Web Services Working Group

2012-05-08T22:33:01Z

Sueter: Created page with "The Web Services Working Group is a Production Working Group. ==Coordinators & PLT Contact== ==Announcements== ==External resources== ==Deliverables== ==Technical Work produ..."

The Web Services Working Group is a Production Working Group.

==Coordinators & PLT Contact==

==Announcements==

==External resources==

==Deliverables==

==Technical Work produced by this group==

==Communications==

==Roadmap==

==Meetings==

[[Category:Documentation Working Group]]
[[Category:Working Groups]]

Production Working Groups

2012-05-08T22:32:16Z

Sueter: /* Web Services Working Group */

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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

==Current Production Working Groups==
The following is a list of all current production working groups in alphabetical order.

===Bug Squad===
For further information see [[Bug Squad|Bug Squad]].

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Database Working Group===
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Documentation Working Group===
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

===Internet of Things Working Group===
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

===JavaScript Working Group===

* Coordinator: Joe LeBlanc
* PLT Contact: To be determined.

For further information see [[JavaScript Working Group]]

===Joomla Security Strike Team===
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Multi-site Working Group===

* Coordinator: Christophe Demko (mailto:christophe.demko@joomla.org).
* PLT Contact: Christophe Demko (mailto:christophe.demko@joomla.org).

===Message Queue Working Group===

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see: [[Message Queue Working Group]].

===Search Working Group===
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: To be determined.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

===Translations Working Group===
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

===Unified Content Model Working Group===
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: To be determined.
* PLT Contact: To be determined.

===Unit Tests for CMS Working Group===

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

===Update and Migration Working Group===

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

For further information see [[Update and Migration Working Group]]

===User Experience Working Group===
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

===Web Services Working Group===

* Coordinator: To be determined.
* PLT Contact: To be determined.

For further information see [[Web Services Working Group]]

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Update and Migration Working Group

2012-05-08T22:30:16Z

Sueter: Created page with "The Update and Migration Working Group is a Production Working Group. Dealing with updates and migration should be a part of every Working Group that makes changes that break ba..."

The Update and Migration Working Group is a Production Working Group.

Dealing with updates and migration should be a part of every Working Group that makes changes that break backward compatibility, but we need a group that can make sure that the software and tools are ready to migrate from 2.5 to 3.x. as seamlessly as possible.

==Coordinators & PLT Contact==
The PLT Contact for this group is Mark Dexter.

==Announcements==

==External resources==

==Deliverables==

==Technical Work produced by this group==

==Communications==

==Roadmap==

==Meetings==

[[Category:Documentation Working Group]]
[[Category:Working Groups]]

Production Working Groups

2012-05-08T22:27:53Z

Sueter: /* Update and Migration Working Group */

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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

==Current Production Working Groups==
The following is a list of all current production working groups in alphabetical order.

===Bug Squad===
For further information see [[Bug Squad|Bug Squad]].

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Database Working Group===
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Documentation Working Group===
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

===Internet of Things Working Group===
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

===JavaScript Working Group===

* Coordinator: Joe LeBlanc
* PLT Contact: To be determined.

For further information see [[JavaScript Working Group]]

===Joomla Security Strike Team===
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Multi-site Working Group===

* Coordinator: Christophe Demko (mailto:christophe.demko@joomla.org).
* PLT Contact: Christophe Demko (mailto:christophe.demko@joomla.org).

===Message Queue Working Group===

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see: [[Message Queue Working Group]].

===Search Working Group===
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: To be determined.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

===Translations Working Group===
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

===Unified Content Model Working Group===
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: To be determined.
* PLT Contact: To be determined.

===Unit Tests for CMS Working Group===

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

===Update and Migration Working Group===

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

For further information see [[Update and Migration Working Group]]

===User Experience Working Group===
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

===Web Services Working Group===

* Coordinator: To be determined.
* PLT Contact: To be determined.

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

JavaScript Working Group

2012-05-08T19:22:43Z

Sueter: Created page with "The JavaScript Working Group is a Production Working Group. It is responsible for establishing standards for JavaScript and seeing that the JavaScript and/or JS frameworks are in..."

The JavaScript Working Group is a Production Working Group. It is responsible for establishing standards for JavaScript and seeing that the JavaScript and/or JS frameworks are integrated and maintained.

==Coordinators & PLT Contact==
The coordinator for this working group is Joe LeBlanc.

==Announcements==

==External resources==

==Deliverables==

==Technical Work produced by this group==

==Communications==

==Roadmap==

==Meetings==

[[Category:Documentation Working Group]]
[[Category:Working Groups]]

Production Working Groups

2012-05-08T19:18:47Z

Sueter:

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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

==Current Production Working Groups==
The following is a list of all current production working groups in alphabetical order.

===Bug Squad===
For further information see [[Bug Squad|Bug Squad]].

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Database Working Group===
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Documentation Working Group===
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

===Internet of Things Working Group===
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

===JavaScript Working Group===

* Coordinator: Joe LeBlanc
* PLT Contact: To be determined.

For further information see [[JavaScript Working Group]]

===Joomla Security Strike Team===
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Multi-site Working Group===

* Coordinator: Christophe Demko (mailto:christophe.demko@joomla.org).
* PLT Contact: Christophe Demko (mailto:christophe.demko@joomla.org).

===Message Queue Working Group===

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see: [[Message Queue Working Group]].

===Search Working Group===
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: To be determined.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

===Translations Working Group===
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

===Unified Content Model Working Group===
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: To be determined.
* PLT Contact: To be determined.

===Unit Tests for CMS Working Group===

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

===Update and Migration Working Group===

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===User Experience Working Group===
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

===Web Services Working Group===

* Coordinator: To be determined.
* PLT Contact: To be determined.

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Production Working Groups

2012-04-26T18:49:24Z

Sueter: /* Unified Content Model Working Group */

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 [http://opensourcematters.org/mission-vision-values.html mission, vision and values] of the Joomla project and additionally we would need the working group coordinators to sign the [http://developer.joomla.org/contributor-agreements.html Joomla Contributor Agreement (JCA)]. Ordinary working groups 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.

==Current Production Working Groups==
The following is a list of all current production working groups in alphabetical order.

===Bug Squad===
For further information see [[Bug Squad|Bug Squad]].

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Database Working Group===
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Documentation Working Group===
The [[Documentation Working Group|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 [http://api.joomla.org api.joomla.org] and other resources.

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

===Internet of Things Working Group===
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

* Coordinator: Phil Walton (mailto:phil@jthings.co.uk)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information go to [http://www.jthings.co.uk www.jthings.co.uk]

===Joomla Security Strike Team===
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 Mark Dexter. Thanks!

* Coordinator: Mark Dexter (mailto:mark.dexter@community.joomla.org).
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===Multi-site Working Group===

* Coordinator: Christophe Demko (mailto:christophe.demko@joomla.org).
* PLT Contact: Christophe Demko (mailto:christophe.demko@joomla.org).

===Message Queue Working Group===

* Coordinator: Chris Davenport (mailto:chris.davenport@joomla.org)
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see: [[Message Queue Working Group]].

===Search Working Group===
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: To be determined.
* PLT Contact: Chris Davenport (mailto:chris.davenport@joomla.org)

For further information see [[Search Working Group]]

===Translations Working Group===
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

===Unified Content Model Working Group===
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: To be determined.
* PLT Contact: To be determined.

===Unit Tests for CMS Working Group===

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

===Update and Migration Working Group===

* Coordinator: To be determined.
* PLT Contact: Mark Dexter (mailto:mark.dexter@community.joomla.org).

===User Experience Working Group===
The [[User Experience Working Group|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 [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: Ron Severdia (mailto:ron.severdia@joomla.org)
* PLT Contact: Ron Severdia (mailto:ron.severdia@joomla.org)

===Web Services Working Group===

* Coordinator: To be determined.
* PLT Contact: To be determined.

==Proposing a new working group==
If you would like to propose a new working group to be added to this list, please follow this procedure:-
* choose a title for the working group.
* write a brief overview of the job that the working group will do.
* list the success criteria for the working group.
* list the initial coordinator (or coordinators if more than one), with contact email address(es).
* send your proposal to Chris Davenport [mailto:chris.davenport@joomla.org] who will ensure that your proposal is considered by the PLT.

==See also==
* [http://developer.joomla.org/news/359-new-production-working-groups.html Announcement on developer.joomla.org]
* [http://community.joomla.org/blogs/community/1496-join-or-start-a-production-working-group.html Announcement blog post]

[[Category:Development]]
[[Category:Working_Groups]]

Welcome to the Bug Squad

2012-04-06T00:08:18Z

Sueter: /* JBS In a Nutshell */

Welcome to the Joomla Bug Squad (JBS)! This article is for new Joomla Bug Squad members and also for people who might be thinking about joining JBS.

===JBS In a Nutshell===

; Who is in JBS? : The JBS is a team of incredibly capable and friendly volunteers. JBS members have varying amounts of experience with Joomla and with programming. You don't have to be a Joomla or PHP expert to contribute to the JBS.

; What do we do? : We report, track, test, and fix bugs in the current Joomla release and we help debug new major releases. A detailed description is available in the [[Bug Squad]] article.

; Where do we hang out? : JBS members meet for informal communications on the Joomla! Bug Squad IRC channel at #joomla-bug-squad. As of April 2011, we also have a Skype chat just for JBS members. To join, please email Mark Dexter. These are places where you can "check in", see what is going on, ask and answer questions, and get to know your fellow JBS members. We also have a Google group for more formal questions and discussions at [http://groups.google.com/group/joomlabugsquad http://groups.google.com/group/joomlabugsquad]. JBS members also monitor the [http://forum.joomla.org/viewforum.php?f=199&sid=eb2adfe2a7fb9f405660b73e05111c4b Joomla! 1.5.x_Q&T forum].

; When do we fix bugs? :Any time is a great time to fix a bug! Reporting and fixing bugs is a continuous, on-going process.

; How do we do it? : The central focus of our work is the tracker at Joomlacode.org. For version 2.5, we use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker]. For version 1.5, we use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=32 Joomla! 1.5.x Bug Tracker]. Most of our work at this point will be in version 2.5.

: The tracker lists all reported bugs and tracks their progress from the initial report to final resolution. For more information about how the Tracker works, see the [[Bug Tracking Process]] article or you can look at a 30-minute webinar called [[Webinar:_Overview_of_Tracker_Process|Overview of the Tracker Process]]. Many of us who do programming use Eclipse, which is a free IDE (integrated development environment) for working with PHP programs like Joomla. Detailed instructions for setting up your workstation for Joomla programming with Eclipse are available [[Setting_up_your_workstation_for_Joomla!_development|here]].

As of May 2010, we are five teams within JBS, as follows:
* Tracker Team
* Coding Team
* Testing Team
* Automated Testing Team
* Upgrade / Migration Team

You can read more about these in the general description of the [[Bug Squad]].

; Why JBS? : Because we want Joomla to be as high quality and bug-free as is humanly possible.

===Overview of JBS Process===
For a description of the way the JBS works, see the [[Joomla! Maintenance Procedures]] article. Also, you can watch a 30-minute webinar called [[Webinar:_Overview_of_Tracker_Process|Overview of the Tracker Process]].

===More Information===
There is a lot of great information for JBS members on the Joomla wiki site under the heading [[:Category:Bug Squad]]. Also, and very importantly, we treat everyone with respect and consideration and take the [[Code_of_conduct | Joomla code of conduct]] very seriously.

[[Category:Bug Squad]]

Category:Version 2.5.4 FAQ

2012-03-31T16:20:16Z

Sueter: Created page with "These FAQs are specific to the Joomla 2.5.4 release. Only issues that are specific to this release will be listed here, together with suggested resolutions. Please add informati..."

These FAQs are specific to the Joomla 2.5.4 release. Only issues that are specific to this release will be listed here, together with suggested resolutions. Please add information to this resource. The Joomla Bug Squad will watch over this page to ensure any new bugs are added to the tracker and resolved. Continue to use the Joomla forums for support requests as this is not a substitute for posting there, but rather a common location for the community to gather release issues.

[[Category:Version 2.5 FAQ]]
[[Category:Joomla! 2.5]]