Marshall Plan (was: Re: Re: [ANN] Archetypes Roadmap)

Am Mon, 06 Feb 2006 18:19:26 -0200 schrieb Sidnei da Silva:

> On Thu, Feb 02, 2006 at 12:01:12PM +0100, Jens W. Klein wrote:
> | Yes. We need this cool piece of software to make easy generic import and
> | export of content possible. 
> | For example we're developing at the moment
> | XMLForest https://svn.biblhertz.it/repos/public/XMLForest/trunk/XMLForest
> | which also will make migration/deployment of Archetypes based content very
> | easy. I know Kapil is working on something similar. There've been
> | coordination between Kapil, Phil and Gogo in past. 
> | The current problem with Marshall at the moment is just that theres
> | currently no real release management. Anyway, we need to improve it. There
> | are two options: Enfold does release management or I'll step into this. It
> | includes QA, merging important branches (or coordination of how we could
> | make features in branches own Products), tagging and publishing at
> | plone.org in sync with Archetypes Roadmap. Hey, if someone (Sidnei, Alan)
> | is reading it, please give me a statement :-)
> 
> Marshall is feature-complete at the time. It has some stuff that needs
> to be moved out, like the ATXML marshaller. I can cope with making a
> release now and then. Of course it can't depend on a single point of
> failure, so would be great if someone else could step up for helping.

Great. Unfortunally gogo and me started to merge Kapils and your branch
together, and it works almost:



Some notes about Marshall at all:

* tests should work w/o dependency to ArchExample

* Pluggable Namespaces are a great must have feature. Why a separate
Product? It doesnt make any sense to me.

* I dont see any reason why we shouldnt ship Marshall with ATXML.

* I would like to see Marshall under a BSD-Like License, like the
Archetypes one or ZPL: The Archetypes bundle should (not must, but anyway)
have a consistent Licenses.

* As Archetypes Release Manager I would like to have access to the
plone.org/products/marshall

* all Marshalling related code inside Archetypes must move over into
Marshall. One step in direction of a smaller Product "Archetypes" and it
will be easier in future to componentize Marshall and Archetypes at all.
BBB code with deprecation warnings in place of old Marshall.py.

-> All this work at Archetypes 1.4-branch in sync with trunk.

Thx for Marshall and have a nice day!

Jensens
-- 
Jens W. Klein,               WEB APPLICATIONS: ZOPE, PLONE - MDA, SOA
BlueDynamics Tyrol           production: concept, development, design
Klein & Partner KEG          consulting: analysis, coaching, training
http://www.bluedynamics.com  management: projects, process, community




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642