Hi Ambrogio,
Ambrogio schrieb:
For example if one open an issue asking for a font effect that is not
implemented yet, can I confirm the issue?
And what appens if I confirm the request as new?
For me, if I think that a request is usefull, and I think that it's
important that this feature will be implemented, I can confirm it.
So developers can know that is a good request.
There was proposal for a RFE-Process some time ago:
http://qa.openoffice.org/issue_handling/handling_RFEs.html
http://qa.openoffice.org/issue_handling/workflowcharts/RFE_issues_by_QA.sxd
We had even some people working on moving "low level" Reqirements to
"high level" Requirements. In theory the high level requirements are
those, that would have status "new" (and some keywords). The idea was
similar as your - those requirements are "good ones" and worth
implementing. Next stage was to get a decision, if they would be
implemented ... but this didn't ever happen (at least not in a visible way).
At the moment, the best way to get a feature implemente is to find
developers, a I-Team to write a specification .. and implement it.
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
