Berin Loritsch wrote:
I disagree.From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Sam Ruby
Berin Loritsch wrote:
People who have not been working on Phoenix really don't know whatThe reason why Avalon became a separate project was due to a similar lack of oversight by Jakarta.
is going on with that project. I have subscribed to it, but with
all the volume of Avalon dev, Avalon users, et. al. it is hard to
notice when something like this happens.
[technical details snipped]
I don't have an opinion on the technical details. But I do have an opinion on the state of affairs when I see people aren't responsive.
The fact that the change slipped in under the radar is something we can't change.
These changes were introduced on the 26-28 November and 02 December. There has been no discussion on this subject. But that does not mean that discussion should not happen. In fact - from a PMC Member perspective there is absolutely no way that I could support the release of Phoenix based on containerkit simply on the grounds that its not "owned by" the community. Beoyond that there is the obviouse issue of the releasing a container revision that is inconsistent with other Avalon work.
Should be possible to roll back Phoneix to the status prior to 27-November 2002. I'm not sufficiently savy to do that in terms of CVS manipulation - but I think its the right thing to do.Who wants to take responsibility for either reverting Phoenix to the point where it no longer needs Info, or updating Phoenix to use Info properly?
I would say preferable the first course.Preferably, the latter course should be done. We need Phoenix to compile.
There are some important things comming up in the context threads that demonstrate a fault in the specifications of both the meta and info packages. These issues are comming up as a result of the recent user community participation on Avalon dev - and I think addressing those issues is more important than pushing through a major rewrite of the Phoenix core (particularly a rewite that has zero community participation). Ideally, that core should be based on meta descriptions that are consistent across all containers - and the reality is that a common solution is strait-forward.
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
