Attendance: Steve Landry, Mike Moretti, Amon Horne, Stuart Brown, Adam Lister

This was the first Working Group Meeting. The group decided to focus on these goals for now:

  1. Frameworks and Code Skeletons: Standard stack of jars based on SASH with some of the options removed (for instance, include sitemesh, exclude tiles). The group felt it was wise to begin by cribbing the work that had been done by the insideMIT team during the SASH 2 evaluation with SourceLabs.
  2. Messaging: IS&T has no messaging infrastructure for it's projects. Could be part of the "stack" or services as part of the MAP web services infrastructure, or both.
  3. Authorizations, Roles Services: Generally, more web services around the idea of identity management.
  4. Source Control Strategy: Standardized use of SVN, Maven, and other tools. Best practices plus use of standard systems (svn.mit.edu and isda-maven1.mit.edu).
  5. PHP Stack: Or lack thereof.
  6. Workflow engine: noted that the SAP applications have this built in to SAP but other systems do not.

Tasks

  1. Amon H: Recruit Working Group members from the PHP development community.
  2. Amon H: Add notes to wiki, map-contrib, with what he has so far about workflow (swamp).
  3. Mike M: Configure isda-maven1, add artifactory, "MIT SASH" repositories.
  4. Adam L: Contributue "MIT SASH" documentation and downloads based on insideMIT's OAS/Java 1.4 stack, add 1.5 version (closer to SourceLabs stack)
  5. Stuart B: Contribute current notes on messaging to map-contrib. Design of new authorization web services based on his projects' current needs.
  6. Steve: Authorizations to working group to admin maven repository, access to "map" repos in svn.mit.edu. Complete charter, review by managers of working group members.
  • No labels

1 Comment

  1. Catherine T Iannuzzo

    Excellent progress!

    I suggest looking at the JBOSS workflow engine. This is one of the open source leaders. Alfresco uses it, and Alfresco is definitely going to be part of our landscape.

    As for messaging, is the group looking for a JMS implementation? I think the two contenders here are JBOSS Messaging (which does not require the JBOSS app server) and Apache ActiveMQ, which is usable by PHP apps as well as Java.

    Is there interest in an ESB?  

    And for the PHP folks, what do you think of Cake?