RunJob Technical Meeting, 2004-August-03 (0) News- report from stakeholders' meeting (Greg) It was suggested that an API guide is needed to help use RunJob effectively. We have a CMS API guide- is that sufficient? What else goes into the API guide to help exps use RunJob effectively? Primary CDF use case is migrate to SAM. However, they also wants flow control on farms. Shreek is identified as a great place to collaborate. It exists and is "morally" supported in RunJob, it is in use by DZero. If CDF has new use cases, then CDF manpower spent here could make a large impact for all stakeholders. Develop a workplan with CDF. Document the shReek with examples. (1) Releases: Handling development releases and release numbers. Current announced release is 1.3, unannoucned is 1.4. Scheduled for a major release on August 15. Release 2.0 should contain: -Core components in XML -Pylint approved modules -Sub Package directory restructuring to make ShahKAr core on par with other subpackages. (2) XML Followup: -Workplan and coding by Greg. (1) XMLFactory Loader will be generalized to take ContentHandler and object references "parametrically". (See attached for UML scratches.) (2) XML format itself: xyz String 123 False (3) Where to put XML config files? We should have a SHAHKAR_XML_CONFIG_PATH, and it should always contain a Shahkar system area as the first pathname. in the short term, we will distribute the XML directly with the code as "here" documents. (3) Pylint followup Status and workplan for Eric: Jerry/Anzar/Eric are almost done ;-) Close checkins after we make sure Jerry is done, and merge with ShahKar head. (4) New project: Generic configurators for demonstration purposes More functional and explanatory than HelloWorld examples. -"How to take a shell script and turn it into a template" tutorial Jerry is thinking about the scope of this.