On 2005.02.07, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
>
> I still do believe that there should be a path/vision established
> which will then justify acceptance or rejection of future ideas or
> ideas already sitting in the RFE queue.

Okay, this is good.  So, how do we define the vision?  I'm in favor of
it being a shared vision between all the constituents of the AOLserver
Community, which was my rationale behind the Steering Committee concept.
Individuals from the community speak on behalf of users they represent
and express what their needs are.  Someone (most likely me) will collate
all of these needs into a cohesive vision which will guide the direction
of the project.

I've already received some feedback privately from people regarding the
steering committee.  I'll give everyone some time to formulate their
statements of position on various aspects of AOLserver and to send them
to me.  Lets make the deadline for submissions Monday, 28 Feb 2005.  I
will aim to have an initial draft of the project vision/plan done by
Wednesday, 16 Mar 2005.

To be clear about this, I am not simply going to collate everyone's
responses together.  I will be looking for common themes amongst all the
responses so that the most people benefit from the improvements that we
make in 2005.  If something you expressed interest in doesn't make it
into the first plan, it's because there wasn't enough interest or
support for that particular aspect.  I will do my best to be fair and
impartial about this.

I also want to remind folks that simply stating a desire for a feature
doesn't put much weight on it.  Describing how the feature would fit
into a real application that you are either building and/or will build
gives it more weight.  This prevents people from "asking for the moon"
and better serves those who are building products which rely on
AOLserver as an underlying technology in the stack.

> And current AS users is what this project has now. Instead of getting
> new ones in, how about activating already present people (there are
> quite a few of them listed in SF as developers)?

This is why I created the different Project Teams.  I'm hoping more
people commit to signing up to the various project teams and actively
participate.

> What I appreciate about AS is its stability, Tcl integration level
> and infrastructure allowing me to write concurrent applications
> with ease. The AS speaking the http protocol is nice, but not the
> main reason why I'm using it.

What is the main reason why you use AOLserver?

Perhaps it would be useful for everyone who uses AOLserver to write a
single sentence or single paragraph that starts out with "I use
AOLserver because ..."

    I use AOLserver because it is free, open source, uses Tcl as its
    scripting language which I enjoy, performs well, is easy for me to
    extend through writing my own Tcl and C code, makes it easy for me
    to write code that connects to popular RDBMS'es, and is easy for me
    to configure.


I'd like to see how other people complete this sentence.  As usual, to
this list or directly to me.

-- Dossy

--
Dossy Shiobara                       mail: [EMAIL PROTECTED]
Panoptic Computer Network             web: http://www.panoptic.com/
  "He realized the fastest way to change is to laugh at your own
    folly -- then you can let go and quickly move on." (p. 70)


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