SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-22-2008, 12:17 PM
| ||||
| ||||
 Re: openhttpd? -> opennntpd On 4/1/06, Steffen Wendzel <cdp_xe@gmx.net> wrote: > how about an openNNTPd? INNd is a monster and hard to configure. Have the INN maintainers refused your patch to fix that? Is the INN license unacceptable in some fashion and have the maintainers refused to address that? Have your attempts to secure, fix, or enhance the INN code base been hindered by poor design and direction and the maintainers have been unwilling to accept patches to fix those defects? If the answer to all three of those is "no" or "I haven't tried that", then what's to be gained *by the OpenBSD team* in forking the code base (ala OpenSSH and the httpd in OpenBSD) or creating a new one (ala OpenBGPd)? (Why do many people act like creating a new OpenFOO is a weekend hack with no _continuing_ costs? I'm not involved in any of them but it's obvious to me from the open source maintainence I did in the past that these things require a *lot* of _sustaining_ effort by developers and that it's only their continual interest the code that matters.) Philip Guenther      |
 |
« Re: Suggested replacement of ap_snprintf with the native alternative snprintf with error check == Patch attached ==
|
Re: openhttpd? -> opennntpd »
| Thread Tools | |
| Display Modes | |
Linear Mode
|
|
All times are GMT. The time now is 05:23 AM.
