> Jim J. wrote...
>
> People will not use it unless they can *really* trust a module. Simply
> expecting people to migrate to it because of the theoretical > benefits isn't quite wise, until it has proven itself. The idea is > to make it easier for people to have access to a module, use it > and test it. More exposure means more feedback and more bug-fixes > (hopefully :) ). But simply "being there" isn't enough to > expect world-wide usage, but "being there" is enough to hope > that people have easier access to play around with it. Well said, Jim.
The experimental modules section of the general release has
always been the 'enticing' part of the tarball and the "You can
play too" advertisement. It is the constant reminder that Apache
had never been, is not now, and will never be FINISHED.
You need to keep everything you've got to prevent the trend of
the last few years to keep from "closing in" and losing your
ability to attract new talent into your developer pool.
Yours
Kevin Kiley
|
- Re: Issues for 2.1.8 William A. Rowe, Jr.
- Re: Issues for 2.1.8 Colm MacCarthaigh
- Re: Issues for 2.1.8 r . pluem
- Re: Issues for 2.1.8 Jim Jagielski
- Re: Issues for 2.1.8 William A. Rowe, Jr.
- Re: Issues for 2.1.8 Mads Toftum
- Re: Issues for 2.1.8 William A. Rowe, Jr.
- Re: Issues for 2.1.8 Colm MacCarthaigh
- Re: Issues for 2.1.8 Brad Nicholes
- Re: Issues for 2.1.8 Jim Jagielski
- Re: Issues for 2.1.8 TOKILEY
- Re: Issues for 2.1.8 Jim Jagielski
- Re: Issues for 2.1.8 Jim Jagielski
- Re: Issues for 2.1.8 William A. Rowe, Jr.
- Re: Issues for 2.1.8 Jim Jagielski
- Re: Issues for 2.1.8 TOKILEY