Berin Loritsch wrote:
> Andrew C. Oliver wrote:
>
>>>
>>> Translation:
>>>
>>> Jakarta = jakarta.apache.org
>>> XML = xml.apache.org
>>>
>>> And the reason on XML.apache.org there is no discussion is:
>>> everyone seems to be on board with Forrest--which is using Centipede.
>>>
>>>
>>
>> Yeah so why can't these work together? I still just don't get it.
>> "Gee we don't like that lets do our own thing or integrate with
>> anything but this or that". It just baffles the crap out of me. If I
>> had the choice. I'd use NEITHER. I choose Centaven WITH GUMP.
>
>
>
> Fine. The history is that Forrest was in motion before I even knew
> there was such a thing as Maven. I know the folks involved with
> Forrest, and they are top notch people. The whole purpose of Forrest
> is to work with GUMP. (Notice the synergy: Forrest Gump).
>
> Forrest was started and talked about publicly on the general@xml
> list before it was even started. That is something that somewhat
> perturbs me about the Turbine projects. SOmething with Maven's
> scope and ability should have been talked about publicly instead of
> sneaking up on us. When we get the message "convert all your
> projects...", that would definitely catch alot of people off guard.
>
>
I am interested is most of Jakarta-land, and in most of xml-land (the
*instanceof* java part).
I'm wondering if cross-communication lists would be needed. Since there
are plenty of communities in Apache, the general lists are too general
for me most of the time.
Since the java.apache.org project was frozen a lot of time ago, we could
reuse the name to create a [EMAIL PROTECTED] list, or some similar
cross-project structure to ease java development communications.
The main points I see are:
- xml is becoming fairly used everywhere, so that most of us are related
to it somehow (specially as power-users or plain-users of the
java-related tools)
- a significant part of Jakarta is devoted to project infrastructure
(build, test, document, ...)
- infrastructure thingies springin in xml are being sent outside instead
of being developed there.
Java server is a big box to organize things, and XML is potentially even
bigger, so I think some organizational thinking should be (is already?)
going on. Also, one year and a half without an ApacheCon synchronization
points does not help much.
I'm not entering here to pick up flames, just looking for constructive
solutions.
Regards,
Santiago
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
