Re: Public Development of Amaya

Hello Ewan,
 
In our previous episode, E.E. Mellor said:
> 
> Is it intended that Amaya (and by extension, Thot) is to be developed
> publicly - i.e. by those not of the core (W3C) team?  I have found no
> statement on development strategy on w3.org.
 
You're right. We don't have such statement yet, but one of our goals for
this year is to open up our CVS base.
 
Up to now, only the core W3C team has read/write access to the Amaya 
CVS base.  Whenever we get contributions, we evaluate and integrate them
ourselves. Indirect contributions make their way inside Amaya by means
of the libraries (e.g., libwww, jpeg, png, ...) which Amaya uses.

> I have yet to find a low-cost graphical browser available for Linux that
> I consider satisfactory in use.  However, Amaya is the closest I have come
> to that and I am willing to spend time on Amaya's development to bring it
> up to scratch.
 
Sounds good. What is your wish list of things to improve?
 
I'd suggest you try to coordinate with the Amaya team to avoid the
duplication of work. Feel free to contact any of us.
 
> Whether or not Amaya is to be openly developed, anonymous CVS (or similar)
> access to the Amaya source would be useful.  This would allow
> incremental source downloads, reducing download cost and load on your
> server.  Is such access available?
 
We're starting work on opening our Amaya CVS base to the public.
In a first time, it'll have world read-only access. This should take place
in one or two months. Depending on the response and on the quality of
contributions, we may open a write access to other people afterwards.
 
Cheers,
 
-Jose

Received on Tuesday, 12 January 1999 04:25:27 UTC