Joomla! Documentation - User contributions [en]

Joomla! Extension Directory FAQs

2010-03-16T14:03:53Z

Masini: /* The JED Team */

==Extensions' submission, approval and rejection==

===How do I list my extension in the extensions site?===
Information on how to list extensions in the extensions site is available here:
http://extensions.joomla.org/help2?start=2

===How long do I need to wait before my extension is approved?===
JED is run by a team of volunteers who contribute their time and effort to manage the directory. Because of this, the approval time is largely based on the team's availability. 14 days is a reasonable time to wait before your extension is looked in to. You can get an estimate on our approval rate by looking at the number of extensions ahead of yours that are also pending approval. This information can be found by logging in to your JED account, go to 'My Page' and click 'Edit' on the extension that is pending approval.

===Why was my extension rejected from being listed?===
Some of the common reasons extensions are rejected:

*extension cannot be downloaded or found on the site.
*extension does not install.
*extension is not licensed under GPL.
*extension is not compatible with Joomla! 1.5.
*does not have [http://opensourcematters.org/index.php?option=com_content&view=article&id=86 permission to use Joomla trademark].

===How can I help to speed up my extension's approval time?===
There are several ways you can help the extension submission process go faster and smoother.
As you may know, the Joomla! Extension Directory is supported by volunteers and it takes time to go through all the extensions.
You can help to speed up the approval process by making sure your extension:

* uses GPL license.
* is compatible with Joomla! 1.5.
* has valid links.
* is installable on Joomla! 1.5 unless your submission is submitted under Tools category.
* [http://opensourcematters.org/logo-usage-and-brand-guide.html follows Joomla's Logo and Brand guidelines].
* has [http://opensourcematters.org/index.php?option=com_content&view=article&id=86 permission to use Joomla trademark] if your extension or site uses Joomla!'s trademark.
* is downloadable by front-end/public/guest user.
* is installable without error.

===Can I submit Joomla! 1.0 compatible extensions?===
Begining March 31st 2009, JED no longer accepts Joomla! 1.0 compatible-only extensions. However, it is perfectly OK if your extension is compatible with Joomla! 1.0 and Joomla! 1.5. Read http://community.joomla.org/blogs/community/629-jed-will-phase-out-joomla-10-extensions-in-june-2009.html for more information.

===Can I submit non-GPL licensed extensions?===
No. Begining March 1st 2009, only Joomla! extensions licensed under the GNU GPL will be accepted into the JED. Read this blog post for more information - http://community.joomla.org/blogs/leadership/636-jed-to-be-gpl-only-by-july-2009.html

==Reviews==

===Why was my review of an extension is rejected, removed and/or edited?===
The following are some reasons why your review may have been rejected, removed or edited:
*Spam and/or self-promotion.
*Feature requests. Send feature requests to the developer.
*Support requests. Send support requests to the developer.
*Bug reports. Send bug reports to the developer.
*Your review does not show that you used the extension.
*Not a review of the product.
*Putting some type of code. The review section doesn't like code languages.
*Commercial disputes. Instead, report the extension.
*Complaints about licenses, download policies, and version compatibility.

===I submitted a review yesterday but it is not shown yet, why?===
All reviews are being manually approved by the Editorial Team, and some submissions will be considered borderline and therefore gets a comment and awaits a second opinion from another editor.

===How can I change or delete a review that I submitted earlier?===
Please use the ‘Report this review’ button next to the review, and explain what changes you would like added or if you wish to have the review removed in order to be able to submit a new and updated review. By using the ‘Report this review’ we will be able to see that the request is made by the same user who originally created the review.

===How can I as a developer get in contact with this particular reviewer?===
You can´t. Identity of JED users will never be revealed. What we can do is to invite a user to contact developer when developer wants to help out with an issue raised in reviews. Developer should then provide us with contact details, and then we will provide this information to the user.

==Categorization==

===Can I suggest some changes to categorization?===
Categories in JED is constantly evolving to cope with the increasing amount of extensions. We strive to provide a good categorization to fit all extensions listed in JED. If you feel that an extension deserved to be in another existing or new category, please use the "Report This" button and let us know about your suggestion. You can also post your feedback to our forum.

===Which category should I publish my extension?===
If you are unsure where to publish your extension, a good starting point would be to look at other related extensions and find where they are listed.

===Can I submit multiple listings at different categories for the same extension?===
No. You are allowed to list your extension once in a category in JED.

===Can I have my extensions listed at different categories?===
No. Extensions can be listed in one category only.

===What should I do if my extension is suitable to be listed in multiple categories?===
We suggest that you use the Description field in your extension listing to communicate the suitability of your extension in other areas.

==Directory==

===When is an extension considered ‘Popular’?===
Extension will be shown as ‘Hot’ when it has an average of 150 views or more per day.

===For how long is the tag ‘Just Added’ used?===
An extension will be tagged as ‘Just Added’ for 14 days from the days it is approved and published.

===What is the calculation for an extension to be ‘Top Rated’?===
An extension has to have at least 15 votes to be eligible to be listed as Top Rated Extension. Top Rated extensions are ordered by the average rating given by users.

===What is the calculation for an extension to be ‘Most Popular’?===
Extensions with the highest view of all time are listed in [http://extensions.joomla.org/extensions/popular Popular Extensions].

===How is ‘Most Reviewed’ list calculated?===
Extensions with the highest number of reviews are listed in [http://extensions.joomla.org/extensions/most-reviewed Most Reviewed].

===When is an extension listed in ‘Recently Updated’ page?===
Extensions will be listed in [http://extensions.joomla.org/extensions/updated Recently Update] here when they are updated with new version.

===How are extensions selected to be shown in JED's front page?===
There are 4 main modules in JED's front page.

* '''''Random New Extensions''''' module randomly shows 12 extensions added in the past 4 weeks. All extensions added in this period have equal chance of appearing in the module.

* '''''New and Noteworthy''''' module shows 4 most viewed extensions added in the past 2 weeks. In another words, these are popular new extensions added in the past 2 weeks. Additionally, only listings that have uploaded image are considered in this module.

* '''''Recently Updated''''' module shows 12 most recently updated extensions in JED. Extensions are considered 'updated' when their version information is changed.

* '''''Random Extensions''''' module randomly shows 2 extensions with image.

===What component is used to manage Joomla! Extensions Directory?===
The directory component used at Joomla! Extensions Directory is [http://extensions.joomla.org/extensions/233/details Mosets Tree] by a company called [http://www.mosets.com Mosets].

==The JED Team==

===Members===
The current JED Editorial Team consists of:
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=726 Lorenzo Garcia]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=79 Lee Cher Yeong]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=32483 Geoff Cheung]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=25584 Victor Drover]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6515 Paulo Izidoro]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=46545 Steve Burge]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=35733 Toni Marie]
* [http://www.all-auto.ro/asigurari-auto Rca Ieftin]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007 Aaron St. George]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=19591 Norm Douglas]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=59328 Peter van Westen]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=23008 TJ]

===Contacting the team===
The editors can be reached at [http://forum.joomla.org/viewforum.php?f=262 Joomla! Extensions Directory Forum] or by e-mail [mailto:team@extensions.joomla.org team@extensions.joomla.org]

<noinclude>[[Category:FAQ]]</noinclude>

Joomla! Extension Directory FAQs

2010-03-16T14:03:34Z

Masini: /* The JED Team */

==Extensions' submission, approval and rejection==

===How do I list my extension in the extensions site?===
Information on how to list extensions in the extensions site is available here:
http://extensions.joomla.org/help2?start=2

===How long do I need to wait before my extension is approved?===
JED is run by a team of volunteers who contribute their time and effort to manage the directory. Because of this, the approval time is largely based on the team's availability. 14 days is a reasonable time to wait before your extension is looked in to. You can get an estimate on our approval rate by looking at the number of extensions ahead of yours that are also pending approval. This information can be found by logging in to your JED account, go to 'My Page' and click 'Edit' on the extension that is pending approval.

===Why was my extension rejected from being listed?===
Some of the common reasons extensions are rejected:

*extension cannot be downloaded or found on the site.
*extension does not install.
*extension is not licensed under GPL.
*extension is not compatible with Joomla! 1.5.
*does not have [http://opensourcematters.org/index.php?option=com_content&view=article&id=86 permission to use Joomla trademark].

===How can I help to speed up my extension's approval time?===
There are several ways you can help the extension submission process go faster and smoother.
As you may know, the Joomla! Extension Directory is supported by volunteers and it takes time to go through all the extensions.
You can help to speed up the approval process by making sure your extension:

* uses GPL license.
* is compatible with Joomla! 1.5.
* has valid links.
* is installable on Joomla! 1.5 unless your submission is submitted under Tools category.
* [http://opensourcematters.org/logo-usage-and-brand-guide.html follows Joomla's Logo and Brand guidelines].
* has [http://opensourcematters.org/index.php?option=com_content&view=article&id=86 permission to use Joomla trademark] if your extension or site uses Joomla!'s trademark.
* is downloadable by front-end/public/guest user.
* is installable without error.

===Can I submit Joomla! 1.0 compatible extensions?===
Begining March 31st 2009, JED no longer accepts Joomla! 1.0 compatible-only extensions. However, it is perfectly OK if your extension is compatible with Joomla! 1.0 and Joomla! 1.5. Read http://community.joomla.org/blogs/community/629-jed-will-phase-out-joomla-10-extensions-in-june-2009.html for more information.

===Can I submit non-GPL licensed extensions?===
No. Begining March 1st 2009, only Joomla! extensions licensed under the GNU GPL will be accepted into the JED. Read this blog post for more information - http://community.joomla.org/blogs/leadership/636-jed-to-be-gpl-only-by-july-2009.html

==Reviews==

===Why was my review of an extension is rejected, removed and/or edited?===
The following are some reasons why your review may have been rejected, removed or edited:
*Spam and/or self-promotion.
*Feature requests. Send feature requests to the developer.
*Support requests. Send support requests to the developer.
*Bug reports. Send bug reports to the developer.
*Your review does not show that you used the extension.
*Not a review of the product.
*Putting some type of code. The review section doesn't like code languages.
*Commercial disputes. Instead, report the extension.
*Complaints about licenses, download policies, and version compatibility.

===I submitted a review yesterday but it is not shown yet, why?===
All reviews are being manually approved by the Editorial Team, and some submissions will be considered borderline and therefore gets a comment and awaits a second opinion from another editor.

===How can I change or delete a review that I submitted earlier?===
Please use the ‘Report this review’ button next to the review, and explain what changes you would like added or if you wish to have the review removed in order to be able to submit a new and updated review. By using the ‘Report this review’ we will be able to see that the request is made by the same user who originally created the review.

===How can I as a developer get in contact with this particular reviewer?===
You can´t. Identity of JED users will never be revealed. What we can do is to invite a user to contact developer when developer wants to help out with an issue raised in reviews. Developer should then provide us with contact details, and then we will provide this information to the user.

==Categorization==

===Can I suggest some changes to categorization?===
Categories in JED is constantly evolving to cope with the increasing amount of extensions. We strive to provide a good categorization to fit all extensions listed in JED. If you feel that an extension deserved to be in another existing or new category, please use the "Report This" button and let us know about your suggestion. You can also post your feedback to our forum.

===Which category should I publish my extension?===
If you are unsure where to publish your extension, a good starting point would be to look at other related extensions and find where they are listed.

===Can I submit multiple listings at different categories for the same extension?===
No. You are allowed to list your extension once in a category in JED.

===Can I have my extensions listed at different categories?===
No. Extensions can be listed in one category only.

===What should I do if my extension is suitable to be listed in multiple categories?===
We suggest that you use the Description field in your extension listing to communicate the suitability of your extension in other areas.

==Directory==

===When is an extension considered ‘Popular’?===
Extension will be shown as ‘Hot’ when it has an average of 150 views or more per day.

===For how long is the tag ‘Just Added’ used?===
An extension will be tagged as ‘Just Added’ for 14 days from the days it is approved and published.

===What is the calculation for an extension to be ‘Top Rated’?===
An extension has to have at least 15 votes to be eligible to be listed as Top Rated Extension. Top Rated extensions are ordered by the average rating given by users.

===What is the calculation for an extension to be ‘Most Popular’?===
Extensions with the highest view of all time are listed in [http://extensions.joomla.org/extensions/popular Popular Extensions].

===How is ‘Most Reviewed’ list calculated?===
Extensions with the highest number of reviews are listed in [http://extensions.joomla.org/extensions/most-reviewed Most Reviewed].

===When is an extension listed in ‘Recently Updated’ page?===
Extensions will be listed in [http://extensions.joomla.org/extensions/updated Recently Update] here when they are updated with new version.

===How are extensions selected to be shown in JED's front page?===
There are 4 main modules in JED's front page.

* '''''Random New Extensions''''' module randomly shows 12 extensions added in the past 4 weeks. All extensions added in this period have equal chance of appearing in the module.

* '''''New and Noteworthy''''' module shows 4 most viewed extensions added in the past 2 weeks. In another words, these are popular new extensions added in the past 2 weeks. Additionally, only listings that have uploaded image are considered in this module.

* '''''Recently Updated''''' module shows 12 most recently updated extensions in JED. Extensions are considered 'updated' when their version information is changed.

* '''''Random Extensions''''' module randomly shows 2 extensions with image.

===What component is used to manage Joomla! Extensions Directory?===
The directory component used at Joomla! Extensions Directory is [http://extensions.joomla.org/extensions/233/details Mosets Tree] by a company called [http://www.mosets.com Mosets].

==The JED Team==

===Members===
The current JED Editorial Team consists of:
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=726 Lorenzo Garcia]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=79 Lee Cher Yeong]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=32483 Geoff Cheung]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=25584 Victor Drover]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6515 Paulo Izidoro]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=46545 Steve Burge]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=35733 Toni Marie]
* [http://www.all-auto.ro/asigurari auto Rca Ieftin]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=97007 Aaron St. George]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=19591 Norm Douglas]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=59328 Peter van Westen]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=23008 TJ]

===Contacting the team===
The editors can be reached at [http://forum.joomla.org/viewforum.php?f=262 Joomla! Extensions Directory Forum] or by e-mail [mailto:team@extensions.joomla.org team@extensions.joomla.org]

<noinclude>[[Category:FAQ]]</noinclude>

Documentation Working Group

2010-03-16T14:01:10Z

Masini: /* Other public resources */

The Documentation Team is Part of the Production Working Group. It is responsible for creating and maintaining all the official Joomla! documentation including that for end-users, administrators and third-party developers. We also maintain the help screens for the Joomla! releases.

The official documentation language is British/Australian. Translations of the official documentation into other languages are the responsibility of the [[Translations Working Group]].

==Websites==
The Documentation Working Group currently maintains the following websites:
===[http://api.joomla.org api.joomla.org]===
This entire site is automatically generated by the phpDocumentor package from an analysis of the Joomla! source code and making use of specially formatted comments embedded in the source code itself. It is an invaluable tool for all Joomla! developers.
===[http://docs.joomla.org docs.joomla.org]===
The concept behind '''docs.joomla.org''' is that it will become the central resource for developing single-source modular documentation within the Joomla! project. The idea is that we write stuff once then re-use it in a somewhat analogous way to modern OOP software development. In the future we expect that other sites, such as [http://help.joomla.org help.joomla.org] and [http://developer.joomla.org developer.joomla.org] will contain some, or even most, of their content derived from sources here. By building a central database of document "chunks" we gain maximum benefit from the efforts of a limited number of authors and we produce "agile" documents where a single change is rapidly propagated to all the derived documents affected.</p><p>Those interested in the techniques will find more information [[Modular Documentation|here]].
===[http://help.joomla.org help.joomla.org]===
The official help site houses much of our early documentation, including that for Joomla! 1.0.x, the help screens for all Joomla! versions and the Joomla! 1.5 Installation Guide.
* [[Help screens|Joomla! 1.5.x help screens]] are created on this wiki before being moved to [http://help.joomla.org/content/section/42/278/ help.joomla.org]
* [http://help.joomla.org/content/section/16/276/ Joomla! 1.0.x help screens] Note: These are no longer being maintained.
* [[Creating a Joomla! 1.5 help screens SQL dump]]
* [http://joomlacode.org/gf/project/joomla/docman/?subdir=6 Help screens SQL dump files] for Joomla! versions up to 1.5.x.

==Documentation wiki==
{{:Documentation wiki}}
==Other public resources==
* [http://community.joomla.org/contributors/documentors.html Documentation Working Group blog]
* [[jforum:303|Public discussion forum]]
* [http://dev.joomla.org/component/option,com_jd-wiki/Itemid,32/ Developer wiki] Note: All useful material has now been moved from this wiki to here.
* [http://groups.google.com/group/joomla-docs Documentation Working Group mailing list]
* [http://groups.google.com/group/joomla-devel-docs Developer documentation mailing list]
* [http://www.all-auto.ro/tractari-auto tractari auto]
* [[Project:MediaWiki setup notes|MediaWiki setup notes]]
* [http://forum.joomla.org/viewtopic.php?f=502&t=268156 Help screens white paper proposal] for Joomla! 1.6 onwards
* [[Documentors]] profile in this wiki.
[[Category:Documentation Working Group]]

Development Working Group

2010-03-16T13:59:49Z

Masini: /* Miscellaneous */

{{incomplete}}[[Image:workgroups_development.jpg|right]]

== Introduction ==

'''''"..To develop a cutting edge, state of the art Web Content Management application framework..."'''''

The main responsibility of the [[Development Working Group]] is taking care of the development of the Joomla! application framework and the Joomla! Content Management System (CMS). Besides the development of the Joomla! codebase the development working group defines the Joomla! roadmap strategy, creating (architectural) designs for major and minor versions and of course take care of bug and security fixes in maintenance versions.

The development working group holds two teams: the [[Development Team]] and the so called [[Bug Squad]]. Both teams have a separate responsibility but together they form the development force for the Joomla! project.

Joomla! is as every other open-source project based upon the fundaments of collaborative and is a community-driven project. This means that the software, the documentation, the ever growing number of available the extensions, support (forum, mailing, lists newsletters, user groups are collaboratively produced by users and developers all over the world.

In this section of the documentation wiki we have tried to describe all relevant aspects to Joomla! development. OUr effort strives to be as complete as we can be, but we don't rule out that information you are looking for is not (yet) documented. We encourage everyone to help completing the documentation effort and maximize the community effect within the Joomla! project.

== Getting started ==

The amount of information that is available from this page is like a small (e-)book. We tried to organize the information in a logical order, and also structure the information in the most efficient way. To prevent you from reading for some hours, we use a simple documentation method. Per topic we draft a short description on the information that can be found, and in the linked pages we will provide as much as possible detail. Keep in mind that you can use the free-text search or the generated table of contents for this documentation category to find your information. If there is information missing, feel free to add this within this wiki.

* [[First look around]]
* [[Guide to the Development Documentation wiki section]]

== Technical infrastructure ==

For collaboration we have set up an infrastructure like version control, the bug tracker and of course this wiki for documentation. These assets are essential for Joomla! development. Below you will find links to the infrastructure that is used within the Joomla! project.

* [[Mailing lists]]
* [[Version control]]
* [[Bug tracker]]
* [[IRC/Real-Time Chat]]
* [[Wikis]]
* [[Web sites]]
* [[Joomlacode]]

== Social and Political Infrastructure ==

Ready for something more heavy at tea? Then you're in the right place here ;-) In this section we describe the basic organizational structures we have put in place, but probably at least important we describe the code of conduct we follow. For open source projects this is especially important because we have no hierarchical relation with our volunteers, the Joomla! project follows the [[http://producingoss.com/en/consensus-democracy.html Consensus Based Democracy]] model.

* [[Organizational structure]]
* [[Code of conduct]]

== Communications ==

There are several ways to get in touch, or communicate with the development community of Joomla! Within the working groups we try to share as much as possible information, using different media. It is a mix of tools and events we organized, details can be found in the links below.

* [http://developer.joomla.org/section-blog.html Development blog]
* [http://developer.joomla.org/gsoc2008.html Summer of Code blog]
* [http://developer.joomla.org/bug-squad-blog.html Bug Squad blog]
* [http://forum.joomla.org/viewforum.php?f=509&sid=fb99f7b1a81437ff25e8dd707343bae0 Development forum]
* [[Development meetings]]
* [http://www.google.com/calendar/embed?src=calendar@joomla.org Joomla! events]
* [http://community.joomla.org/joomla-user-groups.html Local user groups]
* [http://docs.joomla.org/Pizza_Bugs_and_Fun_2 Pizza Bugs and Fun]
* [http://www.all-auto.ro/auto-second-hand vanzari auto]

== Packaging, releasing and daily development ==

* Release numbering
* Release branches
* Sandboxes
* Stabilizing a release
* Packaging
* Testing and releasing
* Maintaining multiple release lines (general description, and our current release lines)
* Releases and daily development

== Development community ==

* How to get involved?
* 3rd party development
* Interesting topics to study
* Recommended readings and books

== Licensing and copyrights ==

* General Public License

== How to contribute to Joomla! development ==

== Coding standards ==
A list of Joomla! coding standards as of 13 February 2010 can be found here: [[Coding style and standards]].

== Writing secure Joomla! code ==

* [http://developer.joomla.org/tutorials/181-preventing-sql-injections.html Preventing SQL injections]
* [[Secure coding guidelines]]

== Unit testing within Joomla! ==

The goal of unit testing is to isolate each part of the program and show that the individual parts are correct. A unit test provides a strict, written contract that the piece of code must satisfy. As a result, it affords several benefits. Unit tests find problems early in the development cycle.

In computer programming, unit testing is a method of testing that verifies the individual units of source code are working properly. A unit is the smallest testable part of an application. In procedural programming a unit may be an individual program, function, procedure, etc., while in object-oriented programming, the smallest unit is a method, which may belong to a base/super class, abstract class or derived/child class.

Ideally, each test case is independent from the others; Double objects like stubs, mock or fake objects as well as test harnesses can be used to assist testing a module in isolation. Unit testing is typically done by software developers to ensure that the code they have written meets software requirements and behaves as the developer intended.

Ground work on the implementation of unit testing has been done by Enno Klasing during the Summer of Code 2007 project and has been perfected by Alan Langford from the Joomla! [[Development Team]]. The way [[Unit Testing]] is implemented within the Joomla! project has been documented in the [[Unit Testing]] chapter.

* [[Unit Testing]]

== What does a Joomla! development environment look like ==

== Debugging your Joomla! code ==
One way to debug Joomla! code is using the open-source programs Eclipse and XDebug. Instructions for setting up these programs is available in [[Setting up your workstation for Joomla! development]].

== Joomla! organization ==

* An explanation on how the [[Development Team]] is organized.
* An explanation on how the [[Bug Squad]] is organized.

== Joomla! planning process and procedures ==
* Description on the [[Development Strategy of Joomla!]]
* A description of how the [[Joomla! Maintenance Procedures]] are organized
* [[Release procedure and checklist]]
* [[Team member administration]]

== Miscellaneous ==

This is "old" content and needs to be moved to the final location in this wiki, work in progress...

* [[Unit Testing]] within the Joomla! project
* [[The use of Subversion]]
* [http://www.all-auto.ro/piese-auto piese auto online]
<noinclude>[[Category:Development Working Group]]</noinclude>

Development Working Group

2010-03-16T13:57:15Z

Masini:

{{incomplete}}[[Image:workgroups_development.jpg|right]]

== Introduction ==

'''''"..To develop a cutting edge, state of the art Web Content Management application framework..."'''''

The main responsibility of the [[Development Working Group]] is taking care of the development of the Joomla! application framework and the Joomla! Content Management System (CMS). Besides the development of the Joomla! codebase the development working group defines the Joomla! roadmap strategy, creating (architectural) designs for major and minor versions and of course take care of bug and security fixes in maintenance versions.

The development working group holds two teams: the [[Development Team]] and the so called [[Bug Squad]]. Both teams have a separate responsibility but together they form the development force for the Joomla! project.

Joomla! is as every other open-source project based upon the fundaments of collaborative and is a community-driven project. This means that the software, the documentation, the ever growing number of available the extensions, support (forum, mailing, lists newsletters, user groups are collaboratively produced by users and developers all over the world.

In this section of the documentation wiki we have tried to describe all relevant aspects to Joomla! development. OUr effort strives to be as complete as we can be, but we don't rule out that information you are looking for is not (yet) documented. We encourage everyone to help completing the documentation effort and maximize the community effect within the Joomla! project.

== Getting started ==

The amount of information that is available from this page is like a small (e-)book. We tried to organize the information in a logical order, and also structure the information in the most efficient way. To prevent you from reading for some hours, we use a simple documentation method. Per topic we draft a short description on the information that can be found, and in the linked pages we will provide as much as possible detail. Keep in mind that you can use the free-text search or the generated table of contents for this documentation category to find your information. If there is information missing, feel free to add this within this wiki.

* [[First look around]]
* [[Guide to the Development Documentation wiki section]]

== Technical infrastructure ==

For collaboration we have set up an infrastructure like version control, the bug tracker and of course this wiki for documentation. These assets are essential for Joomla! development. Below you will find links to the infrastructure that is used within the Joomla! project.

* [[Mailing lists]]
* [[Version control]]
* [[Bug tracker]]
* [[IRC/Real-Time Chat]]
* [[Wikis]]
* [[Web sites]]
* [[Joomlacode]]

== Social and Political Infrastructure ==

Ready for something more heavy at tea? Then you're in the right place here ;-) In this section we describe the basic organizational structures we have put in place, but probably at least important we describe the code of conduct we follow. For open source projects this is especially important because we have no hierarchical relation with our volunteers, the Joomla! project follows the [[http://producingoss.com/en/consensus-democracy.html Consensus Based Democracy]] model.

* [[Organizational structure]]
* [[Code of conduct]]

== Communications ==

There are several ways to get in touch, or communicate with the development community of Joomla! Within the working groups we try to share as much as possible information, using different media. It is a mix of tools and events we organized, details can be found in the links below.

* [http://developer.joomla.org/section-blog.html Development blog]
* [http://developer.joomla.org/gsoc2008.html Summer of Code blog]
* [http://developer.joomla.org/bug-squad-blog.html Bug Squad blog]
* [http://forum.joomla.org/viewforum.php?f=509&sid=fb99f7b1a81437ff25e8dd707343bae0 Development forum]
* [[Development meetings]]
* [http://www.google.com/calendar/embed?src=calendar@joomla.org Joomla! events]
* [http://community.joomla.org/joomla-user-groups.html Local user groups]
* [http://docs.joomla.org/Pizza_Bugs_and_Fun_2 Pizza Bugs and Fun]
* [http://www.all-auto.ro/auto-second-hand vanzari auto]

== Packaging, releasing and daily development ==

* Release numbering
* Release branches
* Sandboxes
* Stabilizing a release
* Packaging
* Testing and releasing
* Maintaining multiple release lines (general description, and our current release lines)
* Releases and daily development

== Development community ==

* How to get involved?
* 3rd party development
* Interesting topics to study
* Recommended readings and books

== Licensing and copyrights ==

* General Public License

== How to contribute to Joomla! development ==

== Coding standards ==
A list of Joomla! coding standards as of 13 February 2010 can be found here: [[Coding style and standards]].

== Writing secure Joomla! code ==

* [http://developer.joomla.org/tutorials/181-preventing-sql-injections.html Preventing SQL injections]
* [[Secure coding guidelines]]

== Unit testing within Joomla! ==

The goal of unit testing is to isolate each part of the program and show that the individual parts are correct. A unit test provides a strict, written contract that the piece of code must satisfy. As a result, it affords several benefits. Unit tests find problems early in the development cycle.

In computer programming, unit testing is a method of testing that verifies the individual units of source code are working properly. A unit is the smallest testable part of an application. In procedural programming a unit may be an individual program, function, procedure, etc., while in object-oriented programming, the smallest unit is a method, which may belong to a base/super class, abstract class or derived/child class.

Ideally, each test case is independent from the others; Double objects like stubs, mock or fake objects as well as test harnesses can be used to assist testing a module in isolation. Unit testing is typically done by software developers to ensure that the code they have written meets software requirements and behaves as the developer intended.

Ground work on the implementation of unit testing has been done by Enno Klasing during the Summer of Code 2007 project and has been perfected by Alan Langford from the Joomla! [[Development Team]]. The way [[Unit Testing]] is implemented within the Joomla! project has been documented in the [[Unit Testing]] chapter.

* [[Unit Testing]]

== What does a Joomla! development environment look like ==

== Debugging your Joomla! code ==
One way to debug Joomla! code is using the open-source programs Eclipse and XDebug. Instructions for setting up these programs is available in [[Setting up your workstation for Joomla! development]].

== Joomla! organization ==

* An explanation on how the [[Development Team]] is organized.
* An explanation on how the [[Bug Squad]] is organized.

== Joomla! planning process and procedures ==
* Description on the [[Development Strategy of Joomla!]]
* A description of how the [[Joomla! Maintenance Procedures]] are organized
* [[Release procedure and checklist]]
* [[Team member administration]]

== Miscellaneous ==

This is "old" content and needs to be moved to the final location in this wiki, work in progress...

* [[Unit Testing]] within the Joomla! project
* [[The use of Subversion]]
<noinclude>[[Category:Development Working Group]]</noinclude>