On Tuesday 08 April 2008 13:52, Rick Cobb wrote: > Well, it's certainly compliant :-), but I suspect Mr. Jackson would object. > If there's one thing aolserver ain't, it's "beta".
Well, at least he has a goal to achieve, and once we attract 'people' who are interested in developing beta grade software, we will surely get there very quickly. A cute logo isn't going to attract the level of developer who would be able to maintain AOLserver, much less provide a useful enhancement. But like I said: why not figure out what needs to be done...first. IMHO, by advertising the stability of the AOLserver API, you will attract users who would otherwise be correctly scared off by constant hacking. Another thing which might attract interest is if our current community members would write a brief application note explaining how they use AOLserver, and why they chose it over other potential platforms. Additionally, we could catalog sites known to run on AOLserver. My guess is that developers who have similar interests and motivations or similar problem solving skills as current community members will be attracted to the community. Given the fact that there have been only a handfull of CVS commits in the last year, I would venture to guess that most community members are happy with the current codebase, and that means that new community members will probably be looking for a mature project which allows them to focus on their own application, at least at first. Then, they may contribute a module which extends AOLserver. A quick look at all the modules in CVS suggests that this is the best way to contribute code, not by hacking on the core. Change for the sake of change will scare off any sane developer, we don't charge for upgrades, please remember this fact. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
