To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=105217
User es changed the following:
What |Old value |New value
================================================================================
Status|NEW |RESOLVED
--------------------------------------------------------------------------------
Resolution| |INVALID
--------------------------------------------------------------------------------
------- Additional comments from e...@openoffice.org Sun Sep 20 11:33:17 +0000
2009 -------
1) The wrong problem: "I have long wondered how to point the OOo developers to":
We don't need to get remember about the fact we have issues pending since years.
We KNOW it!
What we need is developers, which submit patches to solve those issues.
2) The wrong decision: "*I* have long wondered how".
What is the legitimacy of your present action?
Did you discuss this with the developper/QA community?
Do you have gathered input from a Product Management team which decided to use
this method to collect "old 'forgotten' issues"?
I don't think so.
3) The wrong criteria
"it blocks the adaptation of OOo for you or in your organization"
"important (in their opinion)"
Do you think someone reporting an issue will consider *his* issue as not
important?
We try to implement and act on objective criteria but not on subjective ones.
4) The wrong method.
You describe the problem as if we *forget* some issues (which is not the real
problem, see 1)).
In the end this issue will have maybe 500 dependencies to this issue.
Don't you think we can also "forget" this one?
Who is the owner of the issue who will "remember" "people" to fix the tasks?
Does the owner have the *authority* to do so?
"writerneedsconfirm" is definitively the wrong owner.
Sub-component "programming" means Macros, Basic, API and so on in OOo.
Not "to-dos for the programmers"
If the problem is "to long time" than the solution is to set a target to those
tasks to say: "we will fix them then". But your issue has no target and you
don't have the right to set one.
So this method doesn't solve the problem at all!
Sum up: please don't spend more of your free time on an own idea which has not
been discussed and approved by others and which addresses the wrong problem
problem with the wrong method.
I might now recommand you to read this:
http://blogs.sun.com/GullFOSS/entry/why_all_issues_are_equal
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org
For additional commands, e-mail: issues-h...@sw.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
