The best ingredients for a nice Pizza

June 20th, 2008

We’re very close to the second Pizza, Bugs and Fun (PBF) event. As you might have noticed, we have extended the PBF event for a second weekend and now have participants from almost every continent. If you are able to join us at one of these venues, we would love to have you. If you can’t come to a venue but you still want to help, you can just sign in from your location.

Joining in is fairly easy but only Bug Squad members have access and can manage the tracker. We might consider opening it up for the PBF event, but somehow we think that will become a major mess 😉 Like the first PBF event, we set up an easy way to join the PBF participants. When you arrive in the pizza shop, check into the Bazaar by doing these things:
  1. Sign on to the IRC channel (#joomlapbf on freenode) and introduce yourself to the others. Never used IRC? Learn more here and here.
  2. Join in the discussion and get to know everyone. If you have any questions, feel free to ask! At any point, if you have questions, this is where to ask!
  3. If you plan to help with testing bugs or creating patches, register on JoomlaCode so that you can add comments to the artifacts.
  4. You also need to register on the shared Google Document. When you want to get registered, please ask in IRC and the PBF team will contact you to get your e-mail(g-mail) account.
  5. If you plan to assist with documentation, register on so you update to Wiki.

PBF Goal 1: Test pending artifacts

Our first goal for the PBF event is to test all tracker items with "pending" status. This is a collection of artifacts where a patch already is provided, but it has not been fully tested yet. We would love to see participants start by testing these artifacts. We like to have at least two successful tests for simple issues, more for complex ones. In order to help with area 1 (testing patches), you must do the following:

  1. Go to the Google Document (spreadsheet) and pick an issue with "pending" status. Sign up to begin testing by entering your (nick)name next to the issue you plan to test.
  2. Go to the Joomla! bug tracker to learn more about the issue and find the patch.
  3. Apply the patch to your testing site. (Need to know more about setting up your testing site?)
  4. Based on the testing instructions or problem description, see if the patch has the intended result.
  5. Make sure nothing else appears to break.
  6. Post a comment on the Joomla! bug tracker about your results.
  7. If you think the patch is ready to go into the codebase, let one of the couriers know in the IRC channel.

PBF Goal 2: Try to confirm all open artifacts

A lot of artifacts have been reported in the Joomla! bug tracker and the default status of these items is "open." Not every artifact is a real issue and, to confirm this, we need everyone to work on validating open artifacts. As soon as an artifact is confirmed, it will get the status "confirmed" (or another status that will close the artifact in case it cannot be confirmed). Participants who want to work on this goal should do the following:

  1. Go to the Google Document (spreadsheet) and pick an issue with "open" status. Sign up to begin testing by entering your (nick)name next to this issue.
  2. Go to the Joomla! bug tracker to learn more about the issue and see if you can reproduce the problem.
  3. If you are able to confirm the problem, add a comment on the artifact and mark the item "confirmed" in the shared Google document. Also note that it cannot be confirmed, if that is the result, along with your PHP version, browser or other useful information.
  4. Make a small note in the IRC channel that you have confirmed (or cannot confirm) the artifact.

PBF Goal 3: Provide patches

Once issues have been confirmed, it’s time to create patches. This is the area where developers are at their best 😉 When you plan to work on a patch, please perform the following steps:

  1. Go to the Google Document (spreadsheet) and pick an issue with "confirmed" status. To make sure people know you are working on the artifact, entering your (nick)name on the artifact line.
  2. Work on solving the issue and when you’re done, create the patchfile.  
  3. Add a comment to the tracker item. Provide a detailed explanation of how to test the patch.
  4. Change the status in the Google Document to "pending." and ask if someone with access to the tracker to do the same with the individual status of the artifact.
  5. Notify the IRC channel that you have a patch ready and ask if someone with appropriate access to attach your patch to the artifact and set the status to "pending."

PBF Goal 4: Write documentation

  1. Register on so you update to Wiki.
  2. Take a look at and choose a topic you would like to write about.
  3. Enter {{inuse}} at the top of the page you are working on and save it so others know that someone is working on it.
  4. Write your document. 🙂
  5. When you have finished working on a page, remember to remove the {{inuse}} from it.
  6. Let those idling on the IRC channel know that another task is complete. It’s great to celebrate our victories.

PBF Goal 5: Firefox 3 testing

  1. Please pay close attention to template, administration and fron-end behaviour when you use firefox 3.
  2. If you find an issue, please report an issue on the  Joomla! bug tracker.

The team of Pizza Couriers hopes to meet you all during the event!

Regards Chris Davenport, Kevin Devine, Anthony Ferrara, Wilco Jansen, Jennifer Marriott, Ron Severdia, Amy Stephen, and Elin Waring.