http://www.netcraft.com/survey/
This says Apache is bigger than MS + all others.
.V

Andrew C. Oliver wrote:
Those who have not been aware should be aware.

-Andy


------------------------------------------------------------------------

Subject:
Re: Concern about the future of Apache.
From:
[EMAIL PROTECTED]
Date:
Thu, 17 Oct 2002 12:16:55 -0400 (EDT)
To:
[EMAIL PROTECTED]


On 17 Oct 2002, Andrew C. Oliver wrote:


On Thu, 2002-10-17 at 11:42, [EMAIL PROTECTED] wrote:

On 17 Oct 2002, Andrew C. Oliver wrote:


I don't object so much as I think the reorg is missing some obvious
issues: for instance jakarta and XML are very different communities. Technology isn't very important. Now maybe some know better than I,
maybe they are different because they are separate, but to me it looks
like they are separate because they are different.
Nobody is suggesting merging Jakarta and XML.  We are suggesting unifying
the way the ASF is structured.  If it makes sense to have a few top-level
projects with lots of subprojects, then lets do that.  If it makes more
sense to have lots of individual projects, then lets do that.  When we
need to stop doing, is having some projects that are one code base, and
some with lots of sub-projects.

Why?

Because it is very confusing for new people as things are today, and it is
confusing for people who have been here for a while.  We have already seen
on this list that the differences between how APR/HTTPd members approach
things and how Jakarta members approach things is huge.  That makes
communication between the teams harder, which makes collaboration harder.

It also makes it harder to add new projects, where do they belong?  Inside
an existing project, or as their own top-level project?  Finally, there is
the issue of oversight.  There needs to be some, because that is what is
legally required of us as a non-profit.  The way things are today, there
is no real oversight.


We also need to decide how we are going to organize projects.  We can
organize by language, by feature, or with an very flat structure where
projects are then categorized (but they can belong to many categories).
why don't you just create a web page which does that if its important to
you?

I don't see that as requiring a reorganization really.

You are making an assumption that it isn't valid to make.  You are
assuming that the end results of this list will be a massive
re-organization.  I have said from the beginning that the end results may
be a statement "All is well in the ASF".  However, there enough people
have stood up and expressed concern that the issues needed to be look
at.  If we decide that a web page is all that is needed to solve the
problems, then cool.  However, that must be a group decision.  Currently,
it looks like the ASF is leaning more torwards moving projects around and
removing the huge top-level projects.  At least that is how I read the
messages on the list.

Ryan
_______________________________________________________________________________
Ryan Bloom                        	[EMAIL PROTECTED]
550 Jean St
Oakland CA 94610
-------------------------------------------------------------------------------




------------------------------------------------------------------------

--
To unsubscribe, e-mail:   <mailto:general-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:general-help@;jakarta.apache.org>



--
To unsubscribe, e-mail:   <mailto:general-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:general-help@;jakarta.apache.org>

Reply via email to