Re: Jakarta Alexandria and Gump; what should be done?

[Nicola Ken Barozzi <ni...@apache.org>]

Following this mail, I have cleaned the alexandria repository of the 
tests I have been doing for a new Gump codebase with Alexandria integrated.

It has been quite clear that the current Gump codebase is ok and 
indipendent from the Alexandria code, and most important, mission.
The merger didn't look nice and looked really like a hack.

Thus I have clearly separated the two again:

  * moved all new Gump related code to the
    proposal/gump hierarchy
    (proposal/gump/scratchpad/viprom and proposal/gump/editor)

  * removed the code that's already in proposal/gump from the
    main alexandria CVS dir

  * removed the javasrc code till license issues are resolved

  * added the sources of a new Alexandria site to the Alexandria CVS

In this way, all Gump code is in proposal/gump and the main alexandria 
module space is basically a clean slate.

If active Gump committers want to propose Gump as an indipendent effort 
(top-level or under Jakarta), the codebase is ready for the move.
I stand with what they will propose.

As for Alexandria proper, in these days I will

  * update the Alexandria site with the new version,
    and a link to the old one
  * poll the javasrc and xsldoc authors to send us a
    written grant for the code, and keep the jakarta pmc informed
    of the proceedings

When license issues are resolved, I'll start publicizing Alexandria to 
all the projects and people that have shown interest, and have them 
involved.

Finally, I would like to thank all who have given me feedback and help 
on this issue, and hope that it will soon come to a happy and positive 
ending :-)

Nicola Ken Barozzi wrote:
> 
> 
> Stefan Bodewig wrote:
> 
>> On Thu, 7 Nov 2002, Greg Stein <gs...@lyra.org> wrote:
>>
>>> On Thu, Nov 07, 2002 at 09:49:01AM +0100, Nicola Ken Barozzi wrote:
>>
>>
>>
>>>> I would like to see a jakarta-gump CVS module, a gump-dev mailing
>>>> list, the site is already there.
>>>
>>>
>>> This is a job for the Jakarta PMC. They should handle the reorg
>>> between Alexandria and Gump so that you can get your space cleared
>>> out.
>>>
>>> I've CC'd the PMC to deal with this.
>>
>>
>>
>> Actually I think Nicola Ken should propose to move Gump out of
>> Alexandria on alexandria-dev so the committers can decide.
> 
> 
> I reaised this point already.
> 
> http://marc.theaimsgroup.com/?l=alexandria-dev&m=103556892030865&w=2
> 
> No reply (yet), hence my asking for suggestions to my incubator friends.
> 
> I also proposed this to general@jakarta.apache.org some time back, but 
> it had no result.
> 
> http://marc.theaimsgroup.com/?l=jakarta-general&m=102028908729985&w=2
> 
> I'm not a long-time committer, and my involvement is quite recent; I 
> don't think I can really push it too much, and I felt this is the most I 
> should/could do.
> 
>> To me (maybe just to me) Alexandria itself looks like a candidate for
>> the graveyard.  If
>>
>>
>>>> The Alexadria mission itself has programmers that want to work on
>>>> it to reignite the community; where should it be done?
>>>
>  >
> 
>> is true, doing that on alexandria-dev seems the logical choice.
> 
> 
> It's logical, although some thought it would be a case for 
> (re)incubation, and I wondered  if it was really the case.
> 
> Since incubator is new, it's best not to overload it, so I'll not think 
> about putting Alexandria in the incubator, and work over there.
> 
> Is this ok?
> 

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>