Martin Cooper wrote:
I honestly don't see that we could point at some other project outside the
ASF and say that we "endorse" the plugins produced by that project when what
we are really saying is that we don't consider those plugins to be
sufficiently worthy to live at the ASF.
I suppose that's one interpretation. I'd see it more like
struts.sourceforge.net though... it's just an external location where
things can live and develop. Maybe saying it's "endorsed" does go too
far, but just pointing it out and saying "there's some plugins that may
or may not eventually make it into the mainline distribution", wouldn't
that be OK? I mean, I haven't looked in a while, but I recall there
being a link to struts.sourceforge.net on the main Struts site... does
that qualify as an endorsement? I wouldn't think so, but maybe I'm
wrong there.
> Plus, I personally would have a
pretty fundamental problem with "endorsing" any one specific project outside
the ASF in preference to any other.
I would too from the perspective of Struts as a project endorsing
something, no question. But I think it's a question of semantics:
calling something a project carries certain connotations, so maybe
that's the wrong word to use... Repository? Registry? Catalog? I
don't think these carry the same connotations, but all could equally
describe such an external entity.
> I suspect we could get into legal trouble over that sort of thing.
You may be right about that, my Bar card hasn't arrived yet so I can't
say ;)
--
Martin Cooper
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
