Joomla! Documentation - User contributions [en]

Archived:Summer of Code 2009 Project Ideas

2009-03-16T21:07:37Z

Willebil: /* Advanced Poll/Survey Suite */

[[Image:Gsoc_2009_logo.png|right]]

===Welcome!===
Welcome to the Joomla! Google Summer of Code (GSoC) 2009 project ideas page. As we move forward with the 2009 version of the Joomla! GSoC, we will use this page to develop possible project ideas. Please note that anyone who is interested can participate in this process. You do not have to be a GSoC student or mentor to suggest possible project ideas. Thanks!

===Ideas===

=====Advanced Poll/Survey Suite=====

The core polls extension has been removed from Joomla! 1.6. Develop a fully featured poll/survey suite that will allow relatively simple user polls and the collection of complex anonymized survey data authenticated against either the Joomla users database or an external database.

'''Mentor:''' Wilco Jansen (subject to change)

'''Skills:''' Joomla CMS framework, MVC, PHP 5.2, MySQL

'''Difficulty:''' medium

=====Full Frontend Editing=====

Right now we only have frontend editing for articles, there are a few improvements I can propose
* Article editing is done in a modal popup
* Edit module content and params from frontend (Editing done via a modal popup?)
* Article Title - edit in place
* Create some kind of a library function which allows easy frontend editing for any value (This will need some thought)

=====Template Manager Improvements/Advanced Template Manager=====

Extend the template manager so that it providers an better environment for template creation and modification. Improvements might include:
*expanded tool bar, including copy for a complete template
*access to the media manager
*access to all template files (not just css and index.php)
*override manager
*integration of an editor with code highlighting (such as codepress)
*support for template parameter groups
*remove hard-wired references to template name from the core templates (so the new copy function will work as expected)
*"export" button on the toolbar which will create a zip package file containing the template (also fixes any errors in the templateDetails.xml file as it goes).

=====Work Flow Extension=====

Create a 1.6 Extension to flexibly manage workflow for com_content.
Ideally it should be extensible to other components, but com_content should be used as the proof of concept.
Work flow should manage the publication process, including assignment of editors or publishers to specific content items, notifications of relevant actions to specific individuals or groups, change of status to block author editing of published work.

As much as possible administrators should be able to construct their own work flows.

=====Page Versioning Extension=====

Create a 1.6 content versioning extension with the goal that this work could be integrated into the core Joomla CMS for future releases.
The Page Versioning Extension will allow the ability for frontend and backend content users to be able to save and re-publish/revert previously saved versions of content items that they have access to.

Further user permissions could be introduced in order to restrict access to this overall feature.

Features could include a visual and html code difference between the current and previously saved versions, as well as general searching data such as dates and time of previous saved entries of that content.

=====Taxonomy Extension=====

Create a 1.6 Taxonomy extension with the goal that this work could be integrated into the core Joomla CMS for future releases.
The Taxonomy Extension will allow the ability to organise content for classification, improving on the current Section and Categories classification.

Taxonomy is a vital feature of modern CMS solutions, evolving from the previous "pigeonholeing" of a content item.
Full organisational structures and multi tagging of content could be included, including powerful search functions of content under those classifications.

Taxonomy is a missing feature in Joomla!, which another open-source competitor product currently offers. We have seen a number of opportunities when Joomla! misses out on being the chosen option for a CMS due to the lacking of this feature.

=====Keywords Management Extension=====
Keywords in articles are an important part of many Joomla! sites. They are used for page rankings but also can be used with Related Articles modules and component extensions. In this capacity, they provide a way to relate articles that is much more flexible and free-form than the built-in Section / Category / Article hierarchy.

Currently in Joomla!, keywords are entered when editing each individual article. This has several disadvantages, including:
* You cannot see already existing keywords when entering in keywords for an article.
* You cannot see existing articles that are already associated with a keyword.
* It is difficult to be consistent when using keywords. For example, should it be capitalized, singular or plural ("Dog" or "Dogs"), and so on.

To deal with these issues, a back-end Keyword Management extension is proposed. This extension would allow the following capabilities:
* A management screen showing a list of all keywords currently in use. This would provide the ability to drill into any keyword and see all articles that use this keyword.
* A keyword picker screen. This would allow an author to pick keywords for an article from a list of existing keywords. This would make it easier to ensure consistency in spelling, capitalization, and usage between keywords. This screen would also allow the author to add a new keyword to the list.
* The ability to do global search and replace on keywords.
* The ability to see keywords ranked by frequency of use.
* The ability to list articles to which no keywords have been assigned.

=====User-Defined List and Blog Layout Extension=====
Currently in Joomla!, there are built-in Menu Items for list and blog layouts for Sections and Categories. However, the way a list of articles is selected is tightly bound with the way the list is displayed on the page. In theory, you should be able to have a list or blog layout that shows any selection of articles.

To provide this capability, an extension is proposed that would provide layouts similar to the current list and blog layouts. However, the extension would be designed so that the list of articles is provided by a plugin instead of being integrated into the layout. Example plugins could be provided to mimic the current Section, Article, and Front Page layouts. However, the power of this extension is that the user could add their own plugin that would provide a list of articles using any type of query. This list of articles would then feed into the built-in layouts provided by the extension to turn the raw article list into the desired layout.

=====Improve Unit Test Coverage=====
Work has been started on this but the number of unit tests currently in use is small. We need to add many more unit tests. Also, currently unit tests are only able to be used for class methods. We have no way, for example, to test page layouts or module insertion into templates. Part of this project could be to research automated testing solutions to test the complete HTML code sent to the browser. This would allow end-to-end automated testing.

=====Web Based Unit Test Runner=====
Write a test runner that makes it easy to run unit tests from a web browser. The existing unit test framework is based on running PHP from the command line. While this is essential for integrating testing into the build and release process, it's a barrier to using tests during development.

This project involves adapting web-based test runners provided by PHPUnit to support the "Joomla!" testing environment.

Develop and implement a method to allow organizations to update their own CiviCRM records from the Joomla! front end.

=====CiviCRM Integration: Allow Organizational Updating From Joomla! Front End=====
Civicrm [1] is a powerful constituent relationship management system designed for the not for profit/nongovernmental organizations. It currently integrates with Joomla! and the 2.1 version is native to Joomla! 1.5.

Constituent records in CiviCRM may be for individuals, households and organizations. Currently individuals can up date their records from the Joomla! front end if administrators allow it. However, many organizations have other organizations as contituents and currently there is no way for organizational (or household) records to be updated in the front end.

For this project, the student will design and implement a method allowing organizations to update their records by exposing the organizational api to the Joomla! front end and developing appropriate access control and activity tracking.

For this project the student should plan on interacting closely with both the Joomla! and CiviCRM teams.

