Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi Kohei,


Am 09.07.2011 19:39, schrieb Kohei Yoshida:
Regarding this bug

https://bugs.freedesktop.org/show_bug.cgi?id=39068

Rainer started the specification process for this.

I'd rather say he started to collect information in a structured way to help all the people involved in a new feature implementation. And to make more people aware that their help is needed.

I thought one thing we decided to do was not to re-introduce this
over-engineered, time-wasting specification process.  Is this a new
development in the LibreOffice space?
It's not about a mandatory over-engineered process.

I started something similar for the gridline display. I (and others) found this quit helpfull - but I would not do it again in that detail for quite simple patches. It was more to see, what might work and what not.

Anyway - what I really dislike from your further communication (your answer to Christoph) is the way you speak about "us" developers and "you" UX, QA and documentation guys. It's after all "we" who create and develop LibreOffice.

All that said: if you can suggest some other word for "spec" I'd be quite happy. For me it is more or less a notes collection for an implementation - and not the thing that was used at OOo. What Rainer and me currently do with those spects is really only a first step and maybe a step to far. Again - we are currently trying to see what works and what not.

André

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.