Here's how Drizzle development works (based on true events): At first, someone thought "I want to make MySQL better." That idea was spread. Anyone thinking "Drizzle should do X" can make a blueprint for it. Anyone who wants to develop for Drizzle can do what they want, or use a blueprint as their guide for "what should I code?"
Here's how Drizzle advocacy works (based on true events): At first, someone thought "there should be documentation" and put something up at http://drizzle.wikia.com Then, someone thought "there should be a drizzle website" and put something up at http://drizzleproject.org/ Then, someone thought "there really ought to be a blog aggregation for Drizzle blogs" and put something up at http://planetdrizzle.org/ Then, someone thought "Drizzle stuff should really be on http://www.drizzle.org"; and bought it. Forums vs. listservs vs. websites vs. wikis vs. whatever are all relative to what people will use. So put up whatever you want, and if it's not working well you'll know because nobody will post/subscribe/comment/edit/whatever. It's great to solicit ideas and feedback, but what happens is someone says "do you think *this* is a good idea?" and someone else says "well, *that* would be better than *this*". And then it devolves into lots of people talking and nobody doing. So sure. Someone wants a forum, put it up. Someone wants a Google-maps API based conference locator, even better. I suspect that there won't be more than, say, 10 conferences per month featuring Drizzle speakers, so that might be overkill, and text with HTML links might be a better solution. But maybe someone really wants to code that Google-maps API-based conference locator, and has the time, so I say: Bully for you! Have fun. As someone who has volunteered since she was 14, the worst thing you can do is discourage a volunteer. I don't think any of the ideas I've seen about websites in the past few days is a harmful idea. I think some might work better than others, but that doesn't change the fact that having a forum that doesn't get a lot of traffic won't kill Drizzle as a good project. Because there are a few different places for Drizzle, and because part of the feedback is "I don't want to step on toes", my suggestion is this: drizzle.org should be the same as drizzleproject.org -- both were acquired with the intention to be "the website" for Drizzle. If there are 5 different people with 5 different ideas (wiki, forums, whatever) then give those 5 people access to the website, and let them do what they want. One person installs a wiki and manages it. Another is in charge of forums. Another codes the Google-maps based API conference locator. These ideas aren't mutually exclusive, and there is no consensus required. So let's *do*, instead of talking it to death. (talking is a good thing, but check out the types of things the developers are discussing, and how many items come down to consensus vs. how many items are patched and merged.) (now, it's not fair of me to say this, because I own neither domain. However, I think it's in everyone's best interest to use the offer of free bandwidth and shell accounts for the website that I offered previously from Technocation, and then everyone can just do whatever and not feel like they have to get consensus. ;) ) -- - Sheeri K. Cabral
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
