We are announcing a second Joomla! Pizza, Bugs and Fun event scheduled for Saturday, March 16, 2013. The event is global for virtual participants with local venues wherever they are organized. The key goal is to fix as many Joomla 3 and Joomla 2.5 bugs as possible before Joomla 3.1's, which will be on or around the 25th of March, and Joomla 2.5.10's release.
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.
The twitter hash tag is #jpbf13.
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[at]iowawebcompany[dot]com (replace [at] with @ and [dot] with .) 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.
These instructions may change as we get closer to the event.
You are free to work on any aspect of the documentation that takes your fancy, but here are some suggestions for stuff that really needs some love and attention:
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.
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only. This is the same Skype chat we used in March. To get an invitation, add nick.savov[at]community.joomla[dot]org (replace [at] with @ and [dot] with .) 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!Day Boston Microsoft New England Research & Development Center One Memorial Drive Suite 100 Cambridge, MA 02142 10:00 AM-12:15 PM EST and 1:30 PM-4:00 PM EST
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.
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.
Please check the Organization, logistics and communications section for details on how to get involved in working on tasks.
Q: Where is the code for Joomla?
A: The current Joomla code can be found either on Joomlacode or GitHub.
Q: Which one is 3.0?
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: Any known issues with JForge and Chrome on Windows?
A: It have been seen that browsing the JForge tracker, Chrome may ask for a missing plugin (windows media player). No workaround for this is yet known.
Q: How do I apply a Git pull request as an SVN Patch?
A: Git & SVN are two different ways of doing version control for software. Joomla is in a transition stage of moving from SVN to Git. Many of the patches will be SVN patches which you'll find in the files tab at the bottom of the tracker. Some trackers will have Git "pull requests" instead.
These git pull requests can still usually be applied like SVN patches if you only have SVN. Take the URL of the pull request, add ".patch" to the end of it and use that as a URL to the patch.
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.