Hello: On Fri, 22 Jan 2010, Roman Chyla wrote: > Tibor said that perhaps next Tuesday we could have a low-level > discussion about technical details of a workflow engine with > developers.
We shall meet on Tue 26-Jan-2010 16:00-18:00 at 31-S-023 We will brainstorm about the following matters: Do we like workflow-oriented programming paradigm? Are there Invenio modules that would profit from a workflow engine? What would the concrete use cases be? What would the workflow configuration language look like? High-level business friendly? Low-level Python developer friendly? Which options should it provide to cover for all Invenio use cases? Are there existing Python libraries that we could reuse? Pros/cons? Would we need to build a new Invenio-specific tool from scratch? What kind of GUI workflow visualization tools would we want? Do we need a full-fledged GUI editor? The goal of this discussion is not to come up with answers on-the-spot, but to identify all possible workflow engine use cases inside Invenio, which would help in drafting common Invenio-wide specs for the workflow language and in seeking a common Invenio-wide solution. CC-ing the Indico folks: please join us in the brainstorming if you have been thinking about workflow engine technologies for Indico. We may have clear synergies here. > I prepared a wiki page in a hope of getting feedback from you, please > see it here: > > https://svnweb.cern.ch/trac/rcarepo/wiki/InspireWorkflowEngine In addition to Roman's wiki page, please read up on various available technologies, e.g. GoFlow <http://code.djangoproject.com/wiki/GoFlow> will re-raise the old musings about pros/cons of moving to a third-party framework like Django or web.py. Best regards -- Tibor Simko ** CERN Document Server ** <http://cds.cern.ch/>
