Plone Tune-Up Network

Advancing Plone One Ticket At A Time

Plone Tune-Ups are regular online events that aim at addressing tickets in the Plone issue tracker and advancing the Plone CMS in general.

Members

  • Cleber J Santos
  • Thomas Clement Mogensen
  • Simone Deponti
  • Alex Clark
  • Sandibell Coutiño Arteaga
  • Sune Brøndum Wøller
  • Steve McMahon
  • David Glick
  • Hannes Calitz
  • Helge Tesdal
  • massimo azzolini
  • JoAnna Springsteen
  • Andrew Mleczko
  • witsch
  • staeff
  • Jim Nelson

Groups

Latest Activity

on Friday
Thomas Clement Mogensen is now a member of Plone Tune-Up Network
on Friday
Simone Deponti is now a member of Plone Tune-Up Network
on Tuesday
Cleber J Santos updated their profile
October 29
Sandibell Coutiño Arteaga I want to come back to you...... Plone I miss you jiji
October 29
Cleber J Santos and Hannes Calitz joined Plone Tune-Up Network
October 29
October 23
October 23
 

What's Up?

--------------------------------------
23rd PLONE TUNE-UP
November 13th, 2009
9am-6pm your local time!
Join us at #plone-tuneup on irc.freenode.net
Twitter tag: #plonetuneup
View the list of tickets for this Tune-Up
View the list of other tickets you could work on
(if you choose tickets in this list, please tag them "TuneUp23")
--------------------------------------

Get started now!
-> Choose a ticket and "accept" it. If you can't, review the process to get commit rights to the Core (not the Collective)
-> Get the buildout
-> Paste error messages and code to http://paste.plone.org/


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"

23rd Tune-Up Prize:
The 23rd Plone Tune-Up winner will receive a $25 (or equivalent amount in your local currency) iTunes gift certificate.
Past Tune-Up prize winners include: claytron, dbrenneman, encolpe, massimo, garbas, hannosch, maurits, Ricardo Alves, grahamperrin, hexsprite, csenger, james4765, sixstring, t55e, pelle, calvinhp, Amleczko and dukebody.

Past Tune-Up Results:
View the list of tickets closed at the 13th Plone Tune-Up
View the list of tickets closed at the 12th Plone Tune-Up

Blog Posts

JoAnna Springsteen

October 23rd Tune-Up Pledges

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
JarnContinue

Posted by JoAnna Springsteen on October 5, 2009 at 12:00pm

JoAnna Springsteen

Wanted: Developers with Commit Access to the Core

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

Posted by JoAnna Springsteen on July 2, 2009 at 9:41pm

Graham Perrin

Plone tune-ups: calendar of events, list of tasks

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.

Posted by Graham Perrin on December 19, 2008 at 2:42am

Calvin Hendryx-Parker

Plone Tune-Up Tips

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

Posted by Calvin Hendryx-Parker on November 16, 2008 at 11:03pm

Photos

Loading…

Music

Loading…
 
 

About

 

© 2009   Created by Gabrielle Hendryx-Parker on Ning.   Create Your Own Social Network

Badges  |  Report an Issue  |  Privacy  |  Terms of Service