Mach II Team Meeting April 14, 2009

Attendees: Peter Ferrell, Matt Woodward, Kurt Wiersma, Brian FitzGerald

Time: Listed in Eastern time zone.

9:14p

• Kurt: wrapping up some 1.8 tickets
• Kurt: refactoring expression evaluator
• Kurt: wrapping up some URLRoute stuff (rewrite rules, etc)
• Peter: suggests moving refactoring of expression evaluator (EE) to Mach-II 1.9 milestone (team agreed)
• Matt: FYI OpenBD and Railo both support CF 8 threading API, and BlueDragon 7.1 will as well

9:17

• Peter: discussing threading details, lower-level implementation details that we'll need to test

9:21

• Matt: better to leave threading separate for now (separate adapter for each engine - Railo, OpenBD/BD, Adobe CF)

9:43

• Peter: default behavior of timeout (for threading) is if it is not defined, it waits indefinitely
• Matt: confirms decision is to leave threading with separate adapters for now
• Matt: personalized threading adapters could be written for lower level stuff related to the number of "workers" that would be for threading for CFML engine; will discuss further for Mach-II 1.9

9:56

• Peter: copyToScope() is done, it just needs some cleanup ... but it works!
• Peter: discussing remaining tickets for the form tag library

10:01

• Matt, Peter: discussing form library tag names, options vs. !optionGroup, radios vs. !radioGroup. Spring uses "options", but doesn't have "radioGroup" tag. Grails has "radioGroup", but doesn't have "options" tag.

10:04

• Peter: pulling up Grails documentation to see how they implemented a few things

10:07

• Peter: update on his tickets
• Peter: (trac-wiki) #226 "defect: View-loaders Infrastructure improvements (closed: fixed)") view loaders improvements
• Peter: (trac-wiki) #252 "defect: Needed properties not available when needed by the framework when defined ... (closed: fixed)") setting default properties by environment property
• Peter: (trac-wiki) #214 "enhancement: Add support to message-subscribers for call-method (closed: fixed)") add support for call-method to method-subscribers, how should we do the syntax?
  • add "bean" attribute name to subscriber node to keep syntax similar with call-method

10:20

• Kurt: a couple extra tickets, about dynamically reloading changed components if config mode = 0, and one other...
• Peter: those tickets will need to be retargeted for 1.9
• Brian: logging property configuration enhancement ticket ... ran into research snag with supported attributes in various engines
• Matt: mentions getSupportedTags(), getSupportedFunctions() can be called in OpenBD, something similar in Railo, but out of the box doesn't include attributes for tags and functions, just the names
• Brian: suggests plugging in six key attributes: server, username, password, mailerid, charset, spoolenable, and leaving additional options for later release

10:32

• Kurt: timeline for Mach-II 1.8 - shooting for a Beta for cf.Objective() timeframe (the conference starts May 14th)

10:34

• Peter: We've tried to typically release on Mondays, why don't we shoot for Monday May 11th (team agreed and roadmap updated)

10:38

• Peter: for 1.9, I plugged in some "possible features". Packages, loading page on bootstrapper level, soft reference cache
• Peter: Packages potentially the biggest feature for 1.9
• Matt: we're doing a good job with relatively quick release cycles
• Peter (Matt confirms): future packages which are core to the framework should be bundled, but most packages would likely be separate downloads (i.e. Lyla Captcha)
• Peter: push for a RC1 for the dashboard soon, without adding any features until a later release
• Matt: reincarnation of the developers guide, slightly modified from original version, should be a nice resource for developers. Only headache will be redundancy between developer guide and core documentation. More than likely we'll want to keep the developer guide high level and link to the more detailed documents in the core wiki documentation
• Brian: takes on task of event-mapping documentation for wiki after Peter mentions it

11:00

• Peter: suggests formalizing Mach-II project manifesto, largely deriving from Matt's Mach-II History, Philosophy and Community blog post and the Debian social contract as models
• All: discuss importance of consistent well rounded flow of information through blog posts, twitter, regular back and forth communication with community

11:10p

• Meeting wrap up