> >Ah. We currently have a user pool that is almost not growing.
> >Little new users will probably mean little new active ones
> >as well.
> >
> >Many of the people in that pool work for companies that would
> >allow them to work on Avalon in company time as soon as that
> >company would start using Avalon - which does not happen
> >because there is nothing solid enough for them to use. See?
>
> perhaps but there is little we can do till we reach critical mass. Besides
> Avalon and it's ilk is inherently unsexy and fairly demanding - so even if
> it increases usage by many times it will only see a small increase in
> active developers ;( Have a look at other generic frameworks in OSS land -
> they all have similar fates.
We'll *never* reach critical mass unless we have a firm beta date towards which we are
aiming.
There are loads of companies/oss-projs out there not using avalon becase they don't
know when it
is going live. I could not hand-on-heart say this year to anyone that asks me. I am
*desperate*
for OSS and work related reasons to see Avalon stabilise and go live at a certain
point. If it
changes after that (package/class names, implementations) I will accomodate those
changes as I
port from one version to another.
Also, I'll bet you we lost subscribers to the mail lists when we switched from
java.apache.org to
jakarta.apache.org as we're now spammed by CVS messages in the *same* list.
Proposal 1) June 15th : Switch to beta
Proposal 2) Formal release : August 1st
Refactor as much as desired up to (1).
Regards,
- Paul H
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
