All,
 
For the time being, the list will continue to operate as a single mailing list ... there will be an influx of newcomers to the technology, but we are well placed to handle this.  We have an FAQ and we have a strong and talented community of list members able to provide answers to questions.  As we begin to receive new questions, we must be careful to ensure that when questions indicate a lack of resourcefulness on the part of the poster ("how do I set a margin on an hbox") that we don't provide answers, but tell them how to go and find the answers.  With that policy in place, we've managed to keep the signal high, and the noise low on this list.
 
There will always be people that think the list should be forums, or multiple lists, or wikis, or whatever else .... but the simple fact is that the mailing list works for those that use it most; questions are pushed to our inbox, we can quickly scan them, mark the ones we think we can help with for followup, and respond as quickly as possible. 
 
In the first instance, I'd rather we not fragment the list, have the knowledge compartmentalised and suffer from people cross-posting to multiple lists to try and get questions answered.  Let's stick with one list, roll with the punches, and see how we get on.   Let's not do a "big up-front refactoring" :) of the list unless it's evident that it's required; and if that does become the case, the problems will have presented themselves and the solutions will be self-evident.
 
I may be optimistic, but I hope that careful moderation of the list, to ensure that we keep up a high-quality of relevant posts, will be sufficient to accomodate the anticipated growth of the mailing list.
 
Now; i've got 1600 flexcoders emails to read through since MAX.....
 
Steven
--

Steven Webster
RIA Practice Director (EMEA)

Macromedia Consulting



--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




YAHOO! GROUPS LINKS




Reply via email to