Yaws API discussion

[Eric Merritt]

Mickaels ideas below are a great idea. A question
arises though, Is the owner (klacke) willing to allow
this? 

It seems that at the moment yaws is very much a single
owner/maintainer project. After spending a little time
looking over yaws.hyber.org it seems that there is no
way to submit code, get cvs images, no mailing list,
etc. 

It may very well be that the owner is not interested
in expanding the project. 

Does anyone have any idea on this?

Thanks,
Eric

> For the rest, I tend to think that Open Source is
> about improving the tool that
> fit best your need at a given moment of time.
> What worries me is energy dispersion. Here is the
> list of Erlang HTTP server
> that I know of:
> - Inets 2
> - Inets 3
> - Pico
> - Yaws
> - possibly your incoming HTTP Server, Chris
> 
> So the main question is why develop another one ?
> Really ? You can choose one of
> those servers as a basis of improvement. And writing
> another HTTP server, does
> not allow place for other cool improvement in the
> feature of those servers (like
> cool templating system, MVC approach modules, etc)
> 
> It would be cool to see an important Open Source
> Erlang project emerge as a
> collaborative work of many Erlang developpers, but
> this would probably not
> happen if we always rewrite everything when we need
> a piece of code (Even if
> this is easy in Erlang).




__________________________________________________
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
http://autos.yahoo.com