=====Civicrm Integration: Develop Front End Extensions for CiviCRM Data=====
Develop a suite of front end Joomla! 1.5 extensions (modules, plugins and a Joomla! style MVC frontend component for CiviCRM.

[Civicrm : http://civicrm.org] is a powerful constituent relationship management system designed for the not for profit/nongovernmental organizations. It currently integrates with Joomla! 1.0.x and 1.5 in legacy mode, and and the 2.1 version will be native to Joomla! 1.5.

Thus far most functionality for civicrm in Joomla! has focused on the administrator. This project will focus on fuller development of the CiviCRM Joomla! Front end.

This development might include modules, plugins, and a MVC front end component which will allow exposure of various CiviCRM APIs.

Some of these will focus on the display of and interaction with general information, for example:
* a module showing a list of upcoming events
* a module showing progress on a fund raising thermometer
* a module displaying the most recent donations, donations at certain levels, total donations or other information
* a module containing a contribution button linked to a specific contribution page
* a plugin showing total giving in a specified time period (day, week, month, year)
* a donation reporting view with a layout that displays lists of donors in a given time period, sorted by giving level.

Some will focus on the display of user level information such as:
* a module displaying an individual's information from a given profile with the option to update.
* a module displaying an individual's summary giving information.
* a module displaying events an individual is registered for
* a plugin showing a user's information for a give field
* a plugin showing a user's total giving or giving in a given fiscal year

=====Improved Error Handling=====
Create a component that will handle standard errors (ex. 404) so that headers are sent for the error code, but the error is trapped and redirected from the error.php file back to Joomla!
where it can be handled on a normal webpage.

=====Media Manager Improvements=====
The following improvements could be made to the current Joomla! Media Manager:
* Support content expiration (image/video) that allow user to set start – end date of each content which to be lived on site
**e.g. food image can be lived on site only 3 months, due to the license issue, so we need to take out the image and replace it with other default image or leave it blank
* Support user friendly input interface which allow user to complete content input in 1 screen (Text input, Multiple images/videos upload, Tagging, Mapping related content and so on)

=====Whiteboard/Wiki Component=====
Joomla comes with a few core components, and a Whiteboard/Wiki component would be a great addition to those. It would be a basic implementation of the feature with the following possible features:

* Provide a simple interface for editing (perhaps allowing multiple users to edit at once or locking down while under edit)
* Ability to restrict user access on posting
* Organize whiteboards
* Keep revisions in archive

=====Core Extensions Semantic and SEO Updates=====
The core extensions can be modified to produce semantic markup. The tables should be replaced withmore appropriate containers for the contents. This would not replace the need for template overrides, but rather make the default output stronger to build upon. The output should also be arranged to best suit the content in the majority of situations. Perhaps also a basic system reset CSS file would need to be developed to set some of the basic layout items, also to be easily disabled.

The core output cannot be replaced completely without causing many 1.5 templates to break. Therefore it would be necessary to
either have a legacy mode for templates or to automatically detect the template type (1.5 or 1.6) in order to provide the right output.

Modules can be defined in a template to have pretty much any name they wish. While this is great for template makers, it would be good to have at least some guidelines about naming modules. Module names like user1 and user2 are essentially useless semantically, and to administrators of a site. Some templates are designed for any module to fit in any position, but in general there are at least a handful that are designed with the menu, footer, and other aspects in mind. Perhaps Joomla can create some guidelines (not requirements) related to this.

=====Templates for Joomla 1.6=====
Each version of Joomla comes with a set of templates, and they are updated with each major release. 1.6 is currently in development, and will need a new set of templates. These templates should:

* Employ semantic markup
* Provide a fresh look
* Be flexible to accommodate all kinds of content
* Come with example core overrides, perhaps for major extensions as well
* Should have a light memory print
* Comply with accessibility standards
* Validate
* Be easily modified and built upon

=====Administrator and Usability Improvements=====
There are many little improvements that would help with general usability and administration for Joomla users.

* Assigning modules in the Menu Manager
* Assigning links from Article Manager
* Copying templates
* Easily change Control Panel icons
* Improved Front Page article handling
* Improve internal mailing system and its notifications
* Make Control Panel in the menu a one click step, not hover then select
* Have the main tabs linked in case they are clicked, such as Content goes to Articles

=====Content Item Templates=====

Easy page layout template system so that editors can choose from a pre-defined range of layouts.
This could be useful when certain pages all require the Name, Date, Author name, photo in a certain area, tagline etc.
Content item templates could be defined, then saved and authors could then choose from this list, helping sites with larger article content to retain continuity throughout their areas of pages.

=====XML DTDs and XML Schemas for all XML files used in Joomla=====

XML files are used in various places throughout Joomla. Historically, the installer XML files have had DTDs against which they can be validated. However, there are a number of known issues with these DTDs and there are other XML files used in Joomla that have never had DTDs written at all. Furthermore, DTDs can only catch certain classes of errors within XML files and we need to look beyond DTDs to look at XML Schemas to catch other classes of errors.

* Review all XML files used in Joomla and list them on the documentation wiki.
* Create a collection of test cases of XML files that will fail in Joomla and which should, therefore, fail to validate in some way.
* Where DTDs already exist, review, revise and update them as necessary.
* Create DTDs for those XML files that don't currently have one.
* Create patches for the core code (target 1.6?) to ensure that valid DTDs can be written for all XML files.
* All current DTDs force some XML elements to appear in a particular order which is neither enforced nor required by Joomla. If possible, solve this problem so that designers and developers can place those elements in arbitrary order in the XML and still have the XML files validate against the DTDs.
* Create XML Schemas for all XML files used in Joomla.
* Ensure that DTDs and XML Schemas are well commented and/or thoroughly documented.
* Write comprehensive documentation covering the process of validating an XML file against both DTDs and XML Schemas. Some documentation already exists that can be used as the basis for this.
* Expand the collection of test cases to include XML files that will not fail in Joomla but which may or may not fail to validate against the DTDs or XML Schemas.
* Ensure that the test case collection is properly documented so that changes to Joomla and/or the DTDs and XML Schemas can be properly tested.
=====Alternate Component for Editing Articles=====
The idea is to have an component on admin side that allows articles to be edited based on the frontend navigation, Something similar to [http://thewebkitchen.co.uk/typo3temp/pics/a367ba3c04.jpg Typo3 admin]implementation (just 2 and 3 in the image).

Archived:Summer of Code 2009 Project Ideas

2009-03-16T21:06:18Z

Willebil: /* Advanced Poll/Survey Suite */

[[Image:Gsoc_2009_logo.png|right]]

===Welcome!===
Welcome to the Joomla! Google Summer of Code (GSoC) 2009 project ideas page. As we move forward with the 2009 version of the Joomla! GSoC, we will use this page to develop possible project ideas. Please note that anyone who is interested can participate in this process. You do not have to be a GSoC student or mentor to suggest possible project ideas. Thanks!

===Ideas===

=====Advanced Poll/Survey Suite=====

The core polls extension has been removed from Joomla! 1.6. Develop a fully featured poll/survey suite that will allow relatively simple user polls and the collection of complex anonymized survey data authenticated against either the Joomla users database or an external database.

Mentor: Wilco Jansen (subject to change)
Skills: Joomla CMS framework, MVC, PHP 5.2, MySQL
Difficulty: medium

=====Full Frontend Editing=====

Right now we only have frontend editing for articles, there are a few improvements I can propose
* Article editing is done in a modal popup
* Edit module content and params from frontend (Editing done via a modal popup?)
* Article Title - edit in place
* Create some kind of a library function which allows easy frontend editing for any value (This will need some thought)

=====Template Manager Improvements/Advanced Template Manager=====

Extend the template manager so that it providers an better environment for template creation and modification. Improvements might include:
*expanded tool bar, including copy for a complete template
*access to the media manager
*access to all template files (not just css and index.php)
*override manager
*integration of an editor with code highlighting (such as codepress)
*support for template parameter groups
*remove hard-wired references to template name from the core templates (so the new copy function will work as expected)
*"export" button on the toolbar which will create a zip package file containing the template (also fixes any errors in the templateDetails.xml file as it goes).

=====Work Flow Extension=====

Create a 1.6 Extension to flexibly manage workflow for com_content.
Ideally it should be extensible to other components, but com_content should be used as the proof of concept.
Work flow should manage the publication process, including assignment of editors or publishers to specific content items, notifications of relevant actions to specific individuals or groups, change of status to block author editing of published work.

As much as possible administrators should be able to construct their own work flows.

=====Page Versioning Extension=====

Create a 1.6 content versioning extension with the goal that this work could be integrated into the core Joomla CMS for future releases.
The Page Versioning Extension will allow the ability for frontend and backend content users to be able to save and re-publish/revert previously saved versions of content items that they have access to.

Further user permissions could be introduced in order to restrict access to this overall feature.

Features could include a visual and html code difference between the current and previously saved versions, as well as general searching data such as dates and time of previous saved entries of that content.

=====Taxonomy Extension=====

Create a 1.6 Taxonomy extension with the goal that this work could be integrated into the core Joomla CMS for future releases.
The Taxonomy Extension will allow the ability to organise content for classification, improving on the current Section and Categories classification.

Taxonomy is a vital feature of modern CMS solutions, evolving from the previous "pigeonholeing" of a content item.
Full organisational structures and multi tagging of content could be included, including powerful search functions of content under those classifications.

Taxonomy is a missing feature in Joomla!, which another open-source competitor product currently offers. We have seen a number of opportunities when Joomla! misses out on being the chosen option for a CMS due to the lacking of this feature.

=====Keywords Management Extension=====
Keywords in articles are an important part of many Joomla! sites. They are used for page rankings but also can be used with Related Articles modules and component extensions. In this capacity, they provide a way to relate articles that is much more flexible and free-form than the built-in Section / Category / Article hierarchy.

Currently in Joomla!, keywords are entered when editing each individual article. This has several disadvantages, including:
* You cannot see already existing keywords when entering in keywords for an article.
* You cannot see existing articles that are already associated with a keyword.
* It is difficult to be consistent when using keywords. For example, should it be capitalized, singular or plural ("Dog" or "Dogs"), and so on.

To deal with these issues, a back-end Keyword Management extension is proposed. This extension would allow the following capabilities:
* A management screen showing a list of all keywords currently in use. This would provide the ability to drill into any keyword and see all articles that use this keyword.
* A keyword picker screen. This would allow an author to pick keywords for an article from a list of existing keywords. This would make it easier to ensure consistency in spelling, capitalization, and usage between keywords. This screen would also allow the author to add a new keyword to the list.
* The ability to do global search and replace on keywords.
* The ability to see keywords ranked by frequency of use.
* The ability to list articles to which no keywords have been assigned.

=====User-Defined List and Blog Layout Extension=====
Currently in Joomla!, there are built-in Menu Items for list and blog layouts for Sections and Categories. However, the way a list of articles is selected is tightly bound with the way the list is displayed on the page. In theory, you should be able to have a list or blog layout that shows any selection of articles.

To provide this capability, an extension is proposed that would provide layouts similar to the current list and blog layouts. However, the extension would be designed so that the list of articles is provided by a plugin instead of being integrated into the layout. Example plugins could be provided to mimic the current Section, Article, and Front Page layouts. However, the power of this extension is that the user could add their own plugin that would provide a list of articles using any type of query. This list of articles would then feed into the built-in layouts provided by the extension to turn the raw article list into the desired layout.

=====Improve Unit Test Coverage=====
Work has been started on this but the number of unit tests currently in use is small. We need to add many more unit tests. Also, currently unit tests are only able to be used for class methods. We have no way, for example, to test page layouts or module insertion into templates. Part of this project could be to research automated testing solutions to test the complete HTML code sent to the browser. This would allow end-to-end automated testing.

=====Web Based Unit Test Runner=====
Write a test runner that makes it easy to run unit tests from a web browser. The existing unit test framework is based on running PHP from the command line. While this is essential for integrating testing into the build and release process, it's a barrier to using tests during development.

This project involves adapting web-based test runners provided by PHPUnit to support the "Joomla!" testing environment.

Develop and implement a method to allow organizations to update their own CiviCRM records from the Joomla! front end.

=====CiviCRM Integration: Allow Organizational Updating From Joomla! Front End=====
Civicrm [1] is a powerful constituent relationship management system designed for the not for profit/nongovernmental organizations. It currently integrates with Joomla! and the 2.1 version is native to Joomla! 1.5.

Constituent records in CiviCRM may be for individuals, households and organizations. Currently individuals can up date their records from the Joomla! front end if administrators allow it. However, many organizations have other organizations as contituents and currently there is no way for organizational (or household) records to be updated in the front end.

For this project, the student will design and implement a method allowing organizations to update their records by exposing the organizational api to the Joomla! front end and developing appropriate access control and activity tracking.

For this project the student should plan on interacting closely with both the Joomla! and CiviCRM teams.

=====Civicrm Integration: Develop Front End Extensions for CiviCRM Data=====
Develop a suite of front end Joomla! 1.5 extensions (modules, plugins and a Joomla! style MVC frontend component for CiviCRM.

[Civicrm : http://civicrm.org] is a powerful constituent relationship management system designed for the not for profit/nongovernmental organizations. It currently integrates with Joomla! 1.0.x and 1.5 in legacy mode, and and the 2.1 version will be native to Joomla! 1.5.

Thus far most functionality for civicrm in Joomla! has focused on the administrator. This project will focus on fuller development of the CiviCRM Joomla! Front end.

This development might include modules, plugins, and a MVC front end component which will allow exposure of various CiviCRM APIs.

Some of these will focus on the display of and interaction with general information, for example:
* a module showing a list of upcoming events
* a module showing progress on a fund raising thermometer
* a module displaying the most recent donations, donations at certain levels, total donations or other information
* a module containing a contribution button linked to a specific contribution page
* a plugin showing total giving in a specified time period (day, week, month, year)
* a donation reporting view with a layout that displays lists of donors in a given time period, sorted by giving level.

Some will focus on the display of user level information such as:
* a module displaying an individual's information from a given profile with the option to update.
* a module displaying an individual's summary giving information.
* a module displaying events an individual is registered for
* a plugin showing a user's information for a give field
* a plugin showing a user's total giving or giving in a given fiscal year

=====Improved Error Handling=====
Create a component that will handle standard errors (ex. 404) so that headers are sent for the error code, but the error is trapped and redirected from the error.php file back to Joomla!
where it can be handled on a normal webpage.

=====Media Manager Improvements=====
The following improvements could be made to the current Joomla! Media Manager:
* Support content expiration (image/video) that allow user to set start – end date of each content which to be lived on site
**e.g. food image can be lived on site only 3 months, due to the license issue, so we need to take out the image and replace it with other default image or leave it blank
* Support user friendly input interface which allow user to complete content input in 1 screen (Text input, Multiple images/videos upload, Tagging, Mapping related content and so on)

=====Whiteboard/Wiki Component=====
Joomla comes with a few core components, and a Whiteboard/Wiki component would be a great addition to those. It would be a basic implementation of the feature with the following possible features:

* Provide a simple interface for editing (perhaps allowing multiple users to edit at once or locking down while under edit)
* Ability to restrict user access on posting
* Organize whiteboards
* Keep revisions in archive

=====Core Extensions Semantic and SEO Updates=====
The core extensions can be modified to produce semantic markup. The tables should be replaced withmore appropriate containers for the contents. This would not replace the need for template overrides, but rather make the default output stronger to build upon. The output should also be arranged to best suit the content in the majority of situations. Perhaps also a basic system reset CSS file would need to be developed to set some of the basic layout items, also to be easily disabled.

The core output cannot be replaced completely without causing many 1.5 templates to break. Therefore it would be necessary to
either have a legacy mode for templates or to automatically detect the template type (1.5 or 1.6) in order to provide the right output.

Modules can be defined in a template to have pretty much any name they wish. While this is great for template makers, it would be good to have at least some guidelines about naming modules. Module names like user1 and user2 are essentially useless semantically, and to administrators of a site. Some templates are designed for any module to fit in any position, but in general there are at least a handful that are designed with the menu, footer, and other aspects in mind. Perhaps Joomla can create some guidelines (not requirements) related to this.

=====Templates for Joomla 1.6=====
Each version of Joomla comes with a set of templates, and they are updated with each major release. 1.6 is currently in development, and will need a new set of templates. These templates should:

* Employ semantic markup
* Provide a fresh look
* Be flexible to accommodate all kinds of content
* Come with example core overrides, perhaps for major extensions as well
* Should have a light memory print
* Comply with accessibility standards
* Validate
* Be easily modified and built upon

=====Administrator and Usability Improvements=====
There are many little improvements that would help with general usability and administration for Joomla users.

* Assigning modules in the Menu Manager
* Assigning links from Article Manager
* Copying templates
* Easily change Control Panel icons
* Improved Front Page article handling
* Improve internal mailing system and its notifications
* Make Control Panel in the menu a one click step, not hover then select
* Have the main tabs linked in case they are clicked, such as Content goes to Articles

=====Content Item Templates=====

Easy page layout template system so that editors can choose from a pre-defined range of layouts.
This could be useful when certain pages all require the Name, Date, Author name, photo in a certain area, tagline etc.
Content item templates could be defined, then saved and authors could then choose from this list, helping sites with larger article content to retain continuity throughout their areas of pages.

=====XML DTDs and XML Schemas for all XML files used in Joomla=====

XML files are used in various places throughout Joomla. Historically, the installer XML files have had DTDs against which they can be validated. However, there are a number of known issues with these DTDs and there are other XML files used in Joomla that have never had DTDs written at all. Furthermore, DTDs can only catch certain classes of errors within XML files and we need to look beyond DTDs to look at XML Schemas to catch other classes of errors.

* Review all XML files used in Joomla and list them on the documentation wiki.
* Create a collection of test cases of XML files that will fail in Joomla and which should, therefore, fail to validate in some way.
* Where DTDs already exist, review, revise and update them as necessary.
* Create DTDs for those XML files that don't currently have one.
* Create patches for the core code (target 1.6?) to ensure that valid DTDs can be written for all XML files.
* All current DTDs force some XML elements to appear in a particular order which is neither enforced nor required by Joomla. If possible, solve this problem so that designers and developers can place those elements in arbitrary order in the XML and still have the XML files validate against the DTDs.
* Create XML Schemas for all XML files used in Joomla.
* Ensure that DTDs and XML Schemas are well commented and/or thoroughly documented.
* Write comprehensive documentation covering the process of validating an XML file against both DTDs and XML Schemas. Some documentation already exists that can be used as the basis for this.
* Expand the collection of test cases to include XML files that will not fail in Joomla but which may or may not fail to validate against the DTDs or XML Schemas.
* Ensure that the test case collection is properly documented so that changes to Joomla and/or the DTDs and XML Schemas can be properly tested.
=====Alternate Component for Editing Articles=====
The idea is to have an component on admin side that allows articles to be edited based on the frontend navigation, Something similar to [http://thewebkitchen.co.uk/typo3temp/pics/a367ba3c04.jpg Typo3 admin]implementation (just 2 and 3 in the image).

J1.5:Plugin/Events/User

2009-01-11T14:16:33Z

Willebil:

[[Category:Development]]
[[Category:Plugins]]
====5.3 User Events for Plugin System====

===5.3.1 Overview===
In a standard installation of Joomla! 1.5 we have several predefined events which, when triggered, call functions in the associated plugins. For more information on plugins,
look [[plugins:create_plugin|here]].

The user events are divided into two parts. First we have the events used while
authentication of a user takes place:
*onLoginUser
*onLogoutUser
*onAuthenticate
*onAuthenticateFailure

Second we have the events triggered during user management:
*onBeforeStoreUser
*onAfterStoreUser
*onBeforeDeleteUser
*onAfterDeleteUser

===5.3.2 onLoginUser===
==5.3.2.1 Description==
This event is triggered after the user is authenticated against the Joomla! user-base.
If one plugin returns false, the entire authentication process fails.
==5.3.2.2 Parameters==
Two parameters: credentials, and remember.\\
Credentials is an array with this structure:\\
['username']\\
['password']\\
Remember is a boolean, set to true if the login needs to be remembered by the application.
==5.3.2.3 Return Value==
Boolean
==5.3.2.4 Used in files==
*libraries/joomla/application/application.php
*plugins/user/joomla.php
==5.3.2.5 Examples==
*plugins/user/example.php

===5.3.3 onLogoutUser===
==5.3.3.1 Description==
This event is triggered before the user is logged out of the system. If one plugin
returns false, the global logout fails.
==5.3.3.2 Parameters==
Array of credentials. Structure:\\
['username']\\
['id']\\
==5.3.3.3 Return Value==
Boolean
==5.3.3.4 Used in files==
*libraries/joomla/application/application.php
*plugins/user/joomla.php
==5.3.3.5 Examples==
*plugins/user/example.php

===5.3.4 onAuthenticate===
==5.3.4.1 Description==
This event is triggered to verify that a set of login credentials is valid.
==5.3.4.2 Parameters==
Array of credentials. Structure:\\
['username']\\
['password']\\
Alternative authentication mechanisms can supply additional credentials.

==5.3.4.3 Return Value==
An array of [[references:joomla.framework:user:jauthenticateresponse|JAuthenticateResponse]] objects detailing the results of each called plugin, including success or failure.
==5.3.4.4 Used in files==
*libraries/joomla/application/user/authentication.php
*plugins/authentication/gmail.php
*plugins/authentication/joomla.php
*plugins/authentication/ldap.php
==5.3.4.5 Examples==
*plugins/authentication/example.php

===5.3.5 onLoginFailure===
==5.3.5.1 Description==
This event is triggered whenever a user authentication request is failed by any plugin.
==5.3.5.2 Parameters==
Two parameters. The credentials array for the user (see onAuthenticate), and the
[[references:joomla.framework:user:jauthenticateresponse|JAuthenticateResponse]] that caused the failure.
==5.3.5.3 Return Value==
Unknown. The return value appears to be ignored in any case.
==5.3.5.4 Used in files==
*libraries/joomla/application/user/authentication.php

===5.3.6 onBeforeStoreUser===
==5.3.6.1 Description==
This event is triggered before a new user is stored in the database.
==5.3.6.2 Parameters==
Two parameters:
*An associative array of the columns in the user table.
*A unique identifier for this user.
==5.3.6.3 Return Value==
None
==5.3.6.4 Used in files==
*libraries/joomla/user/user.php
==5.3.6.5 Examples==
*plugins/user/example.php
===5.3.7 onAfterStoreUser===
==5.3.7.1 Description==
This event is triggered after an update of a user record, or when a new user has been stored in the database.
==5.3.7.2 Parameters==
Two parameters:
*An associative array of the columns in the user table.
*Boolean to identify if this is a new user (insert) or an existing one (update)
*Boolean to identify if the store was successful
*Error message if store failed
==5.3.7.3 Return Value==
None
==5.3.7.4 Used in files==
*libraries/joomla/user/user.php
==5.3.7.5 Examples==
*plugins/user/example.php

===5.3.8 onBeforeDeleteUser===
==5.3.8.1 Description==
The event is triggered when a user is about to be deleted from the system.
==5.3.8.2 Parameters==
An associative array containing user information. Structure:\\
['id']\\
==5.3.8.3 Return Value==
None.
==5.3.8.4 Used in files==
*libraries/joomla/user/user.php
*plugins/user/joomla.php
==5.3.8.5 Examples==
*plugins/user/example.php

===5.3.9 onAfterDeleteUser===
==5.3.9.1 Description==
The event is triggered after a user has been deleted from the system.
==5.3.9.2 Parameters==
Three parameters: user information, delete result, and error result.
User information is an associative array. Structure:\\
['id']\\
Delete result is boolean true if the delete succeeded or an error message on failure.\\
Error result is a [[references:joomla.framework:utilities:jerror|JError]] object detailing the error, if any.
==5.3.9.3 Return Value==
None.
==5.3.9.4 Used in files==
*libraries/joomla/user/user.php
*plugins/user/joomla.php
==5.3.9.5 Examples==
*plugins/user/example.php

Organizational structure

2008-09-22T02:32:19Z

Willebil:

Joomla! development is organized in two teams; the development team and the Joomla! bug squad. Overall development is coordinated by the development coordinators. The development coordinators manage the overall aspects of the Joomla! development in it's widest sense.

== Development team ==

The development team is a group of developers that are responsible for the development of new features. There is currently no specific devision in roles and responsibilities, there are only developers.

== Bug Squad ==

As with all organisational sections within the project we strive to have as little as possible structure within this team. Becomming a member is pretty simple (just send a mail to the team coordinators and you're in), and the team has the most members within development related sub-teams. To organize the day to day operation we have defined the following roles:

* '''Joomla! bug Squad team coordinator'''; these roles manage the day by day operation within the bug squad and provide help with existing and new members.
* '''Bug Squad Co Maintainers'''; the co-maintainers are responsible for comitting patches that have moved to "ready-to-commit" status. Before they commit the code changes they do a final code validation (standards, quality, docbook mark-ups etc.).

[[Category:Development]]

Organizational structure

2008-09-22T02:25:21Z

Willebil:

Development Team

2008-09-19T23:48:10Z

Willebil: /* Positions, responsibilities and roles */

[[Image:workgroups_development.jpg|right]]
The collaboration within the Joomla! Open-source project is based upon the trust and fun. We want to put as little hierarchy into this team as possible, and, if we actually do Joomla! (all together) this section will be superfluous. But for every team that exists of more than one person, a structure needs to be in place.

This team sometimes also is referred to as core-committers. Some of the members are also core-team members, but the term "core-comitter" refers to team members who have full commit access to the Joomla! code base.

== Positions, responsibilities and roles ==

The '''Development Work group Coordinator''' has the overall lead on Joomla! development and has the following responsibilities:
# Will take care of properly planning the progress through the development stages for the various working groups. Proper planning includes: architectural design, coding stages, testing stages, release stages etc.
# Will take care of basic communication to all surrounding work groups. Arrange structure for testing and documentation, linking development effort to the other roles of the work groups.
# Will take care of standards and guidelines that need to be followed within the development workgroups (not writing them myself, but just arrange that these are created).
# Will write a road map proposal for the Core team, and in later stages propose it to the community. Process any feedback, but guarding the overall goals of the project.
# Will take care of periodical communication to the community: doing a blog, but also taking the road to the PR work group.
#Will define some work group membership guidelines, and try to implement them into the work groups. Non active, or non functional work group members can be removed, for this see the "Status" section.
# Will invite new members to the work groups (can also be done by the lead developers), and remove them when this is needed.
# Will determine which lead developers are in the team.
# Guards the progression on the pre-defined project goals.

A '''Development working group coordinator''' his/her main responsibility is to organize everything around Joomla! development. This is actually one of the very few official positions. The Development working group coordinators set direction, organize the team and do general overview for Joomla! development.

A '''Developer''' actually performs programming, testing and documentation tasks. A Developer can potentially assign himself to a wide variety of tasks but their individual abilities will likely determine which areas he/she will work on.
# Does development of the Joomla! framework code.
# Does testing.
# Follows [[Development guidelines]].
# Works on technical documentation of all aspects of the Joomla! framework.

== Team membership ==

The development work group aims at the development of a cutting edge, state of the art Web Content Management application framework. This workgroup is the driving force behind new versions, and building it. Along with the other working groups we try to realize this ambition.

We always seek for new talent. We are very sharp on who we want because the results of this workgroup determines what the quality of Joomla! is. Most of the times we get in touch with you when we see some interesting work around, but if you think you are the talent we seek you also can contact us. If you want to grab our attention, start [Sending in patches] so we actually can see what you do, and how you do. Before you do please bear the following in mind:

# You need to be available at least 8 hours per week.
# Education (or still being a student) in informatics with knowledge of modern development methods and techniques.
# (Outstanding) knowledge of programming techniques like patterns and object orientation.
# Experience with PHP, (My)SQL and webservices.
# Knowledge with the Joomla! application and CMS framework.

== Membership status ==

Within the development work group, we recognize three membership statuses:
# '''Active''' - actively contributing on a week-by-week or day-by-day basis (or even more).
# '''On-leave''' - temporarily away from duties because of vacations, work commitments or other valid reasons but still in touch with regular communication channels.
# '''Inactive''' - Away from duties and responsibilities for a period of time and not in touch with regular communication channels.

A development team group member is considered active if they are contributing to a communication channel at least once a week and fulfilling a reasonable time commitment to the project. To prevent stagnant teams and blocking out new talent from getting into the development work group some limitations apply to the possible statuses described above:
# A development work group member may be on-leave for up to 3 months. After this period the team member will automatically be transferred to inactive status.
# A development work group member may be inactive for up to 6 months. After this period the team member will automatically be removed from the work group. When transferred from on-leave status to inactive, the total period a team member can be absent is 6 months.

In all cases it is important that the developers informs the work group coordinator or lead developer of his team that he/she is (planning to go) on leave or being inactive.

== Conflict resolution ==

It would be naive to assume that a group of people can work together in perfect harmony. There are going to be times when someone feels they have been wronged. In these times the following procedure should apply:

# Talk privately to the person concerned.
# If you still believe grievances exists, then bring in one or two other people to help mediate.
# If this fails then take the issue to the workgroup coordinator.
# If this fails take the issue with the workgroup coordinator to the Joomla! project leader.
# If this fails take the issue to the whole Core team for final determination.

Team members are encouraged to self-mediate all disputes. In all situations, treat 'wounds' appropriately. A prick on the finger just needs a tissue for a couple of seconds. Some grazes and cut just need a Band-Aid to help heal well but will probably heal anyway if left untouched. More serious lacerations need immediate intervention for survival. If a wound is left to attract an infection then the obvious threat of gangrene is present.

== Resignation ==

Everyone in Joomla! has their season and there are going to be times when someone needs to move on for various reasons. You should always feel comfortable to leave or have a holiday from the project, just inform the work group coordinator or better yet, let the whole team know by posting your absence to the mailing list (joomla-devel@googlegroups.com). If you are going to be unavailable for a period of time, please be considerate and:

* Give reasonable notice in proportion to your role. Work group coordinator and Lead Developers should give around four weeks notice and other members at least one.
* Make sure that your team knows what they have to take over when you leave. Do not put the Team in a position where they have to play detective to find out what you did, where things are, and what their status is, etc.

== Removing members ==

A development team member will be removed:
* When he/she violates the Code of Conduct.
* When the work team member is inactive for more then 6 months (see the membership status section above).

[[Category:Development]]

Bug and Issue Tracker Priority

2008-09-05T21:04:37Z

Willebil:

You've been trying to solve it for hours, no one on the forums has been able to help, the issue seems not to be covered in the documentation, and you are probably on a deadline too. Time to submit it to the tracker. After all that effort, it sure seems like a critical issue. So, you select a priority level of high.

Then what happens? Someone from JBS goes and changes it to medium. Why did they do that? Does that mean your issue isn't important and it won't be dealt with? Are they just mean and uncaring?

Of course not. It just turns out the the development work group has pretty strict definitions of artifact priority levels.

The artifacts are prioritized according to the following characteristics:

#'''High/Critical''': The trunk is not working at all. Significant parts of the source are broken preventing key operations. Examples would be login, installation, extenstion installers, javascript errors that prevent you from moving a save or similar action, etc. Also includes the generation of Fatal PHP errors for .
# '''Medium High/Major''': Parts of the source are obstructing operation in a serious way or causing a major loss in advertised function.
# '''Medium/Normal''': Issues that are hindering advertised behaviour but the application is still workable. Examples would include parameters not working as advertised, language files not loading as expected, etc.
# '''Low/Minor''': Minor loss of function and generally annoying behaviour. May include less common platform or browser specific problems that while they may be technically major in those environments, they represent a minority. Also include missing translation strings.
# '''Very Low/Trivial''': Cosmetic problems, mis-spelled words, graphically mis-aligned object, less common issues with parameters, etc.

What does this mean?

First of all, if it is not within the first few days of a release and it doesn't involve a security issue, unless you are using subversion or a nightly build you will most likely never see a prioirty 1 (high) issue or need to report one. That's because if there are any open priority 1 issues in the codebase, there will not be a release. The same thing actually goes for prioirty 2 (medium high). A real prioirty 1 issue in an actual release is something that would trigger a new release. A priority 1 or priority 2 issue in the 1.5 branch of codebase would keep a scheduled release from taking place. This is serious, because each release contains many bug fixes and improvements, so not releasing keeps most of the community from getting those. Forcing an unscheduled release is serious too, because it means that work on other things stops while all efforts are put into getting the release ready.

The one exception would be if you discover a major security issue, but the tracker is not usually the place to report most security issues.

This doesn't mean that there are never prioirty 1 or 2 issues. A prioirty 1 issue may develop (http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=11225) in the current Joomla! source code that is in Subversion. Subversion is where all of the changes to the source code are made.

So, before you decide to mark an issue as priority 1 or priority 2, think about whether it would really warrant all of these things.

Most issues are priority 3, medium. However, some issues are priority 4 or 5 If you mark your issue as prioirty 4 or 5 does that mean it will not get fixed? Not at all. If it's an easy to fix issue, especially if you provide a patch or proposed code, it may get taken care of right away. Some people in JBS informally specialize in language issues or CSS or other topics that are often in prioirty 4 or 5 issues. So don't feel like you need to mark something prioirty 3 for it to get attention.

Development Working Group

2008-08-05T21:59:03Z

Willebil: /* Coding standards */

{{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 [[Category:Development]] 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]

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

Full description of coding standards
Usage of Docbook markups
Developer guidelines
Error message conventions
Exception handling

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== 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]]

[[Category:Development]]

Development Working Group

2008-08-05T21:58:32Z

Willebil: /* Writing secure Joomla! code */

{{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 [[Category:Development]] 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]

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

Full description of coding standards
Usage of Docbook markups

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== 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]]

[[Category:Development]]

User:Willebil

2008-08-05T21:56:10Z

Willebil:

Just a lonesome cowboy doing some things within the Joomla! project ;-)

Development Working Group

2008-08-05T21:34:51Z

Willebil: /* Communications */

{{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 [[Category:Development]] 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]

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

Full description of coding standards
Usage of Docbook markups

== Writing secure Joomla! code ==

Preventing SQL injections (see http://developer.joomla.org/tutorials/181-preventing-sql-injections.html)

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== 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]]

[[Category:Development]]

Development Working Group

2008-08-05T21:34:28Z

Willebil: /* Communications */

{{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 [[Category:Development]] 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]]

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

Full description of coding standards
Usage of Docbook markups

== Writing secure Joomla! code ==

Preventing SQL injections (see http://developer.joomla.org/tutorials/181-preventing-sql-injections.html)

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== 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]]

[[Category:Development]]

Development Working Group

2008-08-05T21:29:15Z

Willebil: /* Social and Political Infrastructure */

{{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 [[Category:Development]] 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 ==

Development blog
Summer of Code blog
Development forum
Development meetings
Joomla! events (like Joomla! days)
Local user groups
Pizza Bugs and Fun

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

Full description of coding standards
Usage of Docbook markups

== Writing secure Joomla! code ==

Preventing SQL injections (see http://developer.joomla.org/tutorials/181-preventing-sql-injections.html)

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== 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]]

[[Category:Development]]

Development Working Group

2008-08-05T21:25:15Z

Willebil: /* Social and Political Infrastructure */

{{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 [[Category:Development]] 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 [[Consensus Based Democracy http://producingoss.com/en/consensus-democracy.html]] model.

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

== Communications ==

Development blog
Summer of Code blog
Development forum
Development meetings
Joomla! events (like Joomla! days)
Local user groups
Pizza Bugs and Fun

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

Full description of coding standards
Usage of Docbook markups

== Writing secure Joomla! code ==

Preventing SQL injections (see http://developer.joomla.org/tutorials/181-preventing-sql-injections.html)

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== 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]]

[[Category:Development]]

Development Working Group

2008-08-05T21:23:45Z

Willebil: /* Social and Political Infrastructure */

{{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 [[Category:Development]] 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 :wink://[[Image:Wink.gif]] 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 [[Consensus Based Democracy http://producingoss.com/en/consensus-democracy.html]] model.

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

== Communications ==

Development blog
Summer of Code blog
Development forum
Development meetings
Joomla! events (like Joomla! days)
Local user groups
Pizza Bugs and Fun

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

Full description of coding standards
Usage of Docbook markups

== Writing secure Joomla! code ==

Preventing SQL injections (see http://developer.joomla.org/tutorials/181-preventing-sql-injections.html)

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== 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]]

[[Category:Development]]

Organizational structure

2008-08-05T21:18:19Z

Willebil: New page: {{incomplete}} Category:Development

{{incomplete}}

[[Category:Development]]

Development Working Group

2008-08-05T21:16:19Z

Willebil: /* Social and Political Infrastructure */

{{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 [[Category:Development]] 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 [[Consensus Based Democracy http://producingoss.com/en/consensus-democracy.html]] model.

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

== Communications ==

Development blog
Summer of Code blog
Development forum
Development meetings
Joomla! events (like Joomla! days)
Local user groups
Pizza Bugs and Fun

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

Full description of coding standards
Usage of Docbook markups

== Writing secure Joomla! code ==

Preventing SQL injections (see http://developer.joomla.org/tutorials/181-preventing-sql-injections.html)

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== 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]]

[[Category:Development]]

Development Working Group

2008-08-05T21:10:22Z

Willebil: /* Technical infrastructure */

{{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 [[Category:Development]] 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 ==

Organizational structure
Code of conduct

== Communications ==

Development blog
Summer of Code blog
Development forum
Development meetings
Joomla! events (like Joomla! days)
Local user groups
Pizza Bugs and Fun

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

Full description of coding standards
Usage of Docbook markups

== Writing secure Joomla! code ==

Preventing SQL injections (see http://developer.joomla.org/tutorials/181-preventing-sql-injections.html)

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== 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]]

[[Category:Development]]

Joomlacode

2008-08-05T21:06:33Z

Willebil: New page: {{incomplete}} Category:Development

{{incomplete}}

[[Category:Development]]

Development Working Group

2008-08-05T21:05:41Z

Willebil: /* Technical infrastructure */

{{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 [[Category:Development]] 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 ==

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

== Social and Political Infrastructure ==

Organizational structure
Code of conduct

== Communications ==

Development blog
Summer of Code blog
Development forum
Development meetings
Joomla! events (like Joomla! days)
Local user groups
Pizza Bugs and Fun

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

Full description of coding standards
Usage of Docbook markups

== Writing secure Joomla! code ==

Preventing SQL injections (see http://developer.joomla.org/tutorials/181-preventing-sql-injections.html)

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== 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]]

[[Category:Development]]

Bug tracker

2008-08-05T21:05:22Z

Willebil: New page: {{incomplete}} Category:Development

{{incomplete}}

[[Category:Development]]

Mailing lists

2008-08-05T21:05:02Z

Willebil: New page: {{incomplete}} Category:Development

{{incomplete}}

[[Category:Development]]

Development Working Group

2008-08-05T21:04:44Z

Willebil: /* Technical infrastructure */

{{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 [[Category:Development]] 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 ==

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

== Social and Political Infrastructure ==

Organizational structure
Code of conduct

== Communications ==

Development blog
Summer of Code blog
Development forum
Development meetings
Joomla! events (like Joomla! days)
Local user groups
Pizza Bugs and Fun

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

Full description of coding standards
Usage of Docbook markups

== Writing secure Joomla! code ==

Preventing SQL injections (see http://developer.joomla.org/tutorials/181-preventing-sql-injections.html)

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== 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]]

[[Category:Development]]

Development Working Group

2008-08-05T21:03:19Z

Willebil:

{{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 [[Category:Development]] 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 ==

Mailing lists
Version control
Bug tracker
IRC/Real-Time Chat
Wikis
Web sites

== Social and Political Infrastructure ==

Organizational structure
Code of conduct

== Communications ==

Development blog
Summer of Code blog
Development forum
Development meetings
Joomla! events (like Joomla! days)
Local user groups
Pizza Bugs and Fun

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

Full description of coding standards
Usage of Docbook markups

== Writing secure Joomla! code ==

Preventing SQL injections (see http://developer.joomla.org/tutorials/181-preventing-sql-injections.html)

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== 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]]

[[Category:Development]]

Development Working Group

2008-08-05T21:02:49Z

Willebil: /* Getting started */

{{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 [[Category::Development]] 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 ==

Mailing lists
Version control
Bug tracker
IRC/Real-Time Chat
Wikis
Web sites

== Social and Political Infrastructure ==

Organizational structure
Code of conduct

== Communications ==

Development blog
Summer of Code blog
Development forum
Development meetings
Joomla! events (like Joomla! days)
Local user groups
Pizza Bugs and Fun

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

Full description of coding standards
Usage of Docbook markups

== Writing secure Joomla! code ==

Preventing SQL injections (see http://developer.joomla.org/tutorials/181-preventing-sql-injections.html)

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== 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]]

[[Category:Development]]

Development Working Group

2008-08-05T21:02:13Z

Willebil: /* Getting started */

{{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 [[Category::Development]] documentation category to find your information. If there is information missing, feel free to add this within this wiki.

First look around
Guide to this wiki section

== Technical infrastructure ==

Mailing lists
Version control
Bug tracker
IRC/Real-Time Chat
Wikis
Web sites

== Social and Political Infrastructure ==

Organizational structure
Code of conduct

== Communications ==

Development blog
Summer of Code blog
Development forum
Development meetings
Joomla! events (like Joomla! days)
Local user groups
Pizza Bugs and Fun

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

Full description of coding standards
Usage of Docbook markups

== Writing secure Joomla! code ==

Preventing SQL injections (see http://developer.joomla.org/tutorials/181-preventing-sql-injections.html)

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== 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]]

[[Category:Development]]

Development Working Group

2008-08-05T20:48:32Z

Willebil:

Development Working Group

2008-08-05T20:47:56Z

Willebil:

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

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

== Introduction ==

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

First look around
Guide to this wiki section

== Technical infrastructure ==

Mailing lists
Version control
Bug tracker
IRC/Real-Time Chat
Wikis
Web sites

== Social and Political Infrastructure ==

Organizational structure
Code of conduct

== Communications ==

Development blog
Summer of Code blog
Development forum
Development meetings
Joomla! events (like Joomla! days)
Local user groups
Pizza Bugs and Fun

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

Full description of coding standards
Usage of Docbook markups

== Writing secure Joomla! code ==

Preventing SQL injections (see http://developer.joomla.org/tutorials/181-preventing-sql-injections.html)

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== 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]]

[[Category:Development]]

Development Working Group

2008-08-05T20:46:23Z

Willebil:

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

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

== Introduction ==

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

First look around
Guide to this wiki section

== Technical infrastructure ==

Mailing lists
Version control
Bug tracker
IRC/Real-Time Chat
Wikis
Web sites

== Social and Political Infrastructure ==

Organizational structure
Code of conduct

== Communications ==

Development blog
Summer of Code blog
Development forum
Development meetings
Joomla! events (like Joomla! days)
Local user groups

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

Full desciption of coding standards
Usage of Docbook markups

== Writing secure Joomla! code ==

Preventing SQL injections (see http://developer.joomla.org/tutorials/181-preventing-sql-injections.html)

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== 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]]

[[Category:Development]]

Development Working Group

2008-08-05T20:25:58Z

Willebil: /* Unit testing within Joomla! */

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

'''''"..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.

== Joomla! development goals ==

== How to contribute to Joomla! development ==

== Coding standards ==

== Writing secure Joomla! code ==

== Joomla! maintenance ==

== 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]]

[[Category:Development]]

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

== Debugging your Joomla! code ==

== Subversion (SVN) ==

== 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]]

[[Category:Development]]

Development Working Group

2008-08-05T20:00:46Z

Willebil:

Development Working Group

2008-08-05T19:59:00Z

Willebil:

Development Working Group

2008-08-05T19:54:28Z

Willebil:

Development Working Group

2008-08-05T19:54:17Z

Willebil:

Development Working Group

2008-08-05T19:52:02Z

Willebil:

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

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.

There are several ways to contribute to Joomla:

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

=== 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 ===
* [[Unit Testing]] within the Joomla! project
* [[The use of Subversion]]

[[Category:Development]]

Development Working Group

2008-08-05T19:39:55Z

Willebil:

Pizza Bugs and Fun 2/Contributors List

2008-06-28T16:04:04Z

Willebil: /* Contributors to the second PBF */

<noinclude>If you made a contribution to the documentation held on this site, please feel free to add your name below. Please consider adding your real name in addition to your nickname. You may, optionally, include a link to your website.</noinclude>

== Contributors to the second PBF ==

* Chris Davenport ([[Special:Contributions/Chris_Davenport|contributions]])
* Kevin Devine ([[Special:Contributions/Kevin_Devine|contributions]])
* Anthony Ferrara ([[Special:Contributions/ircmaxell|contributions]])
* Jerry Hilburn ([[Special:Contributions/Jerry_Hilburn|contributions]])
* Louis Landry ([[Special:Contributions/Louis_Landry|contributions]])
* Wilco Jansen ([[Special:Contributions/willebil|contributions]])
* Jennifer Marriott ([[Special:Contributions/MMMedia|contributions]])
* Rob Schley ([[Special:Contributions/Rob_Schley|contributions]])
* Amy Stephen ([[Special:Contributions/AmyStephen|contributions]])
* Nereyda Valentin-Macias ([[Special:Contributions/Neriv|contributions]])
* Elin Waring ([[Special:Contributions/Elin|contributions]])
* Michael Casha ([[Special:Contributions/MiCCAS|contributions]])
* Marcelo Eden ([[Special:Contributions/3dentech|contributions]])
* Matt Thomas ([[Special:Contributions/betweenbrain|contributions]])
* Ross Crawford ([[Special:Contributions/RoscoHead|contributions]])
* Mickael Maison ([[Special:Contributions/Mmaison|contributions]])
* Ian MacLennan ([[Special:Contributions/ian|contributions]])
* Jaap Woltjes ([[Special:Contributions/japie1001|contributions]])
* Alan Langford ([[Special:Contributions/Instance|contributions]])
* Michael Hamanaka ([[Special:Contributions/hamanaka|contributions]])
* Joe LeBlanc ([[Special:Contributions/jlleblanc|contributions]])
* Shannon Quinn ([[Special:Contributions/magsol|contributions]])
* Michelle Bisson ([[Special:Contributions/Michelle Bisson|contributions]])
* Airton Torres ([[Special:Contributions/airton|contributions]])
* Toni Marie Swats ([[Special:Contributions/toni.marie|contributions]])
* Jon Giles ([[Special:Contributions/Jonflgiles|contributions]])
* Matheus Mendes ([[Special:Contributions/bigodines|contributions]])

Pizza Bugs and Fun 2

2008-06-26T18:58:14Z

Willebil:

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

;28 to 29 June 2008 <countdown time="06/28/2008 0:00 AM UTC-0000"><font color="red"> *** Countdown: '''<D>''' days, '''<H>''' hours, '''<M>''' minutes and '''<S>''' seconds. *** </font></countdown>

We eagerly announce the second Joomla! Pizza Bug and Fun event scheduled for the weekends of '''June 21 and 22''' and '''June 28 and 29'''. It's hard to believe that six months have passed since the first Joomla! Pizza Bug and Fun event. The first PBF helped finalize Joomla! 1.5 and, if all goes as planned, this second event will help prepare Joomla! 1.5.4 for release early in July.

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

== Goals ==

* '''Bugs''' : For our first PBF event, we targeted priority 1 and 2 bugs and tested the entire application. Since it's release, Joomla! 1.5 has been very stable and there are no serious bugs to fix. But, there are a number of medium priority items that require patches and testing. If we are able to empty the tracker during the weekend, it would be an important accomplishment for the community.

* '''Documentation''' : since the last [[Doc Camp 1|Doc Camp]] a lot of documentation has been written, but we need more of it. If you want to help out writing documentation, you're also more than welcome.

* '''Unit testing''' : we have started writing unit tests for Joomla! This is documented in the wiki, see [[Unit Testing]] for details. This is a very important part to improve the overall quality of Joomla! and increase development speed. If you have experience in this area, we challenge you to come help us.

== FAQ ==
Below you will find as much as possible information we can share on how this events is organized. If you don't find what you are looking for, you can check out the [[PBF FAQ]].

== Organization, logistics and communications ==

Managing this event will be a challenge. The team of [[Pizza couriers]] is working on the organization of this event, taking care of all logistics, infrastructure and communications.

'''Read this blog for information on how to get started when you arrive for the Pizza, Bugs and Fun event:'''
see http://developer.joomla.org/home/26-coordinator-blog/147-the-best-ingredients-for-a-nice-pizza.html

== 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 have any questions regarding this, feel free to contact Wilco Jansen (wilco.jansen@joomla.org).

=== Europe ===
Hotel La Meridiana
Viale Italia 198 - Marina Romea 48010 Ravenna (Ra) Italy
28 June 2008
Additional information [http://www.joomladay.it/ www.joomladay.it]
To register post [http://forum.joomla.it/index.php/topic,44604.0.html here]
[http://www.joomladay.it/component/option,com_contact/task,view/contact_id,1/Itemid,2 Contacts]

JUG Catalan Countries
June 21. Can Domenge Centre Tecnologic. Soldat Arrom quart, 1. Palma de Mallorca Spain
[http://www.joomla.cat JUG Catalan Countries Website]

There will also be a location in the Netherlands (Amsterdam, Rotterdam or Eindhoven, most likely it will be Rotterdam)
If you are interested please send a mail to wilco.jansen@joomla.org

=== North America ===

Webimagery, LLC
843 Carondelet St. Suite 6
New Orleans, LA 70130
USA
[http://jpbf2nola1.eventbrite.com June 21 Registration]
[http://jpbf2nola2.eventbrite.com June 22 Registration]

PICnet, Inc. (DC)
1341 G St, NW, Suite 1100
Washington DC, 20005
[http://www.joomladayusa.org/index.php?option=com_events&type=event&task=details&id=6&Itemid=11 Registration Page]

New York City JUG
WinterGarden
World Financial Center (By the Gap)
[http://www.joomlanyc.org Joomla NYC Website]

Vancouver, BC, Canada
822 Homer (at Robson)
Across from where the JoomlaDay event was held.
Call Mike Hamanaka or Amir Sharifnejad at +1-604-626-9225 and we will buzz you in.
[website to be announced]

=== South America ===
No venue registered

=== Asia/Pacific ===

Spike Systems Pty Ltd
Level 6, 99 York Street
Sydney.
Map here: http://tinyurl.com/4gwatl
URL with additional information will follow soon (including registration option).

=== Africa ===
No venue registered

===Cyberspace===
====Internet Relay Chat (IRC)====
Freenode channel [irc://irc.freenode.net/joomlapbf #joomlapbf] from 21 to 22 June 2008, all times, all timezones.

If you don't have an IRC client installed, use this link: [http://www.joomlanyc.org/index.php?option=com_wrapper&Itemid=23 #joomlapbf]. This is a web-based IRC client.

This channel is available now and throughout the event. We might set up additional channels, if we do they will be listed above.

== 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. If you are traveling to one of the physical locations you are advised to ensure that you have registered on this wiki and have a valid login before you travel. You don't need access to your email account after registration.

=== 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 ===
Pizza can be ordered at a shop near by :-)

Please check the [http://docs.joomla.org/Pizza_Bugs_and_Fun_2#Organization.2C_logistics_and_communications Organization, logistics and communications section] for detail 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 [[PBF Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British/Australian English.
{{:PBF_Contributors_List}}
[[Category: Development]]

Pizza Bugs and Fun 2

2008-06-21T23:32:54Z

Willebil: /* Asia/Pacific */

[[Image:pbf.png|right]]
{{RightTOC}}
We eagerly announce the second Joomla! Pizza Bug and Fun event scheduled for the weekends of '''June 21 and 22''' and '''June 28 and 29'''. It's hard to believe that six months have passed since the first Joomla! Pizza Bug and Fun event. The first PBF helped finalize Joomla! 1.5 and, if all goes as planned, this second event will help prepare Joomla! 1.5.4 for release early in July.

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

== Goals ==

* '''Bugs''' : For our first PBF event, we targeted priority 1 and 2 bugs and tested the entire application. Since it's release, Joomla! 1.5 has been very stable and there are no serious bugs to fix. But, there are a number of medium priority items that require patches and testing. If we are able to empty the tracker during the weekend, it would be an important accomplishment for the community.

* '''Documentation''' : since the last [[Doc Camp 1|Doc Camp]] a lot of documentation has been written, but we need more of it. If you want to help out writing documentation, you're also more than welcome.

* '''Unit testing''' : we have started writing unit tests for Joomla! This is documented in the wiki, see [[Unit Testing]] for details. This is a very important part to improve the overall quality of Joomla! and increase development speed. If you have experience in this area, we challenge you to come help us.

== FAQ ==
Below you will find as much as possible information we can share on how this events is organized. If you don't find what you are looking for, you can check out the [[PBF FAQ]].

== Organization, logistics and communications ==

Managing this event will be a challenge. The team of [[Pizza couriers]] is working on the organization of this event, taking care of all logistics, infrastructure and communications.

'''Read this blog for information on how to get started when you arrive for the Pizza, Bugs and Fun event:'''
see http://developer.joomla.org/home/26-coordinator-blog/147-the-best-ingredients-for-a-nice-pizza.html

== 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 have any questions regarding this, feel free to contact Wilco Jansen (wilco.jansen@joomla.org).

=== Europe ===
Hotel La Meridiana
Viale Italia 198 - Marina Romea 48010 Ravenna (Ra) Italy
28 June 2008
Additional information [http://www.joomladay.it/ www.joomladay.it]
To register post [http://forum.joomla.it/index.php/topic,44604.0.html here]
[http://www.joomladay.it/component/option,com_contact/task,view/contact_id,1/Itemid,2 Contacts]

JUG Catalan Countries
June 21. Can Domenge Centre Tecnologic. Soldat Arrom quart, 1. Palma de Mallorca Spain
[http://www.joomla.cat JUG Catalan Countries Website]

There will also be a location in the Netherlands (Amsterdam, Rotterdam or Eindhoven, most likely it will be Rotterdam)
If you are interested please send a mail to wilco.jansen@joomla.org

=== North America ===

Webimagery, LLC
843 Carondelet St. Suite 6
New Orleans, LA 70130
USA
[http://jpbf2nola1.eventbrite.com June 21 Registration]
[http://jpbf2nola2.eventbrite.com June 22 Registration]

PICnet, Inc. (DC)
1341 G St, NW, Suite 1100
Washington DC, 20005
[http://www.joomladayusa.org/index.php?option=com_events&type=event&task=details&id=6&Itemid=11 Registration Page]

New York City JUG
WinterGarden
World Financial Center (By the Gap)
[http://www.joomlanyc.org Joomla NYC Website]

Vancouver, BC, Canada
822 Homer (at Robson)
Across from where the JoomlaDay event was held.
Call Mike Hamanaka or Amir Sharifnejad at +1-604-626-9225 and we will buzz you in.
[website to be announced]

=== South America ===
No venue registered

=== Asia/Pacific ===

Spike Systems Pty Ltd
Level 6, 99 York Street
Sydney.
Map here: http://tinyurl.com/4gwatl
URL with additional information will follow soon (including registration option).

=== Africa ===
No venue registered

===Cyberspace===
====Internet Relay Chat (IRC)====
Freenode channel [irc://irc.freenode.net/joomlapbf #joomlapbf] from 21 to 22 June 2008, all times, all timezones.

If you don't have an IRC client installed, use this link: [http://www.joomlanyc.org/index.php?option=com_wrapper&Itemid=23 #joomlapbf]. This is a web-based IRC client.

This channel is available now and throughout the event. We might set up additional channels, if we do they will be listed above.

== 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. If you are traveling to one of the physical locations you are advised to ensure that you have registered on this wiki and have a valid login before you travel. You don't need access to your email account after registration.

=== 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 ===
Pizza can be ordered at a shop near by :-)

Please check the [http://docs.joomla.org/Pizza_Bugs_and_Fun_2#Organization.2C_logistics_and_communications Organization, logistics and communications section] for detail 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 [[PBF Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British/Australian English.
{{:PBF_Contributors_List}}
[[Category: Development]]

Pizza Bugs and Fun 2

2008-06-20T23:08:01Z

Willebil: /* North America */

[[Image:pbf.png|right]]
{{RightTOC}}
We eagerly announce the second Joomla! Pizza Bug and Fun event scheduled for the weekends of '''June 21 and 22''' and '''June 28 and 29'''. It's hard to believe that six months have passed since the first Joomla! Pizza Bug and Fun event. The first PBF helped finalize Joomla! 1.5 and, if all goes as planned, this second event will help prepare Joomla! 1.5.4 for release early in July.

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

== Goals ==

* '''Bugs''' : For our first PBF event, we targeted priority 1 and 2 bugs and tested the entire application. Since it's release, Joomla! 1.5 has been very stable and there are no serious bugs to fix. But, there are a number of medium priority items that require patches and testing. If we are able to empty the tracker during the weekend, it would be an important accomplishment for the community.

* '''Documentation''' : since the last [[Doc Camp 1|Doc Camp]] a lot of documentation has been written, but we need more of it. If you want to help out writing documentation, you're also more than welcome.

* '''Unit testing''' : we have started writing unit tests for Joomla! This is documented in the wiki, see [[Unit Testing]] for details. This is a very important part to improve the overall quality of Joomla! and increase development speed. If you have experience in this area, we challenge you to come help us.

== FAQ ==
Below you will find as much as possible information we can share on how this events is organized. If you don't find what you are looking for, you can check out the [[PBF FAQ]].

== Organization, logistics and communications ==

Managing this event will be a challenge. The team of [[Pizza couriers]] is working on the organization of this event, taking care of all logistics, infrastructure and communications.

see http://developer.joomla.org/home/26-coordinator-blog/147-the-best-ingredients-for-a-nice-pizza.html

== 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 have any questions regarding this, feel free to contact Wilco Jansen (wilco.jansen@joomla.org).

=== Europe ===
Hotel La Meridiana
Viale Italia 198 - Marina Romea 48010 Ravenna (Ra) Italy
28 June 2008
Additional information [http://www.joomladay.it/ www.joomladay.it]
To register post [http://forum.joomla.it/index.php/topic,44604.0.html here]
[http://www.joomladay.it/component/option,com_contact/task,view/contact_id,1/Itemid,2 Contacts]

JUG Catalan Countries
June 21. Can Domenge Centre Tecnologic. Soldat Arrom quart, 1. Palma de Mallorca Spain
[http://www.joomla.cat JUG Catalan Countries Website]

There will also be a location in the Netherlands (Amsterdam, Rotterdam or Eindhoven, most likely it will be Rotterdam)
If you are interested please send a mail to wilco.jansen@joomla.org

=== North America ===

Webimagery, LLC
843 Carondelet St. Suite 6
New Orleans, LA 70130
USA
[http://jpbf2nola1.eventbrite.com June 21 Registration]
[http://jpbf2nola2.eventbrite.com June 22 Registration]

PICnet, Inc. (DC)
1341 G St, NW, Suite 1100
Washington DC, 20005
[http://www.joomladayusa.org/index.php?option=com_events&type=event&task=details&id=6&Itemid=11 Registration Page]

New York City JUG
Address to be verified shortly
[http://www.joomlanyc.org Joomla NYC Website]

Vancouver, BC, Canada
822 Homer (at Robson)
Across from where the JoomlaDay event was held.
Call Mike Hamanaka or Amir Sharifnejad at +1-604-626-9225 and we will buzz you in.
[website to be announced]

=== South America ===
No venue registered

=== Asia/Pacific ===

Spike Systems Pty Ltd
Level 6, 99 York Street
Sydney.
Map here: http://tinyurl.com/4gwatl
URL with additional information will follow soon (including registration option).

------
Please enter your location in Asia here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

=== Africa ===
No venue registered

===Cyberspace===
====Internet Relay Chat (IRC)====
Freenode channel [irc://irc.freenode.net/joomlapbf #joomlapbf] from 21 to 22 June 2008, all times, all timezones.

This channel is available now and throughout the event. We might set up additional channels, if we do they will be listed above.

== 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. If you are traveling to one of the physical locations you are advised to ensure that you have registered on this wiki and have a valid login before you travel. You don't need access to your email account after registration.

=== 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 ===
Pizza can be ordered at a shop near by :-)

Please check the [http://docs.joomla.org/Pizza_Bugs_and_Fun_2#Organization.2C_logistics_and_communications Organization, logistics and communications section] for detail 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 [[PBF Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British/Australian English.
{{:PBF_Contributors_List}}
[[Category: Development]]

Pizza Bugs and Fun 2

2008-06-20T23:06:59Z

Willebil: /* Organization, logistics and communications */

[[Image:pbf.png|right]]
{{RightTOC}}
We eagerly announce the second Joomla! Pizza Bug and Fun event scheduled for the weekends of '''June 21 and 22''' and '''June 28 and 29'''. It's hard to believe that six months have passed since the first Joomla! Pizza Bug and Fun event. The first PBF helped finalize Joomla! 1.5 and, if all goes as planned, this second event will help prepare Joomla! 1.5.4 for release early in July.

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

== Goals ==

* '''Bugs''' : For our first PBF event, we targeted priority 1 and 2 bugs and tested the entire application. Since it's release, Joomla! 1.5 has been very stable and there are no serious bugs to fix. But, there are a number of medium priority items that require patches and testing. If we are able to empty the tracker during the weekend, it would be an important accomplishment for the community.

* '''Documentation''' : since the last [[Doc Camp 1|Doc Camp]] a lot of documentation has been written, but we need more of it. If you want to help out writing documentation, you're also more than welcome.

* '''Unit testing''' : we have started writing unit tests for Joomla! This is documented in the wiki, see [[Unit Testing]] for details. This is a very important part to improve the overall quality of Joomla! and increase development speed. If you have experience in this area, we challenge you to come help us.

== FAQ ==
Below you will find as much as possible information we can share on how this events is organized. If you don't find what you are looking for, you can check out the [[PBF FAQ]].

== Organization, logistics and communications ==

Managing this event will be a challenge. The team of [[Pizza couriers]] is working on the organization of this event, taking care of all logistics, infrastructure and communications.

see http://developer.joomla.org/home/26-coordinator-blog/147-the-best-ingredients-for-a-nice-pizza.html

== 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 have any questions regarding this, feel free to contact Wilco Jansen (wilco.jansen@joomla.org).

=== Europe ===
Hotel La Meridiana
Viale Italia 198 - Marina Romea 48010 Ravenna (Ra) Italy
28 June 2008
Additional information [http://www.joomladay.it/ www.joomladay.it]
To register post [http://forum.joomla.it/index.php/topic,44604.0.html here]
[http://www.joomladay.it/component/option,com_contact/task,view/contact_id,1/Itemid,2 Contacts]

JUG Catalan Countries
June 21. Can Domenge Centre Tecnologic. Soldat Arrom quart, 1. Palma de Mallorca Spain
[http://www.joomla.cat JUG Catalan Countries Website]

There will also be a location in the Netherlands (Amsterdam, Rotterdam or Eindhoven, most likely it will be Rotterdam)
If you are interested please send a mail to wilco.jansen@joomla.org

=== North America ===

Webimagery, LLC
843 Carondelet St. Suite 6
New Orleans, LA 70130
USA
[http://jpbf2nola1.eventbrite.com June 21 Registration]
[http://jpbf2nola2.eventbrite.com June 22 Registration]

PICnet, Inc. (DC)
1341 G St, NW, Suite 1100
Washington DC, 20005
[http://www.joomladayusa.org/index.php?option=com_events&type=event&task=details&id=6&Itemid=11 Registration Page]

New York City JUG
Address to be verified shortly
[http://www.joomlanyc.org Joomla NYC Website]

[[Image:http://profile.ak.facebook.com/object3/1074/17/n18143277964_688.jpg]]
Vancouver, BC, Canada
822 Homer (at Robson)
Across from where the JoomlaDay event was held.
Call Mike Hamanaka or Amir Sharifnejad at +1-604-626-9225 and we will buzz you in.
[website to be announced]

=== South America ===
No venue registered

=== Asia/Pacific ===

Spike Systems Pty Ltd
Level 6, 99 York Street
Sydney.
Map here: http://tinyurl.com/4gwatl
URL with additional information will follow soon (including registration option).

------
Please enter your location in Asia here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

=== Africa ===
No venue registered

===Cyberspace===
====Internet Relay Chat (IRC)====
Freenode channel [irc://irc.freenode.net/joomlapbf #joomlapbf] from 21 to 22 June 2008, all times, all timezones.

This channel is available now and throughout the event. We might set up additional channels, if we do they will be listed above.

== 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. If you are traveling to one of the physical locations you are advised to ensure that you have registered on this wiki and have a valid login before you travel. You don't need access to your email account after registration.

=== 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 ===
Pizza can be ordered at a shop near by :-)

Please check the [http://docs.joomla.org/Pizza_Bugs_and_Fun_2#Organization.2C_logistics_and_communications Organization, logistics and communications section] for detail 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 [[PBF Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British/Australian English.
{{:PBF_Contributors_List}}
[[Category: Development]]

Pizza Bugs and Fun 2

2008-06-19T21:08:23Z

Willebil: /* South America */

[[Image:pbf.png|right]]
{{RightTOC}}
We eagerly announce the second Joomla! Pizza Bug and Fun event scheduled for the weekends of '''June 21 and 22''' and '''June 28 and 29'''. It's hard to believe that six months have passed since the first Joomla! Pizza Bug and Fun event. The first PBF helped finalize Joomla! 1.5 and, if all goes as planned, this second event will help prepare Joomla! 1.5.4 for release early in July.

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

== Goals ==

* '''Bugs''' : For our first PBF event, we targeted priority 1 and 2 bugs and tested the entire application. Since it's release, Joomla! 1.5 has been very stable and there are no serious bugs to fix. But, there are a number of medium priority items that require patches and testing. If we are able to empty the tracker during the weekend, it would be an important accomplishment for the community.

* '''Documentation''' : since the last [[Doc Camp 1|Doc Camp]] a lot of documentation has been written, but we need more of it. If you want to help out writing documentation, you're also more than welcome.

* '''Unit testing''' : we have started writing unit tests for Joomla! This is documented in the wiki, see [[Unit Testing]] for details. This is a very important part to improve the overall quality of Joomla! and increase development speed. If you have experience in this area, we challenge you to come help us.

== FAQ ==
Below you will find as much as possible information we can share on how this events is organized. If you don't find what you are looking for, you can check out the [[PBF FAQ]].

== Organization, logistics and communications ==

Managing this event will be a challenge. The team of [[Pizza couriers]] is working on the organization of this event, taking care of all logistics, infrastructure and communications.

more information will be posted as soon as possible to provide guidance to those who are eager to help

== 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 have any questions regarding this, feel free to contact Wilco Jansen (wilco.jansen@joomla.org).

=== Europe ===
Hotel La Meridiana
Viale Italia 198 - Marina Romea 48010 Ravenna (Ra) Italy
28 June 2008
Additional information [http://www.joomladay.it/ www.joomladay.it]
To register post [http://forum.joomla.it/index.php/topic,44604.0.html here]
[http://www.joomladay.it/component/option,com_contact/task,view/contact_id,1/Itemid,2 Contacts]

There will also be a location in the Netherlands (Amsterdam, Rotterdam or Eindhoven, most likely it will be Rotterdam)
If you are interested please send a mail to wilco.jansen@joomla.org

=== North America ===

Webimagery, LLC
843 Carondelet St. Suite 6
New Orleans, LA 70130
USA
[http://jpbf2nola1.eventbrite.com June 21 Registration]
[http://jpbf2nola2.eventbrite.com June 22 Registration]

PICnet, Inc. (DC)
1341 G St, NW, Suite 1100
Washington DC, 20005
[http://www.joomladayusa.org/index.php?option=com_events&type=event&task=details&id=6&Itemid=11 Registration Page]

New York City JUG
Address to be verified shortly
[http://www.joomlanyc.org Joomla NYC Website]

=== South America ===
No venue registered

=== Asia/Pacific ===

Spike Systems Pty Ltd
Level 6, 99 York Street
Sydney.
Map here: http://tinyurl.com/4gwatl
URL with additional information will follow soon (including registration option).

------
Please enter your location in Asia here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

=== Africa ===
No venue registered

===Cyberspace===
====Internet Relay Chat (IRC)====
Freenode channel [irc://irc.freenode.net/joomlapbf #joomlapbf] from 21 to 22 June 2008, all times, all timezones.

This channel is available now and throughout the event. We might set up additional channels, if we do they will be listed above.

== 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. If you are traveling to one of the physical locations you are advised to ensure that you have registered on this wiki and have a valid login before you travel. You don't need access to your email account after registration.

=== 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 ===
Pizza can be ordered at a shop near by :-)

Please check the [http://docs.joomla.org/Pizza_Bugs_and_Fun_2#Organization.2C_logistics_and_communications Organization, logistics and communications section] for detail 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 [[PBF Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British/Australian English.
{{:PBF_Contributors_List}}
[[Category: Development]]

Pizza Bugs and Fun 2

2008-06-19T21:08:04Z

Willebil: /* Africa */

[[Image:pbf.png|right]]
{{RightTOC}}
We eagerly announce the second Joomla! Pizza Bug and Fun event scheduled for the weekends of '''June 21 and 22''' and '''June 28 and 29'''. It's hard to believe that six months have passed since the first Joomla! Pizza Bug and Fun event. The first PBF helped finalize Joomla! 1.5 and, if all goes as planned, this second event will help prepare Joomla! 1.5.4 for release early in July.

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

== Goals ==

* '''Bugs''' : For our first PBF event, we targeted priority 1 and 2 bugs and tested the entire application. Since it's release, Joomla! 1.5 has been very stable and there are no serious bugs to fix. But, there are a number of medium priority items that require patches and testing. If we are able to empty the tracker during the weekend, it would be an important accomplishment for the community.

* '''Documentation''' : since the last [[Doc Camp 1|Doc Camp]] a lot of documentation has been written, but we need more of it. If you want to help out writing documentation, you're also more than welcome.

* '''Unit testing''' : we have started writing unit tests for Joomla! This is documented in the wiki, see [[Unit Testing]] for details. This is a very important part to improve the overall quality of Joomla! and increase development speed. If you have experience in this area, we challenge you to come help us.

== FAQ ==
Below you will find as much as possible information we can share on how this events is organized. If you don't find what you are looking for, you can check out the [[PBF FAQ]].

== Organization, logistics and communications ==

Managing this event will be a challenge. The team of [[Pizza couriers]] is working on the organization of this event, taking care of all logistics, infrastructure and communications.

more information will be posted as soon as possible to provide guidance to those who are eager to help

== 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 have any questions regarding this, feel free to contact Wilco Jansen (wilco.jansen@joomla.org).

=== Europe ===
Hotel La Meridiana
Viale Italia 198 - Marina Romea 48010 Ravenna (Ra) Italy
28 June 2008
Additional information [http://www.joomladay.it/ www.joomladay.it]
To register post [http://forum.joomla.it/index.php/topic,44604.0.html here]
[http://www.joomladay.it/component/option,com_contact/task,view/contact_id,1/Itemid,2 Contacts]

There will also be a location in the Netherlands (Amsterdam, Rotterdam or Eindhoven, most likely it will be Rotterdam)
If you are interested please send a mail to wilco.jansen@joomla.org

=== North America ===

Webimagery, LLC
843 Carondelet St. Suite 6
New Orleans, LA 70130
USA
[http://jpbf2nola1.eventbrite.com June 21 Registration]
[http://jpbf2nola2.eventbrite.com June 22 Registration]

PICnet, Inc. (DC)
1341 G St, NW, Suite 1100
Washington DC, 20005
[http://www.joomladayusa.org/index.php?option=com_events&type=event&task=details&id=6&Itemid=11 Registration Page]

New York City JUG
Address to be verified shortly
[http://www.joomlanyc.org Joomla NYC Website]

=== South America ===
No location signed up

=== Asia/Pacific ===

Spike Systems Pty Ltd
Level 6, 99 York Street
Sydney.
Map here: http://tinyurl.com/4gwatl
URL with additional information will follow soon (including registration option).

------
Please enter your location in Asia here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

=== Africa ===
No venue registered

===Cyberspace===
====Internet Relay Chat (IRC)====
Freenode channel [irc://irc.freenode.net/joomlapbf #joomlapbf] from 21 to 22 June 2008, all times, all timezones.

This channel is available now and throughout the event. We might set up additional channels, if we do they will be listed above.

== 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. If you are traveling to one of the physical locations you are advised to ensure that you have registered on this wiki and have a valid login before you travel. You don't need access to your email account after registration.

=== 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 ===
Pizza can be ordered at a shop near by :-)

Please check the [http://docs.joomla.org/Pizza_Bugs_and_Fun_2#Organization.2C_logistics_and_communications Organization, logistics and communications section] for detail 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 [[PBF Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British/Australian English.
{{:PBF_Contributors_List}}
[[Category: Development]]

Pizza Bugs and Fun 2

2008-06-19T21:05:39Z

Willebil: /* Africa */

[[Image:pbf.png|right]]
{{RightTOC}}
We eagerly announce the second Joomla! Pizza Bug and Fun event scheduled for the weekends of '''June 21 and 22''' and '''June 28 and 29'''. It's hard to believe that six months have passed since the first Joomla! Pizza Bug and Fun event. The first PBF helped finalize Joomla! 1.5 and, if all goes as planned, this second event will help prepare Joomla! 1.5.4 for release early in July.

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

== Goals ==

* '''Bugs''' : For our first PBF event, we targeted priority 1 and 2 bugs and tested the entire application. Since it's release, Joomla! 1.5 has been very stable and there are no serious bugs to fix. But, there are a number of medium priority items that require patches and testing. If we are able to empty the tracker during the weekend, it would be an important accomplishment for the community.

* '''Documentation''' : since the last [[Doc Camp 1|Doc Camp]] a lot of documentation has been written, but we need more of it. If you want to help out writing documentation, you're also more than welcome.

* '''Unit testing''' : we have started writing unit tests for Joomla! This is documented in the wiki, see [[Unit Testing]] for details. This is a very important part to improve the overall quality of Joomla! and increase development speed. If you have experience in this area, we challenge you to come help us.

== FAQ ==
Below you will find as much as possible information we can share on how this events is organized. If you don't find what you are looking for, you can check out the [[PBF FAQ]].

== Organization, logistics and communications ==

Managing this event will be a challenge. The team of [[Pizza couriers]] is working on the organization of this event, taking care of all logistics, infrastructure and communications.

more information will be posted as soon as possible to provide guidance to those who are eager to help

== 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 have any questions regarding this, feel free to contact Wilco Jansen (wilco.jansen@joomla.org).

=== Europe ===
Hotel La Meridiana
Viale Italia 198 - Marina Romea 48010 Ravenna (Ra) Italy
28 June 2008
Additional information [http://www.joomladay.it/ www.joomladay.it]
To register post [http://forum.joomla.it/index.php/topic,44604.0.html here]
[http://www.joomladay.it/component/option,com_contact/task,view/contact_id,1/Itemid,2 Contacts]

There will also be a location in the Netherlands (Amsterdam, Rotterdam or Eindhoven, most likely it will be Rotterdam)
If you are interested please send a mail to wilco.jansen@joomla.org

=== North America ===

Webimagery, LLC
843 Carondelet St. Suite 6
New Orleans, LA 70130
USA
[http://jpbf2nola1.eventbrite.com June 21 Registration]
[http://jpbf2nola2.eventbrite.com June 22 Registration]

PICnet, Inc. (DC)
1341 G St, NW, Suite 1100
Washington DC, 20005
[http://www.joomladayusa.org/index.php?option=com_events&type=event&task=details&id=6&Itemid=11 Registration Page]

New York City JUG
Address to be verified shortly
[http://www.joomlanyc.org Joomla NYC Website]

=== South America ===
No location signed up

=== Asia/Pacific ===

Spike Systems Pty Ltd
Level 6, 99 York Street
Sydney.
Map here: http://tinyurl.com/4gwatl
URL with additional information will follow soon (including registration option).

------
Please enter your location in Asia here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

=== Africa ===
No venue registered

===Cyberspace===
====Internet Relay Chat (IRC)====
Freenode channel [irc://irc.freenode.net/joomlapbf #joomlapbf] from 21 to 22 June 2008, all times, all timezones.

This channel is available now and throughout the event. We might set up additional channels, if we do they will be listed above.

== 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. If you are traveling to one of the physical locations you are advised to ensure that you have registered on this wiki and have a valid login before you travel. You don't need access to your email account after registration.

=== 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 ===
Pizza can be ordered at a shop near by :-)

Please check the [http://docs.joomla.org/Pizza_Bugs_and_Fun_2#Organization.2C_logistics_and_communications Organization, logistics and communications section] for detail 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 [[PBF Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British/Australian English.
{{:PBF_Contributors_List}}
[[Category: Development]]

Pizza Bugs and Fun 2

2008-06-19T21:05:03Z

Willebil: /* South America */

[[Image:pbf.png|right]]
{{RightTOC}}
We eagerly announce the second Joomla! Pizza Bug and Fun event scheduled for the weekends of '''June 21 and 22''' and '''June 28 and 29'''. It's hard to believe that six months have passed since the first Joomla! Pizza Bug and Fun event. The first PBF helped finalize Joomla! 1.5 and, if all goes as planned, this second event will help prepare Joomla! 1.5.4 for release early in July.

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

== Goals ==

* '''Bugs''' : For our first PBF event, we targeted priority 1 and 2 bugs and tested the entire application. Since it's release, Joomla! 1.5 has been very stable and there are no serious bugs to fix. But, there are a number of medium priority items that require patches and testing. If we are able to empty the tracker during the weekend, it would be an important accomplishment for the community.

* '''Documentation''' : since the last [[Doc Camp 1|Doc Camp]] a lot of documentation has been written, but we need more of it. If you want to help out writing documentation, you're also more than welcome.

* '''Unit testing''' : we have started writing unit tests for Joomla! This is documented in the wiki, see [[Unit Testing]] for details. This is a very important part to improve the overall quality of Joomla! and increase development speed. If you have experience in this area, we challenge you to come help us.

== FAQ ==
Below you will find as much as possible information we can share on how this events is organized. If you don't find what you are looking for, you can check out the [[PBF FAQ]].

== Organization, logistics and communications ==

Managing this event will be a challenge. The team of [[Pizza couriers]] is working on the organization of this event, taking care of all logistics, infrastructure and communications.

more information will be posted as soon as possible to provide guidance to those who are eager to help

== 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 have any questions regarding this, feel free to contact Wilco Jansen (wilco.jansen@joomla.org).

=== Europe ===
Hotel La Meridiana
Viale Italia 198 - Marina Romea 48010 Ravenna (Ra) Italy
28 June 2008
Additional information [http://www.joomladay.it/ www.joomladay.it]
To register post [http://forum.joomla.it/index.php/topic,44604.0.html here]
[http://www.joomladay.it/component/option,com_contact/task,view/contact_id,1/Itemid,2 Contacts]

There will also be a location in the Netherlands (Amsterdam, Rotterdam or Eindhoven, most likely it will be Rotterdam)
If you are interested please send a mail to wilco.jansen@joomla.org

=== North America ===

Webimagery, LLC
843 Carondelet St. Suite 6
New Orleans, LA 70130
USA
[http://jpbf2nola1.eventbrite.com June 21 Registration]
[http://jpbf2nola2.eventbrite.com June 22 Registration]

PICnet, Inc. (DC)
1341 G St, NW, Suite 1100
Washington DC, 20005
[http://www.joomladayusa.org/index.php?option=com_events&type=event&task=details&id=6&Itemid=11 Registration Page]

New York City JUG
Address to be verified shortly
[http://www.joomlanyc.org Joomla NYC Website]

=== South America ===
No location signed up

=== Asia/Pacific ===

Spike Systems Pty Ltd
Level 6, 99 York Street
Sydney.
Map here: http://tinyurl.com/4gwatl
URL with additional information will follow soon (including registration option).

------
Please enter your location in Asia here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

=== Africa ===
Please enter your location in Africa here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

===Cyberspace===
====Internet Relay Chat (IRC)====
Freenode channel [irc://irc.freenode.net/joomlapbf #joomlapbf] from 21 to 22 June 2008, all times, all timezones.

This channel is available now and throughout the event. We might set up additional channels, if we do they will be listed above.

== 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. If you are traveling to one of the physical locations you are advised to ensure that you have registered on this wiki and have a valid login before you travel. You don't need access to your email account after registration.

=== 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 ===
Pizza can be ordered at a shop near by :-)

Please check the [http://docs.joomla.org/Pizza_Bugs_and_Fun_2#Organization.2C_logistics_and_communications Organization, logistics and communications section] for detail 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 [[PBF Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British/Australian English.
{{:PBF_Contributors_List}}
[[Category: Development]]

Pizza Bugs and Fun 2

2008-06-19T21:04:33Z

Willebil: /* North America */

[[Image:pbf.png|right]]
{{RightTOC}}
We eagerly announce the second Joomla! Pizza Bug and Fun event scheduled for the weekends of '''June 21 and 22''' and '''June 28 and 29'''. It's hard to believe that six months have passed since the first Joomla! Pizza Bug and Fun event. The first PBF helped finalize Joomla! 1.5 and, if all goes as planned, this second event will help prepare Joomla! 1.5.4 for release early in July.

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

== Goals ==

* '''Bugs''' : For our first PBF event, we targeted priority 1 and 2 bugs and tested the entire application. Since it's release, Joomla! 1.5 has been very stable and there are no serious bugs to fix. But, there are a number of medium priority items that require patches and testing. If we are able to empty the tracker during the weekend, it would be an important accomplishment for the community.

* '''Documentation''' : since the last [[Doc Camp 1|Doc Camp]] a lot of documentation has been written, but we need more of it. If you want to help out writing documentation, you're also more than welcome.

* '''Unit testing''' : we have started writing unit tests for Joomla! This is documented in the wiki, see [[Unit Testing]] for details. This is a very important part to improve the overall quality of Joomla! and increase development speed. If you have experience in this area, we challenge you to come help us.

== FAQ ==
Below you will find as much as possible information we can share on how this events is organized. If you don't find what you are looking for, you can check out the [[PBF FAQ]].

== Organization, logistics and communications ==

Managing this event will be a challenge. The team of [[Pizza couriers]] is working on the organization of this event, taking care of all logistics, infrastructure and communications.

more information will be posted as soon as possible to provide guidance to those who are eager to help

== 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 have any questions regarding this, feel free to contact Wilco Jansen (wilco.jansen@joomla.org).

=== Europe ===
Hotel La Meridiana
Viale Italia 198 - Marina Romea 48010 Ravenna (Ra) Italy
28 June 2008
Additional information [http://www.joomladay.it/ www.joomladay.it]
To register post [http://forum.joomla.it/index.php/topic,44604.0.html here]
[http://www.joomladay.it/component/option,com_contact/task,view/contact_id,1/Itemid,2 Contacts]

There will also be a location in the Netherlands (Amsterdam, Rotterdam or Eindhoven, most likely it will be Rotterdam)
If you are interested please send a mail to wilco.jansen@joomla.org

=== North America ===

Webimagery, LLC
843 Carondelet St. Suite 6
New Orleans, LA 70130
USA
[http://jpbf2nola1.eventbrite.com June 21 Registration]
[http://jpbf2nola2.eventbrite.com June 22 Registration]

PICnet, Inc. (DC)
1341 G St, NW, Suite 1100
Washington DC, 20005
[http://www.joomladayusa.org/index.php?option=com_events&type=event&task=details&id=6&Itemid=11 Registration Page]

New York City JUG
Address to be verified shortly
[http://www.joomlanyc.org Joomla NYC Website]

=== South America ===
Please enter your location in South America here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

=== Asia/Pacific ===

Spike Systems Pty Ltd
Level 6, 99 York Street
Sydney.
Map here: http://tinyurl.com/4gwatl
URL with additional information will follow soon (including registration option).

------
Please enter your location in Asia here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

=== Africa ===
Please enter your location in Africa here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

===Cyberspace===
====Internet Relay Chat (IRC)====
Freenode channel [irc://irc.freenode.net/joomlapbf #joomlapbf] from 21 to 22 June 2008, all times, all timezones.

This channel is available now and throughout the event. We might set up additional channels, if we do they will be listed above.

== 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. If you are traveling to one of the physical locations you are advised to ensure that you have registered on this wiki and have a valid login before you travel. You don't need access to your email account after registration.

=== 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 ===
Pizza can be ordered at a shop near by :-)

Please check the [http://docs.joomla.org/Pizza_Bugs_and_Fun_2#Organization.2C_logistics_and_communications Organization, logistics and communications section] for detail 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 [[PBF Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British/Australian English.
{{:PBF_Contributors_List}}
[[Category: Development]]

Pizza Bugs and Fun 2

2008-06-19T21:04:13Z

Willebil: /* Europe */

[[Image:pbf.png|right]]
{{RightTOC}}
We eagerly announce the second Joomla! Pizza Bug and Fun event scheduled for the weekends of '''June 21 and 22''' and '''June 28 and 29'''. It's hard to believe that six months have passed since the first Joomla! Pizza Bug and Fun event. The first PBF helped finalize Joomla! 1.5 and, if all goes as planned, this second event will help prepare Joomla! 1.5.4 for release early in July.

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

== Goals ==

* '''Bugs''' : For our first PBF event, we targeted priority 1 and 2 bugs and tested the entire application. Since it's release, Joomla! 1.5 has been very stable and there are no serious bugs to fix. But, there are a number of medium priority items that require patches and testing. If we are able to empty the tracker during the weekend, it would be an important accomplishment for the community.

* '''Documentation''' : since the last [[Doc Camp 1|Doc Camp]] a lot of documentation has been written, but we need more of it. If you want to help out writing documentation, you're also more than welcome.

* '''Unit testing''' : we have started writing unit tests for Joomla! This is documented in the wiki, see [[Unit Testing]] for details. This is a very important part to improve the overall quality of Joomla! and increase development speed. If you have experience in this area, we challenge you to come help us.

== FAQ ==
Below you will find as much as possible information we can share on how this events is organized. If you don't find what you are looking for, you can check out the [[PBF FAQ]].

== Organization, logistics and communications ==

Managing this event will be a challenge. The team of [[Pizza couriers]] is working on the organization of this event, taking care of all logistics, infrastructure and communications.

more information will be posted as soon as possible to provide guidance to those who are eager to help

== 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 have any questions regarding this, feel free to contact Wilco Jansen (wilco.jansen@joomla.org).

=== Europe ===
Hotel La Meridiana
Viale Italia 198 - Marina Romea 48010 Ravenna (Ra) Italy
28 June 2008
Additional information [http://www.joomladay.it/ www.joomladay.it]
To register post [http://forum.joomla.it/index.php/topic,44604.0.html here]
[http://www.joomladay.it/component/option,com_contact/task,view/contact_id,1/Itemid,2 Contacts]

There will also be a location in the Netherlands (Amsterdam, Rotterdam or Eindhoven, most likely it will be Rotterdam)
If you are interested please send a mail to wilco.jansen@joomla.org

=== North America ===

Webimagery, LLC
843 Carondelet St. Suite 6
New Orleans, LA 70130
USA
[http://jpbf2nola1.eventbrite.com June 21 Registration]
[http://jpbf2nola2.eventbrite.com June 22 Registration]

PICnet, Inc. (DC)
1341 G St, NW, Suite 1100
Washington DC, 20005
[http://www.joomladayusa.org/index.php?option=com_events&type=event&task=details&id=6&Itemid=11 Registration Page]

New York City JUG
Address to be verified shortly
[http://www.joomlanyc.org Joomla NYC Website]
------

If you want to add another venue, please enter your location in North America
here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

=== South America ===
Please enter your location in South America here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

=== Asia/Pacific ===

Spike Systems Pty Ltd
Level 6, 99 York Street
Sydney.
Map here: http://tinyurl.com/4gwatl
URL with additional information will follow soon (including registration option).

------
Please enter your location in Asia here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

=== Africa ===
Please enter your location in Africa here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

===Cyberspace===
====Internet Relay Chat (IRC)====
Freenode channel [irc://irc.freenode.net/joomlapbf #joomlapbf] from 21 to 22 June 2008, all times, all timezones.

This channel is available now and throughout the event. We might set up additional channels, if we do they will be listed above.

== 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. If you are traveling to one of the physical locations you are advised to ensure that you have registered on this wiki and have a valid login before you travel. You don't need access to your email account after registration.

=== 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 ===
Pizza can be ordered at a shop near by :-)

Please check the [http://docs.joomla.org/Pizza_Bugs_and_Fun_2#Organization.2C_logistics_and_communications Organization, logistics and communications section] for detail 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 [[PBF Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British/Australian English.
{{:PBF_Contributors_List}}
[[Category: Development]]

Pizza Bugs and Fun 2

2008-06-14T22:01:48Z

Willebil:

[[Image:pbf.png|right]]
{{RightTOC}}
We eagerly announce the second Joomla! Pizza Bug and Fun event scheduled for the weekends of '''June 21 and 22''' and '''June 28 and 29'''. It's hard to believe that six months have passed since the first Joomla! Pizza Bug and Fun event. The first PBF helped finalize Joomla! 1.5 and, if all goes as planned, this second event will help prepare Joomla! 1.5.4 for release early in July.

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

== Goals ==

* '''Bugs''' : For our first PBF event, we targeted priority 1 and 2 bugs and tested the entire application. Since it's release, Joomla! 1.5 has been very stable and there are no serious bugs to fix. But, there are a number of medium priority items that require patches and testing. If we are able to empty the tracker during the weekend, it would be an important accomplishment for the community.

* '''Documentation''' : since the last [[Doc Camp 1|Doc Camp]] a lot of documentation has been written, but we need more of it. If you want to help out writing documentation, you're also more than welcome.

* '''Unit testing''' : we have started writing unit tests for Joomla! This is documented in the wiki, see [[Unit Testing]] for details. This is a very important part to improve the overall quality of Joomla! and increase development speed. If you have experience in this area, we challenge you to come help us.

== FAQ ==
Below you will find as much as possible information we can share on how this events is organized. If you don't find what you are looking for, you can check out the [[PBF FAQ]].

== Organization, logistics and communications ==

Managing this event will be a challenge. The team of [[Pizza couriers]] is working on the organization of this event, taking care of all logistics, infrastructure and communications.

more information will be posted as soon as possible to provide guidance to those who are eager to help

== 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 have any questions regarding this, feel free to contact Wilco Jansen (wilco.jansen@joomla.org).

=== Europe ===
Please enter your location in Europe here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

=== North America ===

Webimagery, LLC
843 Carondelet St. Suite 6
New Orleans, LA 70130
USA
URL with additional information will follow soon (including registration option)

PICnet, Inc. (DC)
1341 G St, NW, Suite 1100
Washington DC, 20005
URL with additional information will follow soon (including registration option)

------

If you want to add another venue, please enter your location in North America
here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

=== South America ===
Please enter your location in South America here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

=== Asia/Pacific ===

Spike Systems Pty Ltd
Level 6, 99 York Street
Sydney.
Map here: http://tinyurl.com/4gwatl
URL with additional information will follow soon (including registration option).

------
Please enter your location in Asia here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

=== Africa ===
Please enter your location in Africa here, provide us with:
location and name of the venue, date(s)/time (don't forget the timezone),
url for more info, how to register, contact option

===Cyberspace===
====Internet Relay Chat (IRC)====
Freenode channel [irc://irc.freenode.net/joomlapbf #joomlapbf] from 21 to 22 June 2008, all times, all timezones.

This channel is available now and throughout the event. We might set up additional channels, if we do they will be listed above.

== 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. If you are traveling to one of the physical locations you are advised to ensure that you have registered on this wiki and have a valid login before you travel. You don't need access to your email account after registration.

=== 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 ===
Pizza can be ordered at a shop near by :-)

Please check the [http://docs.joomla.org/Pizza_Bugs_and_Fun_2#Organization.2C_logistics_and_communications Organization, logistics and communications section] for detail 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 [[PBF Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British/Australian English.
{{:PBF_Contributors_List}}
[[Category: Development]]

Pizza Bugs and Fun 2/Contributors List

2008-06-11T16:02:06Z

Willebil: /* Contributors to the second PBF */

Pizza Bugs and Fun 2/Contributors List

2008-06-10T20:52:57Z

Willebil: /* Contributors */