After a short and spirited discussion on the design list, we have
looked at the risks at various angles.
We've discussed about risks from a strategic perspective. We looked
at the impact on development and QA. In addition, we have shared
various opinions on the design.
What are the risk factors which favor one design over the other?
*Schedule risk in development (Getting preview out the door)*
Matthew estimates there is no additional time required to develop one
approach over the other.
*Schedule risk in QA (Getting preview out the door)*
Mikeal and Adam believe the new design will not take any more time to
test.
*Serious objections from any member of the team, this includes anyone
at OSAF*
No one claims they have any serious objections to trying out an
alternative design. No design is truly risk free. The proposals
represent slightly different compromises and emphasis. Ted cautioned
us this is not the last time we'll iterate on the design.
It seems like the question at hand is whether to do this for preview
or post preview?
The server team favors trying out the new proposal for preview. With
that in mind, we are going to move forward with the new proposal for
the detail view, aware of the risks raised in this discussion.
From this point on, we've settled on a direction for preview. There
were healthy questions raised in the discussion today and we will
revisit them throughly post preview.
I feel this is a calculated risk. I look forward to testing preview
and informing future design with the results.
-Priscilla
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
