• Sprint Topics

  last modified March 16, 2007 by cjj

BBQ Sprint Topics work page

Please express interest for a topic by adding your name beside anything you would like to work on or lead.


Grok: Live Caveman Application Development

on-point: Philikon
continuations: fifer

First day of the sprint Philip will lead a tutorial / space-monkey session for grok.  Participant will be introduced to grok by Philip as a live interactive application development experience.   This excercise will work like this:

  1. Introduce folks to new ergonomic RSI-averting way to approach Zope 3
  2. Allow Philikon to see what irritates folks  or irritate him
  3. Folks and Philikon smash irritants with giant grok hammer
 
Richard has expressed an interest in exploring grok extensions(megrok.five, megrok.*) as a new approach to RAD in Zope2 and Plone.  Such an effort might leverage Alec Mitchell's recent work on plone.app.form and plone.relation and improvements in the widget story.   Others might be interested in figuring out how to add a grokker to speed development.


Xappa / Frank

on-point: michelp
interested: tres, ian, whit, jim allman, (kapil?)

Micro-App Search Appliance and Zope 3 integration.  Originally named xappa in reference to zope/xapian integration, now code named Frank as a general api for searching that might possible encompass xapien, lucene, pylucene and other services.

It might be cool to define the application-side API for an external
search engine, and then implement it via each of the three backends.
For one thing, that would let us test each one using identical workloads.

[Tres Seaver]

I chatted with the Grassy Knoll guy (pfein on FreeNode) and he's going to put together a command-line script to interact with GK, which should be a helpful example.  It would probably be good to ping him on IRC before you start working with it, to check if it's in a proper state (since it is very young).  Directly using PyLucene seems like it might be difficult, as it requires you use gcj threads, and generally seems like a bit of a nuisance to have in-process, especially in an already big process like Zope's.  If it's out-of-process, we might as well use/extend Grassy Knoll.  It is possible to run a JVM inside Python, which is something else entirely, and might be worth trying if you want direct access to Lucene; but at that point it seems like it's pursuing too many options at once, especially with Solr in the mix too. -- Ian B



PLIP 128 - Vice and the Wages of Syn(dication)

Unifying the zope/plone/at syndication story into a single set of properly packaged python libraries.

on-point: Derek, Chopin, Paul B.


Relativity

Alec Mitchell on  plone.relation:
"It's the equivalent of the Archetypes ReferenceEngine, which is a bit of a mess.  ... I've got 100% test coverage on the packages so far, but UIs and documentation cleanup would be very valuable. 

If someone wants to try their hand at getting AT to use this stuff internally (on a branch of course) that would make for a really nice proof of
concept. 

The engine itself is super z3-ified so it's a really great opportunity for people to play with something that's about as close to pure Zope 3 in Zope 2 as we can manage right now. 

There will likely still need to be some event handling code written to ensure that everything is appropriately updated when content is deleted or moved around."

[Alec Mitchell]

Alec Mitchell has recent landed some very attractive new code for modelling relationship in zope 2 using zope corporations acclaimed zc.relationship library.   This code is ready for it's next step: ui, documentation, and use in applications.  This is a great opportunity to learn an important new technology applicable in zope2 and zope3, as well as a chance to work with adapters, views and subscribers.

Links


Some Possible Tasks

  • UI for relation CRUD
    • formlib widgets
    • add, edit, delete forms
  • UI for graph inspection
  • five.intid object events:
    Since five.intid has to use paths to access objects, when canonical pathes change, they need to be updated
  • practical documented examples
  • Migrate AT to use intids for UID



Plone 3 Bugs, Docs and Tests

on-point: whit, dray, jjmojojjmojo, blambert, jonthomas

Whit needs to do some wicked fixes/improvements for the beta release and will be leading folks generally interested in testing, exploring and fixing Plone 3.  If we have significant interest, we may do an afternoon of Plone 3 bug smashing.

Plone 3 Bug Bash



World o' Widgets

on-point: accepting resumes

Zope 3 based content-types and zope 3 schemas offer many advantages over older AT based content types.  One area zope3 doesn't do quite as well is the variety and quality of available widgets for rendering schema.   We would like to make available the same quality and selection of widgets that Archetype has out of the box.

This topic offers excellent oportunity to:
  1. win the admiration and love of the entire zope community
  2. work in pure zope3 in a fast iterative style
  3. create code you can reuse again and again


Plone Commerce , aka GetPaid

on-point: hazmat, cjj, robline

Plone Commerce is a project is set up a base platform for commerce in Plone. It is not your dream ecommerce store ported to Plone...quite the contrary, it is very simple. It is meant to make payment processing possible for Plone sites and therefore enable simple transactions (ie donations or a purchase of single object). It is also meant to enable developers to build other products for more ornate commerce processes (stores, registrations, etc) leveraging this as the backbone. Please see our project page for lots more info...


PloneSoftwareCenter

on-point: Chris Calloway, Aclark, fifer

  • knocking out the todo
  • distribution
  • generic setup


Zope infrastructure

  • Philip's patch for Acquisition (enable __parent__ traversal and meaningful usage of ILocation in Zope2)

possible topics:
  • ZopeTestCase/Zopelite Layer


Mail

interested: Steve McMahon, Robert Marianski, Chris Abraham, Alec Mitchell, Rob Miller

Listen

Listen is a mailing list management application for Plone that allows for easy creation of mailing lists through the Plone interface, forum-like posting and viewing of archives, and a choice of list types. 

on-point: rmarianski, cabraham
infosession: [day 3 | room 2 | morning]



Unified Improved Mailing List Handling

Improving the python mail story and moving mail handling out of Plone. 

on-point: Steve McMahon


Groupware / Subsite Management

Possible topics:


Deliverance

on-point: Ian Bicking
interested: chopin, dr, mcdonc, cbcunc

  • project page: spec, open issues, ideas
  • Possible topics:
    • social engineering: tutorial/howto, configuration skeletons, documentation
"So, I'd like to figure out how people can use Deliverance in Zope and/or 
Plone with much less setup.  I'll also show people how Deliverance 
works, some about why it works the way it does, as we try to figure out 
the best strategy for deployment.  Help from someone with knowledge of 
Zope's innards would be helpful, specifically how to do transformations 
without entirely pulling apart Zope."

[Ian Bicking]

GenericSetup

on-point: calvinhp, rafrombrc, tres seaver

interested: fifer, jim allman

possible topics (working *on* GS):

  • shared migration architecture
  • quickinstaller replacements
  • support for deltas in profiles
  • Support removing steps from a profile

Possible topics working *with* GS

"Personally, I would love to kill off the way the archetypes
setup dance is currently done -- it makes it nearly impossible to do the
Right Thing (tm) in a custom site profile (a "baseline")."

[Tres Seaver]