On Fri, 3 May 2002, Geir Magnusson Jr. wrote:
> > I'm also very unhappy with the xml/jakarta separation and
> > the balkanisation of apache - as well shown by the current
> > maven/forest/cocoon/centipede discussion, where even xml.apache.org
> > is affected by jakarta's NIH.
> >
> > So I'll be -1 ( as a jakarta commiter - my vote obviously
> > doesn't count for that ) on another apache.org fragmentation.
>
> Really? The point, as I see it, is simply to help organize the greater
> Apache community by subject of interest.
>
> Stretching your argument to an absurd conclusion, if we eliminated all
> general@*.apache.org and made a single [EMAIL PROTECTED] list, it would
> quickly become useless as people perceive "noise" differently.
>
> People have different interests. I am sure that there are httpd people that
> are interested in what's going on in Jakarta, but not *all* of them.... I
> personally adore some of the projects in XML-land, but don't want to be a
> part of their general@ list...
>
I'm with Costin on this one, I think, [though I count myself as someone
who is stilling learning to be an apache person]. Catching up with the
thread, the suggestions seem to have been:
1) OJB joins Jakarta. I say: Yes. OJB has long been on my list of "this is
very cool and good" and having it in Jakarta would be great.
2) OJB becomes a Jakarta sub-project. Again, Yes.
3) OJB be used as a nucleus of DB-Commons, some kind of Jakarta subproject
specialising in Databases [but still Java]. I'm not convinced here at all.
If OJB had begun at Jakarta I would imagine it would have been a sandbox
component in Commons or Avalon or somesuch, and would have followed
Latka's route. It would now be a full on Jakarta sub-project.
Existing projects with a large enough scope might want to consider reusing
OJB instead of their own. ie) Should dbtags taglib involve some kind of
ojb specific bits? Or do we just need an ojb taglib.
If ojb does have a taglib, do they go into the Taglib project?
OJB must have common components. Bet they have a String utlity. Should OJB
be dependent on Commons? [or Excalibur etc].
4) OJB as the nucleus of db.apache.org. Some kind of database focused new
top level project at Apache:
No no no. Ick. Ack. etc.
What will the plan for db.apache.org be?? When will dbtags move to it.
When will my rebol source code for accessing mysql go into it, when will
we add DBVisualiser to it.
Basically coming down to, what are top level Apache projects. Mainly they
seem to be language based [except the flagship webserver, which seems
really to be 'C' than 'Webserver']. XML does have some issues, but that's
due to the language not the project.
I'm +1 on OJB joining.
+1 on Jakarta.OJB.
-1 on Jakarta.DB-Commons unless otherwise convinced.
-1 on db.apache.org, unless people start offering bribes.
For what it's worth :)
Hen
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
