re This List

The board members should have a discussion on how this group is to function technically (perhaps moderated IRC), however the list should continue to function as an open discussion forum on PHP standards. It's bizarre that such illustrious members of the PHP community are essentially advocating measures *against* the community. Leave the list open, have a meeting on procedure (post the minutes) and above all engage in Productive discussion. On that note, another poster interested me with his call to have procedural programming standardised. If phpBB, drupal, OSC would engage in such a process it would be of great benefit to the developers using the software. Despite the lack of more academic and structured design in these projects having some input from them would be a Good Thing. A two-part approach to this standard is something to consider. It seems people are viewing this two different ways: as "something to conform to" or "a guide". Guides issue recommendations and use "may" (etc.) where as one conforms to "musts". You wouldn't be conforming to strict xhtml if you had an unclosed image tag, this isn't something you "may" do. Particulars of implementation (such as autoloaders) should perhaps be requirements of conformity whereas certain aspects of application design may fall under a "recommendations" section. A clarification on the breadth of this standard should also be provided, is this going to concern things such as a standardised MVC implementation... or perhaps a "recommended" implementation. I would quite like to see some examples of certain patterns included with this as "recommended" or "example implementations"... but that is just me... perhaps it's too much to require and falls outside the scope of this standard (though it would seem the board is free to extend the scope as it likes). Michael