There may be strategic reasons why AOL does not want to add value to
AOLserver outside of existing functionality. For instance, new
functionality may compete with AOL technology that has not been
released. AOL could be at a disadvantage if it has to re-write other
existing code to work with a significantly different AOLserver
implementation, where new competition would not have that cost burden if
starting with a fresh version of AOLserver. That does not stop a
competitor from implementing entirely different (and newer) code, not
based on AOLserver.

Perhaps the way to reconcile this is to have two opensource AOLserver
versions. One version meets the current project requirements (including
AOL's internal ones).

The other version has less restrictive requirements, thereby fostering
the creativity and implementaton requirements of others in the community
as technology (and it's uses) evolve.  This alternate version would be
in AOL's strategic interests for technology innovation and advancing the
AOLserver platform. AOL could add parts of this version to the other
version as it sees fit.

Maybe make even numbered versions according to the strict AOL
requirements, and odd numbered versions to the "relaxed" version?

Torben

Dossy wrote:

Spend some time thinking about it, and when you have a better idea of what that "something" actually is, tell us all about it. We're all listening.

Vlad Seryakov wrote:


In my case "something" is: i feel that contributing into AOLServer
project feels like asking permission from AOL, is AOL willing to accept
or even consider whatever additions i am offering. In most case they
will be rejected because of stability, direction, code style or pure
"messed up code". I understand that AOL pays core developers but i think
this is what makes me feel this is not open-source project, this is AOL
project with open sources. It is not bad and AOL benefits from this
greatly, so many free QA/testers but still, AOLserver goes in the
direction at least i do not agree with.
I think AOLServer should not be pure webserver, just another webserver
even running by AOL, still just another webserver, it has potential to
be full-blown application server.

I support my patches and develop different version of aolserver,
allowing differnet protocols, for example HTTP or SIP over UDP, but i am
sure AOL will not accept them, so i keep them to myself. There are many
small improvements can be done and i 've done a lot of them, binder for
example, many modules. They are public but still, core is what AOL
provides.

I am not saying the word "fork", but it may happen.


If you're being intentionally vague about what "something" is, and
"something" refers to me and my leadership of this project, then please
just say so.


You are great project leader, no doubt, you just work for AOL, it is
very noticable.




--
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.

Reply via email to