Michael Meeks wrote:
Let me show you why I feel this way, from a simple example I was
reading this morning: notice the consultation going on in this issue:
http://www.openoffice.org/issues/show_bug.cgi?id=56202
[snip]
------- Additional comments from nn Tue Apr 4 ... 2006 -------
Default keyboard shortcuts are administered by User Experience, so
I'm cc'ing MMP to allow him to comment.
..
[snip]
Had you quoted more, we'd see that the ".." part lists some problems
with the patch that haven't been resolved.
I know this is your attitude personally Frank, and I've enjoyed working
with you on several pieces of code; however all too often people's
attitude seems to be:
"I'm so busy I can't be bothered to reply to your mail/issue"
or "no - I'm too busy to handle this => I'll block it"
or "yes it's fine, but some step in the process wasn't done in
the correct order => reject"
On the other hand, it shouldn't turn into "I've got an unfinished
implementation of something I can't describe, and expect Sun to do all
the real work about it".
I find it hard to communicate how intensely frustrating the Sun
interaction is, but I just thought of an innovative way here, watch this
space.
You could save yourself a lot of frustration by following a common-sense
order of steps: *First* define what a desired feature is, *then* start
implementing. Really. Try it.
Niklas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
