Mach II Team Meeting September 29, 2009 - Mach-II/Mach-II-Framework GitHub Wiki

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

Time: Listed in Eastern time zone

Action Items Drawn from this Meeting

  • Kurt will tighten up preso's for BFusion

  • Brian will kick out one MachStart video per week

  • Matt will come up with case study questions

  • Peter will build an application form for people who would like to contribute to the framework

  • 10:06p

  • discussion of pre-conference training for cfObjective 2010

  • pre-conference Mach-II training will likely be offered at cfObjective, will be a killer deal, and will dig in on some key new framework features

  • 10:21p

  • discussion of BFusion/BFlex Mach-II training

  • Matt asks if anyone can put together (or update?) the powerpoint presos for the conference

  • Kurt takes on the task of updating the presos

  • Peter points out that he is multitasking by eating a loaded baked potato. Not to be outdone, Matt points out that he is polishing off a vegetable hash

  • Matt points out we should keep a narrow focus and dig deeper into a few key features (logging, caching, and view/form tag libraries)

  • 10:29p

  • Kurt notes that we should certainly point out to the list about the upcoming training opportunities

  • Peter has kind words about the beginnings of the MachStart video training series

  • Team discusses preparing a case study questionnaire to get some profiles from users from the community (using Mach-II and want to some great publicity? email team@…)

  • discussion of the many high profile sites making use of the Mach-II framework

  • 10:43p

  • discussion of possibility of new Mach-II team members

  • Matt and Peter discuss ways to build community involvement in the project

  • Matt points out having logical separation(s) within Team Mach-II will make a lot of sense for organizing the attack moving forward

  • Matt and Peter discuss the addition of a written agreement/expectation document for new members regarding formal expectations of contributions

  • purpose of document is not to pressure people, but to make sure everyone is on the same page to keep progress moving forward consistently

  • 11:04p

  • switching gears to vision for Mach-II moving forward

  • Matt talks about how we can make major strides and improvements in Mach-II moving forward

  • Kurt mentions the possibility of milestone releases and how they can help things moving forward smoothly

  • Peter concurs with milestones aiding with a frequent release cycle

  • Peter points out that the Mach-II vision encompasses both the technical aspect and community aspect which are both equally connected and important

  • Discussion of how to naturally make Mach-II more full-stack by nature

  • Peter talks about vision of a specific baked in ease of use feature to remove extra layer of configuration

  • 11:32p

  • Matt mentions that he and Peter have discussed the idea of bundling CFML engine in Mach-II package as an option

  • Peter points out big features for Mach-II he has in mind: Validation (i18n), (Major ease of use feature), (Big additional Feature for 2.0), View enhancements

  • Kurt talks about wicked feature planned for 2.0 and discusses his related research and planning

  • Peter brings up integration with Unit Testing framework such as mxunit

  • Matt points out that the unit testing integration may take a back seat to other upcoming features

-11:48p

  • Matt and Peter discuss the idea of leaving behind the strict lines keeping Mach-II out of your views and model
  • Brian and Kurt concur that this has been an unnecessary restriction which is holding Mach-II back from it's full potential
  • Peter asks for thoughts on feature targeting for 1.9 vs. 2.0
  • Matt suggests that keeping in line with our milestone release philosophy, we should probably look at including the Validation functionality in 1.9
  • Peter pointing out that 1.9 should include Validation and Packages

-12:02a

  • Meeting wrap up and finalization of action items (see above)
⚠️ **GitHub.com Fallback** ⚠️