Pizza Bugs and Fun July 12, 2013

From Joomla! Documentation

Revision as of 20:03, 4 April 2020 by Wilsonge (talk | contribs) (Fix workstation link)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

A Joomla! Pizza, Bugs and Fun event is scheduled for Friday, July 12, 2013. The event is global for virtual participants (both businesses and individuals), with local venues wherever they are organized. The key goal is to fix as many Joomla 3 and Joomla 2.5 bugs as possible.

See the section General Instructions below for instructions.

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

Follow @JoomlaBugSquad on Twitter for updates during PBF and some social fun. The Twitter' hash tag is #JoomlaPBF.


  • Bugs : We will be working through the CMS Issue Tracker where there are bug reports needing patches and/or testing.
  • Documentation : If you want to help out writing documentation, you're also more than welcome. See the Documentation Details below for suggestions.

Organization, logistics and communications[edit]


We have set up a Skype chat for all attendees of the PBF. Skype is invitation only and you are all invited. This is the same chat we used for the PBF last September. To get an invitation, add nick.savov to your Skype contact list. To make sure you can get in, log in before the day of the PBF. This Skype chat will be in English, but other languages can set up their own chat groups as well.

Training Sessions[edit]

There was an optional webinar training session on 11 July, 2013. For anyone that missed it, we recorded the session and added it to YouTube:

Also, on 11 July, 2013, from 17:00-18:00 UTC the Skype group chat will be open for Q&A and for help getting started. See the Skype Chat section below for how to get access to the group chat.


We've dubbed the event as a Business PBF, since it's our first PBF on a weekday (Friday) and we'd like to get more business involved. We've created badges that you can use on your sites to spread awareness of the event and get recognition for your participation:

Furthermore, we'd like to give you more recognition and highlight your pledge of participation by placing your logo and a link to your site on the landing page:

There are three participations levels: Platinum, Gold, and Silver. Platinum is for 10 hours or more pledged to the event. Gold is four hours or more pledged. Silver is pledged to participate in the event.

So, for example, if Company ABC had five of their developers for two hours, then they could use the Platinum badge and have their logo (and link) in the platinum area on the landing page.

The hours you choose to pledge towards the event is totally up to you as an individual or business. As a bonus, if you write a blog post about the event, you can count it as 30 minutes towards your pledge. So if you pledged 5 hours and write a blog post, you'd be helping at the event for 4.5 hours.

Finally, on the day of the event, come and go as you'd like and fulfill your pledged hours. You can help with testing bug fixes, reporting bugs, coding bug fixes, etc. Most of all, enjoy every minute! Have fun, enjoy the fellowship, learn, and make Joomla better for you, your business, your clients, and your friends.

General Instructions[edit]

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

Task List[edit]

You can find a task list at

If you want to test bug fixes (i.e. patches)[edit]

  • Look for issues with a status of Pending. We want at least 2 testers and more on complex issues, so you can test what others have tested already.
  • Use the CMS Issue Tracker as usual, which means you download the patch from the tracker and apply it to your test instance of Joomla.
  • Most of the issues should have test instructions with them.
  • Once you have tested, add comments to the tracker on your results. Start your comment with @test so you will get counted in the stats as a tester. If the test is successful check of a successful text box.
  • Note: You don't have to delete the installation folder when you are using the development version of Joomla. This allows you to reinstall just by deleting the configuration.php file.
  • Note: See the FAQ on how to apply a Git pull request as an SVN patch.
Helpful Documentation

If you want to code bug fixes[edit]

  • Use the CMS Issue Tracker as usual, looking for the issues with a status of Confirmed.
  • When you have a patch, add it to the tracker and change the status to Pending if you are able to. Add testing instructions if they don't already exist.
  • If you want to just put your toe in the water at first, you could see if any of the older patches with a Pending status need updating to the newest build. When you find one that won't apply, you can manually apply it as necessary and then recreate the patch. Uploading to the tracker as a later version and note that you've updated it to the current build. Just make sure that you are using Unix End of Line and create that patch at the project level.
Helpful documentation

If you want to work on Documentation[edit]

  • To edit this Documentation Wiki, you will need a user account on the wiki. If you don't already have one, you may register on Special:UserLogin. You only need a valid email address to register. After confirming your email address you will have immediate permission to edit any page except for a few that are protected because they are high profile spam targets.
  • Important! - You should review the Wiki policy and our use of Abuse filters for new users.
  • Get your user account a few days before and make sure that you are able to sign in since the automatic authorization system can lock some people out.
  • If you'd like something to be edited, but you're not sure what to write exactly, use talk pages to add comments to pages.
  • During the PBF, several experienced Wiki editors will be available in the Skype chat to help you.
Remember, Documentation has bugs too![edit]

You are free to work on any aspect of the documentation that takes your fancy, but here are some suggestions below for stuff that really needs some love and attention. Don't worry, sometimes even the most seasoned wiki editors can get lost, distracted or confused about what to do next. Just ask a question on Skype and someone will try to guide you out.

