Hi Niklas,
On Fri, 2006-10-20 at 10:40 +0200, Niklas Nebel wrote:
> 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
>
> Had you quoted more, we'd see that the ".." part lists some problems
> with the patch that haven't been resolved.
Sure - and they are valuable feedback, much appreciated; and need
fixing - but ultimately is there any point if User Experience are the
gateway for all changes, and simply don't comment ?
> 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".
"real work" ? honestly - do you expect to get perfect 1st patches from
people inexperienced with the 'intricacies' of the calc code ?
Volunteers for example ( Muthu is an unpaid Indian chap ).
If so, I would suggest that is not a realistic expectation. As for not
being able to describe what is required, I refuse to accept that adding
a single missing key-binding for a single language requires any more
detailed description in order for you (or anyone else) to understand
it :-)
If by "real work" you mean that the paperwork and interaction involved
in getting a small change into OpenOffice.org *far* outweighs the actual
time generating the code - then I totally agree with you :-) Some people
see that as a feature, I see it as a debilitating bug.
On projects I'm interested in developing, if a patch arrives that needs
a couple of minor fixes, I would tend to point these out & fix them at
the same time [ it's often no more effort than locating them in the 1st
instance ], test & commit.
> > 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.
<joke>Strange - we have a different process whereby we have no idea
what we want to achieve, we just type at random for some weeks, then
submit a patch ;-> This whole "knowing what you want to achieve" thing
is a revolutionary concept indeed.</joke>
Regards,
Michael.
--
[EMAIL PROTECTED] <><, Pseudo Engineer, itinerant idiot
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
