A couple of other reasons to supplement Danny's reply:
-- Because they're easy to use at one level, and they're the lowest common
denominator. Everyone (well, nearly) has an email account, and can read
and respond to mailing lists. We have some contributors who still live
over part-time
[EMAIL PROTECTED] wrote
I will try to make this last message on the topic of ethics, its up
to
the people sitting on the hands to see this is as a problem and do
something.
Well, I've been sitting on my hands realy hard trying not to jump
in with a witty and sarcastic reply
Hmmm. A couple of comments.
Have folks here read http://www.apache.org/foundation/bylaws.html yet?
If not, you really need to (well, skim it, plus the opening paras on
the /foundation/ page).
The ASF (Apache Software Foundation) is an 'official' non-profit
corporation under Delaware, US laws.
As already noted, several of the FAQ documents include links to copies
of the license. Plus the fact that virtually all Apache projects
include a LICENSE or the like file in an obvious place inside the
project (which you presumably downloaded to see if you wanted to use
it) as well as the fact
Sorry for my tangent - it's clear that on legal matters, I should just
get the heck outta Dodge and let someone with more patience work on it.
8-{
I've forwarded a link (with threading) to your (Conor's) message to the
xml PMC so they should be aware of this licensing issue with JAXP and
Great! I'll keep an eye out so we can propose stealing what you come
up with for xml.apache.org as well... 8-)
Suggestions/comments/questions:
-- Focus on overall how-to steps for the release process and signing
'public' distribution units; I can volunteer to do QA on any
instructions you come
