On 17 Feb 2003 17:40, Richard Levitte - VMS Whacker wrote: > I intend to make development of CTWM much more a community kind of > thing, with whoever having wrote access to CVS having last say. > Therefore, there will be more development-oriented conversation going > on (or so I hope). For now, it's rather been me having a monologue, > mostly in form of mails generated by the request tracker, and I've > noticed that some people have chosen to leave this list shortly after. > > All this makes me think a split is in order, with this list being more > of a user-oriented list where all kinds of non-development questions > can be asked and answered by whoever wishes to do so, and a new list > called (say) ctwm-dev, where the development-oriented discussions can > happen without disturbing those who aren't interested. > > I'd like to hear your input on this.
If having two lists will help, then by all means, lets have two. But judging by the level of activity during the last year or two, I'd say the reason people dropped off the list probably more was due to discovering that a list long forgotten still existed. In my mind, merging all pending patches, testing the resulting CTWM and releasing a new version is priority one. I had almost given up on CTWM myself when 3.6 finally was released, but I was actually pretty disappointed with that release since it only merged a couple of the many patches flowing around. I would very much like to be able to send people a pointer to a CTWM archive without also giving them a list of patches they should apply. Also, releasing a new version may spark some new interest in the project, both from old users and potential new ones. (Although I think CTWM probably is a pretty hard sell to newcomers.) /Bj�rn
