Return-Path: Delivered-To: apmail-cocoon-lenya-dev-archive@cocoon.apache.org Received: (qmail 20105 invoked by uid 500); 10 Jun 2003 08:17:33 -0000 Mailing-List: contact lenya-dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: "Lenya Developers List" Delivered-To: mailing list lenya-dev@cocoon.apache.org Received: (qmail 20093 invoked from network); 10 Jun 2003 08:17:32 -0000 X-Injected-Via-Gmane: http://gmane.org/ To: lenya-dev@cocoon.apache.org From: Andreas Hartmann Subject: Workflow Roadmap Date: Tue, 10 Jun 2003 10:16:10 +0200 Lines: 48 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@main.gmane.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030507 X-Accept-Language: en-us, en Sender: news X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi Lenya developers, before contiunuing the discussion about the workflow schema language specification, I would like to know your opinion about the general WF integration roadmap for Lenya. Up to now, my idea was to implement a minimal feature set with a minimum of costs to keep changes cheap and to avoid unnecessary work that will be obsolete. I always kept in mind that it must be possible to integrate a more complex engine. At the moment, there are two discussions going on: (1) On our list, Gregor and Daniel point out the benefits of a solid and usable WF description language. (2) On OSCOM, many people seem to be in need of a WF engine to be used in CMS. It looks like they want to get started with a common WF project. IMHO this leads to the following questions: (a) Which way do we want to go for the time being? If we follow the path that I suggested, we don't invest more research on the current solution but do it the agile way (KISS + be ready to implement changes rapidly). If we invest much time on the development of our engine and decide to switch to a general solution, the time might be wasted. If we go the agile way, there is the risk of getting difficulties when more complex features are needed. We would have to decide if we want to implement these features or if we drop our code and integrate an external solution. (b) How much do we want to invest on following / influencing external (WF) projects? IMHO this is a quite important question. If we jump on the OSCOM WF train, we could probably influence the project. But it is worth the efforts? So, how do you feel about the further WF development? Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org For additional commands, e-mail: lenya-dev-help@cocoon.apache.org