[Zope3-dev] Re: ZopeTop skin

[Paul Everitt]

Roger Ineichen wrote:
> Hi Paul 
> 
> 
>>-----Original Message-----
>>From: zope3-dev-bounces+dev=projekt01.ch at zope.org 
>>[mailto:zope3-dev-bounces+dev=projekt01.ch at zope.org] On 
>>Behalf Of Paul Everitt
>>Sent: Tuesday, March 22, 2005 4:26 PM
>>To: zope3-dev at zope.org
>>Subject: [Zope3-dev] Re: ZopeTop skin
>>
>>Roger Ineichen wrote:
>>
>>
>>>Cool, that good news.
>>>
>>>I like to add the xmltree back to the new skin after 3.1.
>>
>>Is that a final decision?  Meaning, if the bugs are fixed, it 
>>will still 
>>not ship as the default tree in 3.1?
>>
>>If so, my motivation for fixing bugs in 
>>soon-to-be-stripped-out software 
>>is rather low. :^)
> 
> 
> Yup, I see.
> 
> 
>>>We will add a option where we can select between the 
>>>two trees in the ZMI (TTW).
>>>
>>>Right now the target was, that the ZMI works in every browser!
>>
>>That's new information.  Rotterdam was based on a different decision, 
>>made long ago.
>>
>>I don't mind if that decision is now made, and the original 
>>decision is 
>>overturned.  I just want someone with the right authority to 
>>communicate 
>>the decision.
> 
> 
> That's my problem, Stephan wrote a TODO marked the issue we have to 
> fix that's only I have right now. Stephan is at vacation right now.
> 
> Jim has to much work, and others I think don't care.
> 
> I don't like it to propose something, I tell and do only what 
> I think is ok for most users and developers. But it's hard to 
> guess what people think without feedback.
> 
> Whould be nice to hear a statement form the release or project 
> manager here!
> 
> Do whatevery you think is the best for the next release. 
> I'm really don't care about older browsers by myself. 
> 
> btw
> What I know now, is, if Stephan is back and Jim has time,
> we really have to discuss our project management.
> 
> We REALLY NEED some project manamgent and a clear way
> for release, bugfix, new features and other parts like
> descicions about browser compatibility etc.
> 
> Otherwise I'm really lost with commiting and working
> straight forward.

I agree with what you've said.  Ultimately, we need some way, I think, 
for the UI folks to self-organize and have the stamp of legitimacy on 
their decisions.  We can't keep piling more stuff on Jim and Stephan's 
shoulders.

My vote is to not change the status quo for the upcoming feature freeze. 
  The status quo is:

1) Rotterdam is default.

2) Rotterdam is targeted first at users, not developers.

3) Rotterdam should feel "modern".

4) Rotterdam can use IE 5.5+ or Mozilla to accomplish (2) and (3).

While this is clearly not what everybody in this thread has wanted, it 
is in fact the status quo, and I don't think we can make a big change in 
the next 11 days.

--Paul