Actions

Difference between revisions of "Pizza Bugs and Fun March 3, 2012"

From Joomla! Documentation

(North America)
(If you want to work on Documentation)
 
(21 intermediate revisions by 4 users not shown)
Line 28: Line 28:
  
 
==== If you want to code bug fixes ====
 
==== If you want to code bug fixes ====
* Look for issues with a status of Confirmed
+
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, looking for the issues with a status of Confirmed.
* Before you start coding, find the issue in the [https://docs.google.com/spreadsheet/ccc?key=0AuHNF8-wsi3tdGtOU0lqSThaLXB4NDJCUTBMNkxzcXc#gid=0 CMS Issues Google doc] and put your name on the issue so people know someone is working on it. You can sign things out to a group if a group is working on any issue. Remember that everyone is seeing the same document, so please don't hide rows.
+
* 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.
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, which means you download the patch from the tracker and apply it to a current SVN copy of Joomla.
+
 
* When you have a patch, add it to the tracker and change the status to Pending if you are able to.
+
* 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.
* Go back into the Google doc and change the status there to Pending as well and remove your name and add a comment with your name that you added a patch. If the tracker still needs to be changed to pending, you can mention it there.
+
 
 
Helpful documentation:
 
Helpful documentation:
 
* [[Setting up your workstation for Joomla! development]].  A step-by-step guide to installing the Eclipse IDE on your local workstation for Joomla! development.
 
* [[Setting up your workstation for Joomla! development]].  A step-by-step guide to installing the Eclipse IDE on your local workstation for Joomla! development.
Line 43: Line 43:
 
* 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.
 
* 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 [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, which means you download the patch from the tracker and apply it to a current SVN copy of Joomla.
 
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, which means you download the patch from the tracker and apply it to a current SVN copy of Joomla.
 +
* If you find the tracker a little intimidating or want some guidance on bug fixes to test, go to the [https://docs.google.com/spreadsheet/ccc?key=0AuHNF8-wsi3tdGtOU0lqSThaLXB4NDJCUTBMNkxzcXc#gid=0 CMS Issues Google doc]. This Google doc has a list of the bug fixes that need testing. The column on the far right has comments, such as pointing out some easy ones to test. Click on the Link for the item you want to test to go directly to that tracker where you can download the patch file to apply. Double check that the Status is still Pending.
 
* Most of the issues should have test instructions with them.
 
* 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.
 
* 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.
Helpful Documentation:
+
* 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 [http://docs.joomla.org/Pizza_Bugs_and_Fun_March_3,_2012#FAQ FAQ] on how to apply a Git pull request as an SVN patch.
 +
===== Helpful Documentation =====
 
*  [[Tortoise SVN]] Freestanding Windows based SVN. This may be all you need, if you have a Windows PC
 
*  [[Tortoise SVN]] Freestanding Windows based SVN. This may be all you need, if you have a Windows PC
 
* [http://www.adobe.com/devnet/dreamweaver/articles/using_subversion_pt1.html Dreamweaver CS5 with SVN] Start of tutorials on how to use SVN in Dreamweaver
 
* [http://www.adobe.com/devnet/dreamweaver/articles/using_subversion_pt1.html Dreamweaver CS5 with SVN] Start of tutorials on how to use SVN in Dreamweaver
Line 52: Line 55:
  
 
==== If you want to work on Documentation ====
 
==== If you want to work on Documentation ====
* To edit this Documentation Wiki, you will need a user account. If you don't already have one, you may register on [[Special:UserLogin]]. While a brand new user account won't give you all the permissions you'd get with a confirmed and "elevated" account, you will be able to edit most pages.
+
* 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.
 
* 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.
 
* 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.
 
* During the PBF, several experienced Wiki editors will be available in the Skype chat to help you.
{{:Documentation wiki}}
 
  
===== Help Screens =====
+
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:
* There are help screens that still need to be made for 2.5 [[Help25:Help screens]]
+
* Help screens for Joomla 2.5.
 +
*: 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.  [[Help25:Help screens]] is a complete list of all the help screens.
 +
* [[Getting Started with Joomla!]]
 +
*: This needs a comprehensive review as it was originally written for 1.6 and hasn't been much updated since.  I'm sure there are improvements that can be made too.
 +
* [[Administrators]]
 +
*: 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.
 +
* [[Developers]]
 +
*: 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).
  
 
=== Pizza ===
 
=== Pizza ===
Line 99: Line 110:
 
  28 Vernon Street
 
  28 Vernon Street
 
  Brattleboro, VT 05301
 
  Brattleboro, VT 05301
 +
10am to 2pm. We can stay longer if there is interest.
 
  Contact: [mailto:andrea.tarr@joomla.org Andrea Tarr]
 
  Contact: [mailto:andrea.tarr@joomla.org Andrea Tarr]
  
 
  [http://www.vertualize.com San Francisco, PBF event hosted by Vertualize Inc.]
 
  [http://www.vertualize.com San Francisco, PBF event hosted by Vertualize Inc.]
 
  Mike Hamanaka @hamanaka
 
  Mike Hamanaka @hamanaka
  Group will meet Friday evening, March 2nd, 3pm to 9pm PST
+
  Group will meet Friday afternoon, March 2nd, Noon to 6pm PST, informal drop in on the left side of the Fairmont's Caffe Cento
  Location TBD based on group size.
+
  Location: [http://www.fairmont.com/sanfrancisco/GuestServices/Restaurants/CaffeCento.htm Caffe Cento] 801 Powell St., San Francisco, CA  
  San Francsisco, CA  
+
 
  Contact: [mailto:mike@vertualize.com Mike Hamanaka]
 
  Contact: [mailto:mike@vertualize.com Mike Hamanaka]
  
Line 113: Line 124:
 
  Chicago, IL 60610
 
  Chicago, IL 60610
 
  Contact: [mailto:kendall.cabe@timestwotechnology.com Kendall Cabe]
 
  Contact: [mailto:kendall.cabe@timestwotechnology.com Kendall Cabe]
 +
'''Registration is required'''; Visit site above to register for the event
 +
 +
Boise, Idaho
 +
No user group, just some Joomlaphiles getting together to contribute!
 +
Gates Conference Room 10 AM - 4 PM
 +
Boise Public Library, Main Branch
 +
715 S. Capitol Blvd.
 +
Boise, ID 83702
 +
Contact: [mailto:info@bluebridgedev.com John Hooley]
  
 
=== South America ===
 
=== South America ===
Line 125: Line 145:
 
http://www.meetup.com/Joomla-User-Group-Sydney/events/53020132/
 
http://www.meetup.com/Joomla-User-Group-Sydney/events/53020132/
 
</pre>
 
</pre>
 +
 +
JUG Pune (India)
  
 
=== Africa ===
 
=== Africa ===
Line 170: Line 192:
  
 
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.
 
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: SVN & Git are two different ways of doing version control for software. Joomla is in a transition stage of moving from SVN to Git. Most 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.
 +
 +
[[Image:eclipse-pull-request-1.png]]
 +
 +
Many of this pull requests will also have extra folders on the internal file names like a/ and b/.
 +
 +
[[Image:eclipse-pull-request-3.png]]
 +
 +
In Eclipse, to remove those automatically, change Ignore Leading Path Name Segments to 1.
 +
 +
[[Image:eclipse-pull-request-2.png]]
  
 
==Contributors==
 
==Contributors==
 
{{:Pizza Bugs and Fun March 3, 2012/Contributors List}}
 
{{:Pizza Bugs and Fun March 3, 2012/Contributors List}}

Latest revision as of 04:34, 3 March 2012

Pbf.png

Contents

We are announcing a Joomla! Pizza, Bugs and Fun event scheduled for Saturday, March 3, 2012. The event is global for virtual participants with local venues where ever they are organized. We squashed a lot of bugs last month, but as more people use a new release, we always find more. We'll also have documentation ready to be worked on.

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.

Goals

  • 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

Communication

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 December. To get an invitation, email your Skype name to Andy Tarr (andrea.tarr@joomla.org). 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.

General Instructions

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

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.

Helpful documentation:

If you want to test and you have or can set up SVN and XAMPP/MAMP

  • 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.
  • If you find the tracker a little intimidating or want some guidance on bug fixes to test, go to the CMS Issues Google doc. This Google doc has a list of the bug fixes that need testing. The column on the far right has comments, such as pointing out some easy ones to test. Click on the Link for the item you want to test to go directly to that tracker where you can download the patch file to apply. Double check that the Status is still Pending.
  • 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.
Helpful Documentation

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 2.5.
    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. Help25:Help screens is a complete list of all the help screens.
  • Getting Started with Joomla!
    This needs a comprehensive review as it was originally written for 1.6 and hasn't been much updated since. I'm sure there are improvements that can be made too.
  • Administrators
    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.
  • Developers
    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).

Pizza

We are offering pizza and soda for pre-registered groups. We aren’t 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 (andrea.tarr@joomla.org) before the event to register and get details.

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 set up a location please send contact information to Andy Tarr (andrea.tarr@joomla.org). Feel free to contact her with any questions.


Europe

Joomla User Group Suffolk
Jackson Civil Engineering
30 White House Road 
Ipswich, Suffolk, IP1 5LT
10:00 - 15:30 GMT
Contact: Matt Meyrick
Joomla User Group France
B5Prod agency
31 rue des Tuiliers
69008 Lyon
9:00 - 18:00 GMT
Contact: Marc Studer
Joomla User Group France
Agerix agency
25 rue Fernand Belliard
33100 Bordeaux
9:00 - 18:00 GMT
Contact: Eric Lamy

North America

Joomla User Group New England
Marlboro College Graduate School
28 Vernon Street
Brattleboro, VT 05301
10am to 2pm. We can stay longer if there is interest.
Contact: Andrea Tarr
San Francisco, PBF event hosted by Vertualize Inc.
Mike Hamanaka @hamanaka
Group will meet Friday afternoon, March 2nd, Noon to 6pm PST, informal drop in on the left side of the Fairmont's Caffe Cento
Location: Caffe Cento 801 Powell St., San Francisco, CA   
Contact: Mike Hamanaka
JoomlaChicago User Group
Offices of Taylor Bruce Design Partnership
213 WEST INSTITUTE PLACE Suite 705
Chicago, IL 60610
Contact: Kendall Cabe
Registration is required; Visit site above to register for the event
Boise, Idaho
No user group, just some Joomlaphiles getting together to contribute!
Gates Conference Room 10 AM - 4 PM
Boise Public Library, Main Branch
715 S. Capitol Blvd.
Boise, ID 83702
Contact: John Hooley

South America

Asia/Pacific

Sydney, Australia 3pm-9pm
Hosted by Tim Plummer - Tweet @bfsurvey
InterfaceFLOR (usual Sydney JUG venue)
101 Chalmers Street, Surry Hills, NSW
http://www.meetup.com/Joomla-User-Group-Sydney/events/53020132/
JUG Pune (India)

Africa

Middle East

Virtual

Skype Chat

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 December. To get an invitation, email your Skype name to Andy Tarr (andrea.tarr@joomla.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.

Registration

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 detail on how to get involved in working on tasks.

Requirements

  • 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.

FAQ

Q: Where is the code for Joomla?

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

Q: Which one is 2.5?

A: For SVN, it is the main trunk. On GitHub, it is the master 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: SVN & Git are two different ways of doing version control for software. Joomla is in a transition stage of moving from SVN to Git. Most 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.

Eclipse-pull-request-1.png

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

Eclipse-pull-request-3.png

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

Eclipse-pull-request-2.png

Contributors

Thanks to everyone who participanted in the Joomla! Pizza, Bugs and Fun on March 3, 2012. Lots of people worldwide tested, coded/fixed and documented new features and issues in Joomla! 2.5, helping to improve the release. Some of the countries represented were the United Kingdom, France, Germany, Denmark, The Netherlands, Israel, the United States, Canada, Australia, Malaysia, South Africa, and India. It was great to see so many people come out to help. These are the statistics from the Joomla CMS Issue Tracker and Joomla CMS Feature Tracker for the period. Thanks must also go out to the people not on these charts including those who did documentation, those who tested but didn't have a login to the trackers and those giving support.

  • Andrea Tarr (Event organizer)
  • Mark Dexter
  • Elin Waring
  • Jean-Marie Simonet
  • Brian Teeman
  • Ofer Cohen
  • Saurabh Shah
  • Jean-Claude Richard
  • Adrien Baborier
  • Nicolas Claverie
  • Marc Studer
  • Eric Lamy
  • Benjamin Darmon
  • Laurent Claude
  • Jean-Paul Fabre
  • MIG Manickam
  • Mihaly Sarki
  • Yann Gomiero
  • Annick Aeschimann
  • Pierre Sempé
  • Serge Billon
  • Simon Grange
  • Stéphane Benoît
  • Franck Arroyo
  • Olivier Lafenêtre
  • Elisabeth Moore
  • Heidi Stancliff
  • Dianne Henning
  • Abby Kingman
  • Ajay Lulia
  • Michael Babker
  • Kendall Cabe
  • Dennis Kmetz
  • Linda Lafianza