On Friday 07 September 2001 18:28, Rodent of Unusual Size wrote:
> * On 2001-09-07 at 21:21,
>
> Ryan Bloom <[EMAIL PROTECTED]> excited the electrons to say:
> > On Friday 07 September 2001 17:46, Greg Stein wrote:
> > > Current consensus appears to be to add it to modules/experimental.
> >
> > I don't see how that could possibly be the consensus, since I have -1 in
> > the STATUS file.
>
> And I pointed out that I think the bases you quoted for your
> veto were specious if the module in question is in /experimental/. :-)
>
> Since several people seem to be in favour of putting it into
> experimental, I wonder how much effort is going to go into
> trying to get you to rescind your veto instead of into
> real work on 2.0.. :-D
I would hope none. I am incredibly unlikely to rescind my veto. I do not
believe that adding new functionality to the server is the way to get a release
out the door.
I also do not believe that we should be making this decision right now. I am
100% in agreement with Jim about this. We should table this whole discussion
until emotions have calmed, the patent issue has been finally resolved (Dirk
told me today that he knows of two patents, and he would post about them),
and Apache 2.0 has shipped.
Putting the module in experimental essentially means that at some point, we
expect to move it out of that directory. I do not know that is the case.
I would also point out that the consensus as I count it doesn't have this
going into the server at all right now. I am counting five people who have
said on list that they would rather this module didn't go into the server at
this point (although I am the only one to veto). I also count five who have
said they would like it to go into the server, either in filters or experimental.
That does not sound like any kind of consensus. My count is below.
Would prefer not: Ryan, Bill, Doug, Jim, Ben
Would prefer: Ken, Ian, Justin, Cliff, Greg
I may have missed one or two, but even if I did, that would not be a very
strong majority.
Ryan
______________________________________________________________
Ryan Bloom [EMAIL PROTECTED]
Covalent Technologies [EMAIL PROTECTED]
--------------------------------------------------------------
