Yeah, long threads are a problem, mainly I think due to yahoo's stupid table-based ads they throw in.
I don't really think a FAQ will help in that people will read it before they post, but it will help in making it real quick to answer questions that are common (but asked politely). The search function of the list isn't great, and it seems to be archived in several places making searching it from google kinda manky sometimes. I've been on it a while now so I can search my own archive with gmail, and I can often find an answer that way. Frankly I agree the list doesn't need splitting. But a nice FAQ from which we can post links to people who ask reasonable yet common questions would probably be a good thing. People appreciate getting an answer, and they also know to check there first the *second* time they have a question. -Josh On Tue, Jun 17, 2008 at 9:28 PM, Michael Schmalle <[EMAIL PROTECTED]> wrote: > Josh, > > Threads that get over 30 seem to get muddled. You talking to me? > > My opinion is splitting up this list won't help. Why do I know this? In my > previous post, flexcomponents list is a ghost town, why, devs will ask on > flexcoders because that is 'where we ask'. > > I was part of the group (professional component developers) back in 2006 > that got flexcomponents list created, I am actually a moderator on that > list. But, people don't read. Putting up a FAQ or sending it to people won't > help because people don't read! :) > > These ridiculous questions mainly are because people don't read manuals > like the veterans did (when we were "inspired"). > > Once you get a technology stable like flex and we are out of the betas > (2006), it becomes a 'get it done and make money'. The people that answer > questions are the ones that read the manual. > > Anyway, this is it for me. :) > > Mike > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
