On 11/2/06, Michael Meeks <[EMAIL PROTECTED]> wrote:
It seems there has been a wide-ranging debate on the spec. topic wrt.
reducing potentially discouraging barriers to entry for community
contributors. I tried to summarise where I -think- we're at, and then
present some principles & some proposals for some new ways of doing
things.
[snip]
Another point I want to mention is that, perhaps the UI design
requirement at CWS integration time should be relaxed a bit. Instead
of requiring UE approveal of the UI change at cws integration time,
either QA or peer reviewer can pre-approve the UI and integrate the
code first. And queue the final UI approval to IssueTracker as a new
issue, assign it to UE (whoever that is) and set the appropriate
target milestone so that he/she can finalize it later. If UE thinks
that a UI change is necessary, request change to the developer so that
the finalization takes place before the public release. This way, the
process is asynchronous, and in line with our goal of fast track code
integration.
Kohei
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
