how open is drizzle?

one piece of jay’s advice to mysql got me thinking about something that bugs me about drizzle development. jay said:

Make all decisions open and transparent: For the non-maintenance team, make a policy that all decisions about the kernel design be done in an open forum, with the community able to participate in the discussion. Have stewards that are willing to negotiate the design decisions with the community and do everything in a transparent manner.

since jay is one of the key lieutenants in the drizzle effort, it only seems to fair to put them up against that standard. one thing i have noticed is that there is relatively little discussion on the drizzle mailing list about all the coding that is going on. the latest discussions mostly seem to be flypaper for standards wonkery and taking shots at mysql.

meanwhile, you have big refactorings of code like mark atwood’s plugin-ization of several features that seem to just go into the code without any discussion of the design or implementation.

maybe all the discussion is happening on the irc channel, but that is not a great way to get much of the potential community involved. how much of it is happening off-line? maybe more than the core drizzle developers realize, or would care to admit.

« wonton at rest december 23, 2008 12:55am »