Comment 96 for bug 668415

When I marked this bug Invalid in NULL Project, I explained why that was correct. See https://bugs.launchpad.net/unity/+bug/668415/comments/78.

It is meaningless for a bug in NULL Project to have non-Invalid status. Please click on "NULL Project" and read what it means before making changes to bugs assigned to it. If this bug is to be reopened, it should also be assigned to a project that corresponds to some real application or software development effort. This bug's Invalid status in NULL Project is *not* incorrect, because the statuses that represent this bug's real state are the statuses in unity and in Ubuntu, *not* the statuses in NULL Project.

This bug's current Won't Fix statuses in unity and in Ubuntu reflect that there is a difference of opinion; they are correct as well. (However, it is not *universally* the case that bugs where there is a difference of opinion should not be marked Invalid. Different projects use Won't Fix a bit differently from one another. In some projects, if there is a difference of opinion that the developers agree is reasonable, but they have nonetheless decided not just to make the requested change but also that the issue raised is *not* a bug, they may correctly mark the bug Invalid. See https://help.launchpad.net/Bugs/Statuses.)