How to use the new Launchpad status?

[Evan]

On Wed, Jul 7, 2010 at 11:21 AM, Bruno Girin <brunogirin at gmail.com> wrote:
> On Wed, 2010-07-07 at 09:53 -0500, Benjamin Root wrote:
>> Sounds like to me that it is a finer grained version of "Invalid".
>> The idea being that rather than possibly insulting the OP with an
>> "Invalid" statement, one could mark it as "Opinion" where it is
>> effectively closed, but leaves open the possibility that it might have
>> to be revisited later.
>>
>> I guess this helps to distinguish between the bugs that are blatantly
>> Invalid and the bugs that might be a little bit more ambiguous.
>>
>> At least, that is my interpretation...
>
> Thanks, that sounds like a sensible interpretation. So in terms of
> triaging, if the bug is one that we would normally set to invalid
> because even though the software does not behave as the OP thinks it
> should, the reasons for changing it are not clear cut, we would assign
> it the Opinion status rather than the Invalid status.
>
> I suspect that in this case, bugs in that status should also have a
> severity of Wishlist?
>
> A new standard response to use when setting bugs to that status would be
> good. What about the following?
>
>        Thank you for taking the time to report this bug and helping to
>        make Ubuntu better. While we appreciate that the software does
>        not behave as you expect, we consider that it is a matter of
>        opinion whether it should be changed to accommodate your
>        requirement. This bug is being set to "Opinion" to indicate
>        that, although we do not consider it invalid, we will not start
>        work on resolving it until we are satisfied that there are
>        enough details on how to change the software without
>        compromising usability or existing features.

Great. I find the last sentence a bit of a mouthful though. How about:

       Thank you for taking the time to report this bug and helping to
       make Ubuntu better. While we appreciate that the software does
       not behave as you expect, we consider it a matter of
       opinion whether or not the behavior should be changed as you
       suggest. This bug is being set to "Opinion" to indicate
       that. Although we do not consider it invalid, we will not start
       work on resolving it until we have a solution that solves your
       problem without compromising existing functionality and usability.

Just my two cents,
Evan