Do you want to help in the Tune-Up but aren't sure where to start? We can help!

Tune-Ups are scheduled for the 3rd Friday of every month. 

1) Send an email to carol@sixfeetup.com  or ping me on irc.freenode.net (I am "carolsixfeetup") and let me know you are Tuning Up! This way, I can give you credit for helping out. This is also a good way to ask any questions you may have. I might not know the answer, but I can find someone who can (this is one of the ways the Tune-Up Survey was so successful - fill it out if you haven't yet!)

2) Follow the instructions at http://dev.plone.org/plone/wiki/DevelopmentEnvironment to set up your local development environment. Send an email to carol@sixfeetup.com or ping me (carolsixfeetup) in the irc.freenote.net #plone-tuneup room if you have any problems with this. Please be as detailed as possible with the issue that you are having so I can be most effective at helping solve the problem.

3) Look at the tickets at http://dev.plone.org/plone/report/28 or our accessibility focused tickets at http://dev.plone.org/plone/report/56 and decide what you'd like to fix. Accept that ticket and begin working. If you have to walk away from working on it, please attach a diff to the ticket and describe the work that you have already done - this way, someone can easily pick up where you left off!

4) If you don't think there's anything you'd be able (or have time) to fix, start up a local Plone site that has not yet been modified and begin testing it - try to break it! If you find something that's broken, see if there's already a ticket for it. If not, create one!

Thanks for all your help!

We have been working to clean up the Tune-Up tickets:

• add skill levels (newbie, green-belt, black-belt) to most Tune-Up tickets
• add new tickets, including some that should only take a couple hours to finish
• removed some tickets that were not Tune-Up worthy (too long, too complicated, etc.)

Please take a few minutes to decide which Tune-Up tickets you'll work on during the next Tune-Up, Friday May 18th. If nothing there suits you, take a look at the rest of the Plone tickets to see what you prefer (if you decide to work on one of these, please tag them as "TuneUp".

For those of you with commit rights, we could also use some help committing a few tickets (tagged "forcommit"). Thanks!

--------------------------------------
56th PLONE TUNE-UP Friday, May 18, 2012
9am-6pm in your local time zone!
http://plone-tuneup.ning.com
Join us at #plone-tuneup on irc.freenode.net
Twitter tag: #plonetuneup
--------------------------------------

This month will be our 56th installment of the Plone Tune-Up Day. Come out and help further the Plone project by grabbing some tickets and committing some fixes.  

Get started now!
-> Go to http://dev.plone.org/plone/wiki/DevelopmentEnvironment for instructions on getting your buildout set up. If you need help, ask in the #plone-tuneup room in irc.
-> If you already have a current buildout, please be sure it is checked out from the development buildout's repository at http://svn.plone.org/svn/plone/buildouts/plone-coredev/branches/4.2/ - this will ensure you have all the latest changes.

-> The most recent development release is Plone  4.2rc1!  If you are working on Plone 4 tickets, please point your buildouts to https://github.com/plone/buildout.coredev
-> Choose a Tune-Up ticket - be sure to "accept" it. If you can't, review the process to get commit rights to the Core (not the Collective) at  http://plone.org/community/develop
-> Paste error messages and code to http://pastie.org/ and then ask for help in the #plone-tuneup room
-> Send an email to carol@sixfeetup.com if you have any questions.

Key to Trac tickets keywords:
- Simple tickets are tagged "newbie"
- Tickets of a medium difficulty level are tagged "greenbelt"
- Difficult tickets are tagged "blackbelt"
- Time-consuming tickets are tagged "bigbug"
- Tickets that just need to be tested are tagged "forqa"
- Tickets that are ready to be committed are tagged "forcommit"