Multiple lists enforce thinking if it is appropriate before posting. Moderators can ban/redirect unappropriate message. Flexcomponents often redirect new users to flexcoders if the question is not about components. You almost never see questions on UI design in weborb.
All in all - let us have the simplest thing possible - multiple list - we will see how people position themselves, and which parts of flex are actually position to grow. In old moderated world of CompuServe product of Flex scope would have 15-20 lists and that would give very concise picture of the product feature, median developer level, much faster/easier search and better networking. Thank you, Anatole Tartakovsky Farata On Tue, Jun 17, 2008 at 11:20 AM, Doug McCune <[EMAIL PROTECTED]> wrote: > > > How about an agreed list of acronyms that we use to prepend the Subject > line with: NEWB, MXML, AS3, DESIGN, HTTP, ALL, etc., and we do the sorting > ourselves with the mail rules? > > > > > You can't force people to add keywords to their subjects (I'd also argues > that any categories you come up with are inherently flawed and topics > usually apply to many categories), since people unfamiliar with the list > won't do it, and the biggest problem I see has to do with people new to Flex > and this list (note that I highly support new developers getting involved > and asking questions, but they should do a little research first and not ask > someone to do their work for them). If people start tagging their subjects > it might catch on and people might be smart enough to see the traffic on the > list and adhere to the standard before posting, but I give it a very small > chance. > > And if someone replied and changed the subject line then threading gets all > jacked, which is why I suggested someone replying with a certain tag in the > body of the message that we can use to filter the threads (not to categorize > legit threads, simply to filter out illegitimate ones). > > Doug > > >
