• Project Home

  last modified April 28 by kayeva

When ?

25-27 April 2008

    Where ?

    Ingeniweb's office, Paris, France

    locaux-d-ingeniweb.jpeg

    Address: 1 Rue Royale Saint-Cloud 92210 Ile-de-France France

    How ?

    Here's the scheduling:

    Friday

    • 9h -> 10h - welcoming
    • 10h - topics discussions, team composition
    • 11h - sprint starting
    • 13h - lunch at "Il Gran Sasso" - 10 pl Moustier, SAINT CLOUD
    • 15h - back to sprint
    • 20h - end
    • 21h - drinks at "Mad Maker Pub" - 22, rue Cujas, Paris 5e

    Saturday

    • 9h -> 10h - welcoming
    • 10h - wrapup from Friday
    • 10h30 - sprint starting
    • 14h - lunch at "Il Gran Sasso" - 10 pl Moustier, SAINT CLOUD
    • 15h30 - back to sprint
    • 20h - end
    • 21h - drinks at "Mad Maker Pub" - 22, rue Cujas, Paris 5e

    Sunday

    • 9h -> 10h - welcoming

    • 10h00 - sprint starting
    • 13h - lunch-bag
    • 18h - end of sprint, final wrapup

    How to get there

    Our offices are located in a build building "Bureaux de la colline, floor 9, Building D".

    We will put some posters in the main hall to guide you, so look for the plone logo ;)

    If you are lost, call us :) +33 (0)1.78.15.24.00

    • By Metro : last station on line 10, Boulogne (pont de Saint-Cloud), then walk on the bridge (la seine) to saint cloud, then under the road bridge. You will see a "harley davidson" shop at the first floor of our building, climb the 'rue royale' on the right of it, and our main hall in the first door on the left.
    • By Bus : stop at 'parc de Saint-Cloud' (52, 72, 126, 175) or 'Saint-Cloud', or 'Général-Leclerc' (160, 460, 467) , then walk under the road bridge. You will see a "harley davidson" shop at the first floor of our building, climb the 'rue royale' on the right of it, and our main hall in the first door on the left.
    • By Tramway : line T2, stop at 'parc de Saint-Cloud', then walk under the bridge, you will see a "harley davidson" shop at the first floor of our building, climb the 'rue royale' on the right of it, and our main hall in the first door on the left.
    • By Train : gare Saint-Lazare ou La Défense, arrêt Saint-Cloud

    • By Car : A13 exit Saint-Cloud / from Paris : Porte de Saint-Cloud then D 907 / from Versailles : D 985

    Image

    Where to stay

    The recommended hotel is the Ibis Boulogne. It is situated right across the bridge from Ingeniweb's office, affordable and nice.
    People should hurry up to book an hotel.

    Other places of interest...

    Thanks to google maps, here are all places for the sprint...

    Who ?

    THE REGISTRATION IS NOW CLOSED

    Everyone needs to bring an ID card (regular ID card, passport, driving license) to be able to get into the building

    If you don't have wifi on your laptop let me know

    let everybody knows when you are present here : http://www.doodle.ch/participation.html?pollId=3d88t3zgbwhyrfmn

    This sprint welcomes people that are involved in :

    • Plone development
    • Community product development

    Anyone who is familiar with Plone, Zope and Python is welcome, although this event will not provide any tutorial sessions. Thus, the required level is developers that are used to the Test-Driven Development approach.

    List of participants [name - nickname, company/organization, country/days present - below]:

    1. Mustapha Benali - mustap - Headnet - Denmark (3 days)
    2. Alex Clark - aclark - ACLARK.NET, LLC - USA
    3. Godefroid Chapelle - __gotcha - BubbleNet
    4. Laurence Rowe - elro - obejctvibe.net UK (tentative)
    5. Kai Lautaportti - dokai - Hexagon IT - Finland
    6. Anton Stonor - Headnet - Denmark [hotel: 1 person, single room, 3 nights - april 24-27 ]
    7. Youenn Bousard - Ingeniweb - France [I come with 20 litter of really good wine (muscat and maury), Saturday and Sunday]
    8. Tarek Ziadé - Ingeniweb - France
    9. Gilles Lenfant - Ingeniweb - France
    10. Gael Pasgrimaud - gawel - Ingeniweb - France
    11. [Friday, Saturday] Encolpe Degoute - Ingeniweb - France
    12. Jean-Mathieu Grimaldi - Ingeniweb - France
    13. Aleksi Korvenranta - Hexagon IT - Finland
    14. Kamon Ayeva - Ingeniweb - France [saturday, sunday]
    15. Olivier Lauzanne - Ingeniweb - France
    16. Cyril Lebaupin - Ingeniweb - France
    17. Frédéric Dupré - Ingeniweb - France
    18. Carsten Rebbien - COM.lounge - Germany
    19. Sylvain Viollon - sylvain - Infrae - Netherlands
    20. [2 person occupancy for 3 nights (separate beds) the 24 evening to 27 morning] Todd Matsumoto - Infrae - Netherlands
    21. [share the room of Todd] Wim Boucquaert - wimbou - Infrae - Netherlands
    22. Maik Röder - Yaco Sistemas - Spain
    23. Lennart Regebro - France (All days)
    24. Matthew Wilkes - Circular Triangle – England
    25. Thierry Benita - tbenita - atReal - France
    26. Jean-Nicolas Bès - drjnut - atReal - France
    27. Matthias Broquet - tiazma - atReal - France
    28. Florent Michon - f10w - atReal - France
    29. Jean-Michel FRANCOIS - toutpt - makina-corpus - France
    30. Christophe Combelles - ccomb - Gorfou - France
    31. Alain Meurant - ameurant - Affinitic - Belgium
    32. Laurent Lasudry - __laz - Affinitic - Belgium
    33. Jean-François Roche - jfroche - Affinitic - Belgium
    34. Michel D'HOOGE - mdhooge - France
    35. David Convent - musée des sciences naturelles - Belgium - Friday PM, All Saturday, Sunday PM (no lunchbox)
    36. Mehdi Benammar - Kitry - Luxembourg [ Fri. after noon - Saturday all day - Sunday all day ]
    37. Joël Lambillotte - Sambreville - Belgique
    38. Gauthier Bastien - Sambreville - Belgique
    39. Stéphan Geulette - UVCW - Belgique
    40. Jean-Michel Abé - La Bruyère - Belgique
    41. Olivier Grisel - ogrisel - Paris - France
    42. Bernhard Bühlmann - 4teamwork - Berne- Suisse
    43. Christian Schneider - 4teamwork - Berne - Suisse
    44. Romain Griffiths - Cellfish Media- Paris - France (vendredi - samedi)
    45. Olivier Snickers - Seneffe - Belgique
    46. Christophe BOSSE - Ingeniweb - Paris - France (samedi)
    47. Sébastien Douche - on saturday for photos!
    48. Kit (Christopher James) Blake - Infrae - on sunday

    What ?

    This sprint is focused on Plone 3. The sprint tasks can cover third-party products from the collective or Plone itself.

    The topic list is being discussed and built on the Mailing List

    The sprint topics that are proposed so far are:

    • PloneSoftwareCenter (Alex, Tarek)
      • Finish up PyPI integration (need a distutils-name ID)
      • Finish up ratings and self certification criteria code.
      • Work on storages
        • Provide an abstraction (see http://www.nabble.com/PloneSoftwareCenter-storage-td16202157s6745.html)
        • Add a Filesystem Storage
        • Replace functionality provided by ExternalStorage with ZODB Blobs.
    • Funittest - High-level functional testing for Plone (Maik Röder, Sylvain Viollon, Frédéric Dupré)
      • ClientForm style form filling for Selenium Interpreter
      • Finish the equivalent of PolicyTestCase for Funittest
      • Support for .csv fixtures for dataproviders
      • Better API for expected state generators
    • Documentation
      • Small "Archetypes Dev Manual" update (Kamon)
        • Update the content type tutorial with the use of marker interfaces, explaining their importance...
        • Update with the use of ZCML for the various type's logic registrations (factory, permissions, etc...)
        • Update: I focused on plonesocial, so will work in this later when I get some time.
      • Other aspects: API docs in code / Recipes that can be used later to generate consistent documentation ?
        • Start working in plone recipe cookbook wich consist of eggs created especially for documentation (Youenn)
          • each doctests answers to an question for plone developper (ex : how_to_deal_with_permissions.txt )
            • define a structure for doctest
            • perhaps define metadata for recipe (easy, hard, python , template ...)
          • the namespace of egg concern the api tested ( ex : plone.cookbook.permission )
          • the final goal is to generate a site dedicaced to this cookbook
    • I18N
      • Would be nice to review the french translations and fix some inconsistencies / unclear terms ?
      • zope.i18n needs to be fixed so eggs can provide translations in existing domains (like plone)
    • Grok-style layer for Plone (Lennart, Godefroid)
      • Can we use grokcore.component in Zope2/Plone to register adapters, utilities and subscribers ?
      • Can we build grokkers that would register Five views, viewlets, Plone portlets, and so on ?
    • Pimp my buildbot ! (gawel)
      • see http://tarekziade.wordpress.com/2008/04/01/pimp-my-buildbot/
      • tasks
        • add a svn/hg/... watcher so the buildbot can be configured without having to add a commit-hook
        • provide scheduler configuration in recipe
        • find a solution for the python executable issue: its path is sent to the slave from the master, whitout knowing if the master has it
        • make tests with slaves in windows
        • make it possible to configure the mail that is sent on failures
        • hook a css (see http://buildbot.zope.org)
    • Finish plone.recipe.cluster (gawel)
      • make the Linux version use suprevisord
      • create the windows version
    • Grufspace
      • decide on the future of Grufspace under Plone 3
      • check the delta with TeamSpace
      • I think you should also look at borg.project/borg.localrole which IMO is a simpler solution (Kamon)
    • PloneSocial (Kamon, Dylan Jay (remotely))
        • Start addition of basic social networking features to Plone (plonesocial.invite & plonesocial.share)
        • See http://groups.google.com/group/plone-social-networking for use cases and discussion
        • Update: At the end of the sprint, we had a prototype working. Work will continue in the next weeks to implement our core components.
    • KSS + eventPush (drjnut)
      • Finish the fileupload widget we started with Ramon Bartl on the snowsprint2008
      • Make the zope side facilities of eventPush ready for a livechat app.
    • Upgrade plone.org
      • Migrate ExternalStorage file objects and their filesystem contents to blob
      • Support "double upload" of PSC files to plone.org and dist.plone.org to defer load from plone.org
        • add event listener for PSCFile creation and modification
        • copy the file to the filesystem
    • plone.recipe.apache : Building and configuring Apache for buildout (Youenn)
      • Complementary to plone.recipe.squid or plone.recipe.varnish
      • Add a part for building apache
      • Add a part to generate some good configuration for apache to use with a zope virtual host
    • ZopeSkel local commands: [mustapha]
      • tests
      • make all ZopeSkel templates addcontent aware
      • sub-templates per ZopeSkel template: addcontent command should only enable sub-templates related to the parent template. ie: for an archetype project show only the archetypes sub-templates and for a PAS project or plone3_buildout project show only the sub-templates related to the PAS or the plone3_buildout project
      • localcommands inserting: make possible to insert strings in different places of a file.
      • fix the recreation of paster_plugins.txt in egg-info folder when executing the egg_info setuptools command
      • Add sub-templates:
        • A PAS template + plugins sub-templates
      • write a tutorial based on the PAS template and the plugins sub-templates.
    • collective.themevariations : change plone theme through a form [macadames] :
      • change plone theme using an ATCT (or another method ?)
      • plone site and any plone folderish can have a new theme variation
      • a theme variation inherit of a parent folder theme variation
      • theme images can be overloaded
      • a css can be added into each theme variation
    • contents for the new zope.org site [ccomb] (Frédéric Dupré)
      • find content in the current zope.org that can be migrated/rewritten/summarized to the new site
      • write attractive introductory texts for the different projects (zope2, zope3, zodb, etc.)
    • Create a SimpleMonitor buildout recipe
      • make SimpleMonitor Python 2.4 compatible
      • create a buildout recipe to easily monitor a buildout instance
    • Investigate better ways to deal with long running tasks in Plone (stonor)
      • Play with existing asynchronous packages: zc.async, lovely.remotetask
      • write a plip
    • Write a howto on configuring a secure access to an internet-based instance
      • Rationale: It is quite difficult for newcomer to understand how to create a plone site available through internet that does not leak passwords. There is no point to have a well-thought security policy if (admin) sessions can be simply hijacked by sniffing the network.
      • Collect up-to-date best practices: HTTPS, cookies management, ...
      • Write a tutorial (with maybe some insights on how PAS works).
      • Improve official plug-ins
        • A bug in the Session plug-in prevents automatic creation of new secrets
        • Add checking IP address of principal
        • Use secure-only cookie (side-effect: allows to view site as a visitor through HTTP...)
        • For small sites, use random-generated, not-guessable cookies
    • PloneGov
      • Merge components created in PloneGov from different countries (PloneGov.ch PolneGov.org, PloneGov.fr, CommunesPlone)


    If you have any topic proposal, please register to the project and submit it in the Mailing List.