Don't forget to add the {{inuse}} template to an article you are going to be working on for a long period of time, more than a minute. It helps to prevent editing conflicts.

  • There are a lot of pages of antiquity in the 'Cookie jar' - they are all time stamped, some over 4 years old. The majority were never even started and pertain to Joomla! 1.5. Mark those articles with the {{delete}} template you feel need to be deleted. After PBF, a bot run will clean up the ones marked deleted unless someone objects on the talk page of the article.
  • Browse some articles and feel free to make use of the {{delete}}, {{merge}} or {{JSplit}} templates on articles. Click the previous template links to see how to use and apply them to articles you think need these marker templates.
  • Another area of similar to the 'Cookie jar' is our Needs pages. They are called 'Needs pages' because they are in need of various tasks to complete them. Some of these needs are simple tasks such as reviewing content, adding an image, more content or improvements. Pick a few, give them a little love and help others when they read the docs.
  • Categorisation is always a something easy to do, necessary and in great demand on our wiki! Pages without categories are abundant, pick some titles you know and skip the ones you might not know right off. See how many you can give at least 1 category in an 10 minutes or 1/2 hour. Make it fun and have a competition with others! Make it a real challenge, who can add the most to one category.
  • Help pages, yes we know they are a lot of work, but necessary for beginners and even those with intermediate knowledge of Joomla! Joomla! 2.5 still has a year of life and Joomla! 3 is just getting started! The love you give them will be felt by many users worldwide. You can find the matrix of 2.5 Help Screens here and 3.0 Help Screens here. Some just need to be reviewed and marked complete in status, others need to be started, completed, have images uploaded(670px max width), etc. Make sure you read the 2.5 Style Guide or the 3.0 Style Guide. Anyway questions, just ask on Skype.
  • Join the Developer Tutorials Project and share your knowledge. Sign your name using 4 tildes ( ~~~~ ) on the Developer Tutorials Project page and list what you might be able to do. Feel free to add some tutorial topics to the suggested topics list.
  • The docs team is also working on Beginner Tutorials. Our goal is to make them easy to understand and navigate, something a Beginner can follow easily and learn basic concepts. Think back to when you were new to Joomla! and add a topic about something you struggled with as a beginner.


We are offering pizza (or any comparable locally popular main course) and soda for pre-registered groups. We are not setting a specific maximum, but please don’t go crazy with it. Get enough so there’s plenty for everyone, but not a week’s worth of pizza and soda leftovers for everyone. Contact Nick Savov (nick.savov[at]community.joomla[dot]org , replace [at] with @ and [dot] with .) before the event to register and get details.


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

If you set up a location please send contact information to Nick Savov (nick.savov[at]community.joomla[dot]org , replace [at] with @ and [dot] with .). Feel free to contact him with any questions.



Follow @JoomlaBugSquad on Twitter for updates during PBF and some social fun. The Twitter' hash tag is #JoomlaPBF.

Skype Chat[edit]

We have set up a Skype chat for all attendees of the PBF. Skype is invitation only. This is the same Skype chat we used last. To get an invitation, add nick.savov to your Skype contact list. To make sure you can get in, get your invitation and log in before the day of the PBF.

If you don't already have Skype, you can download it for free from Skype.



Joomla Pizza, Bugs & Fun in Sofia, Bulgaria
Date: Friday 12 july, from 10:00 - 18:00
Location: Headquarters, 8 Racho Petkov Kazandzhiyata Str, Sofia
To attend, please email


Joomla Pizza, Bugs & Fun in Eindhoven, The Netherlands
Date: Friday 12 july, from 11:00 - 18:00
Location: Strijp-S, Torenallee 24 (Apparatenfabriek), Eindhoven
To attend, please add yourself to:

United Kingdom[edit]

Joomla Pizza, Business & Fun in Ipswich, Suffolk
Date: Friday 12 july, from 08:30 - 22:00
Location: Virya Technologies, 30 The Junction, Mallard House Business Centre, The Street, Little Bealings, Woodbridge, Suffolk, IP13 6LT
To attend, please email

North America[edit]

South America[edit]



A Division of Ameex Technologies Pvt. Ltd.
No 284/1A, Rajiv Gandhi Salai (OMR),
Kanthanchavadi, Perungudi PO., Chennai 600 096
Bus Stop: Kanthanchavadi
Landmark: Opp to Prince Infocity/ Adjacent to BP petrol pump.
This location is available for PBF to be held on July 12th, 2013. Location will be available for 20 participants from 10 am to 10 pm IST. 
To reserve your place, please email Hari (hari.prasad[at]ameexusa[dot]com , replace [at] with @ and [dot] with .)and get the confirmation.
Joomla Service Provider'
A Division of Synergy Technologies Services Pvt. Ltd.
701, Acropolis, Military road,
Marol, Andheri (East), Mumbai, Maharashtra, 400059
Bus Stop: Marol Maroshi near SevenHills Hospital
This location is available for PBF to be held on July 12th, 2013. Location will be available for 10 participants from 10 am to 5 pm IST.
Please get your Laptops. Wifi will be provided. 
To reserve your place, please email Anurag (anurag.soni[at]joomlaserviceprovider[dot]com , replace [at] with @ and [dot] with .)and get the confirmation.


Middle East[edit]


For write access to this wiki[edit]

To get write access to this wiki you will need to register here first. Please be aware that the registration process requires a valid email address. This is the same login for updating Joomla documentation.

At a physical location[edit]

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[edit]

Please check the Organization, logistics and communications section for details on how to get involved in working on tasks.


  • All code must be made available under the General Public Licence version 2.
  • All documentation contributions must be made available under the Joomla! Electronic Documentation License. Further information on the JEDL is available in the 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 Contributors List
  • All contributions must be in English. Note that the official language of the Joomla! project is British English.


Q: Where is the code for Joomla?

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

Q: Which one is 3.1?

A: On GitHub, it is the master branch:

Q: Which one is 2.5?

A: On GitHub, it is the 2.5.x branch:

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

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

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


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


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


Please see JDOC Wiki Documentation on: My first pull request


Pizza Bugs and Fun July 12, 2013/Contributors List