We are announcing a Joomla! Pizza, Bugs and Fun event scheduled for Saturday, September 15, 2012. The event is global for virtual participants with local venues wherever they are organized. Joomla 3 is scheduled to be released on September 26th, so hopefully this Bug Squish will play a big part in squashing the remaining bugs.
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 #jpbf12.
- Bugs : We will be working through the CMS Issue Tracker where there are bug reports needing patches and/or testing.
- Documentation : We still have documentation that needs to be done. If you want to help out writing documentation, you're also more than welcome.
Organization, logistics and communications
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 in March. To get an invitation, email your Skype name to Andy Tarr (email@example.com). To make sure you can get in, get your invitation and 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.
If you want to test
- 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 a current SVN copy 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.
- 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.
If you want to code bug fixes
- 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.
If you want to work on Documentation
- 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 and once registered you will have immediate permission to edit any page except for a few that are protected because they are high profile spam targets.
- 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.
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:
- Help screens for Joomla 3.0.
- I would suggest you pick a particular part of the help screens and propagate that through all the help screens, rather than trying to complete a single help screen. For example, make sure every page has an up-to-date screenshot or make sure every page has a correct and up-to-date description, and so on. Help30:Help screens is a complete list of all the help screens.
- Getting Started with Joomla!
- The plan is for this page to become the entry point into a comprehensive, task-orientated Administrators Manual. As you can see, there are plenty of gaps that need filling, so please fill away :P
- Secure coding guidelines
- This needs to be updated, or perhaps a new version created, following the introduction of JInput and the deprecation of JRequest.
- A re-organisation of the Developers page is long overdue and suggestions are welcome. Rather than editing this page directly, I would suggest adding a new sub-page under your user page (eg. User:Jane Doe/Developers so that it can be reviewed and improved before committing a major change to this important page).
We are offering pizza 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 Andrea Tarr (firstname.lastname@example.org) 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 Andy Tarr (email@example.com). Feel free to contact her 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, email your Skype name to Andy Tarr (firstname.lastname@example.org). 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.
For write access to this wiki
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
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
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 Joomlacode or GitHub.
Q: Which one is 3.0?
A: On GitHub, it is the master branch. For SVN, it is the main trunk.
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.