All Blog Posts (4)

This week we have issued a challenge to Plone consultancies, asking everyone to pledge a specific amount of development time for our 22nd Tune-Up. I will be keeping track of pledges here. If you would like to pledge hours, please email me and I will add your pledge! ACLARK.NET - 8 hours David Brenneman Open Source Solutions - 4 hours Jarn… Continue

If you have commit access to the core, we need your help! We have six tickets ready for commit and 5 more that need to be QA'd before they can be committed. If you're available on July 10th, even for just an hour or so, we need your help! Join us in #plone-tuneup and loan us your skills to help make Plone just a little bit better! We need people with Core commit access to commit the following: http://dev.plone.org/plone/ticket/9019 http://dev.plone.org/plone/ticket/8827 http://dev.plone.org/… Continue

View-only * https://hub.chandlerproject.org/pim/collection/28861330-bfc9-11dd-b513-9bb8ad49fc36?ticket=d52caef0 View and edit * URL availalbe on request. Please post your request, and any other questions/comments, to General Questions in the Plone support fora. Continue

Just make sure we are all on the same page as we move forward with these Tune-Ups, from time to time I'll send out some tips to make sure we make developing on Plone fun and keep it consistent. 1) If you are committing something please reference the ticket number in the post using the trac keywords refs, closes etc. in front of the ticket number like this: refs #1234 If you mark your commit messages like this, they will get posted on the tickets in trac automagically. 2) Don't forget to merge… Continue