Sprint report Sunday

published Nov 01, 2009
  • People have been signing contributor agreements. We got 23 new core Plone contributors this weekend. Fantastic!
  • Deco: testing javascript stuff (30 percent coverage currently), describing use cases of deco UI, see what differences will be with Plone 4 and 5.
  • slc.linguatools: interface improvements, rewrite from scratch, zc3 based, making sure functionalities are working.
  • funkload buildout, measure nightly performance testing: it works, except creation of a Plone Site currently fails (please help fix this).
  • collective.hostout: worked on multiple python versions, completed plugin for mr.developer integration, database integration, fixed bugs, helped out video guys.
  • amberjack: show to user which tours are completed and which not, translation work, completed some of the tours, talked about using amberjack in third party projects.
  • Trying to revitalize plone Italian community, talking, user map on google.
  • Content import and export, transmogrifier: using zope.brokenfile, dependency graphs, store everything on portal.
  • mr.git: commands, detailed readme.
  • testing crawler: create a very small tests.py file that finds all tests
  • QA: testing packages against different Plone versions with buildbot.
  • fluxbin application/tool: routing, website
  • blob support: CMFEditions, fixed bugs, 1 line of zcml and 3 lines of code will get you blob support.
  • Singing and Dancing: Italian translation, discussion on users handling.
  • Plone Marketing material: get existing material and links.
  • Video: annotations for storing height, width, etc. We think various sizes can be stored, collective.flowplayer work. We will be sprinting at the open society, near the Basilica, with food. Contact us. Send mail to participants list.
  • Roadrunner: working now with dexterity cts, working with z3c.autoinclude, preparing 0.3 release. Check out the dev version and try it out.
  • Banjo: point and click improvements.
  • Limi: Plone now has less css files, move files to the Plone Classic Theme. Some strategic talking. How to improve templating story, add-on story, which things to move to WSGI, what we can kill off in Zope 2, how to handle at versions dexterity references, what parts of CMF to keep.
  • 3rd party products: PloneSoftwareCenter, ZopeSkel, Scrawl, PressRelease, several others.