Guvnor - the repository current state of the union

[michaelneale]

Jervis and Michael have been busy discussing and sketching things in the wiki:

http://www.jboss.org/community/docs/DOC-9834
and atom pub here: http://www.jboss.org/community/docs/DOC-12836 (a first cut implementation by Jervis).

There is some still monkey knife fighting over deciding how to go about this in relation to the drools repository (how to reuse, or not). The worry is to reduce the workload in having both drools repository and SOA repository. Ideally there will be maximum code in common, with SOA repository back end being a super set of drools, and the front end being a subset.

See also: http://www.jboss.org/community/docs/DOC-13161

To be continued...

[michaelneale]

A tentative agreement on the structure of the repository (on discussion with Jeff and Mic and jervis) has been reached:

https://www.jboss.org/community/docs/DOC-13221

The repository will have a separate code base initial based on the drools stuff, but ideally the drools repository back end will migrate to using it.

In terms of web front end - there will be separate codebases to drools BRMS, with as much as common widget wise (the SOA repository will probably use the atom pub interface).

The WebDAV + IDE tooling will be in common for the repositories (drools and SOA).