Comment 12 for bug 262193

On Tue, 2008-11-11 at 22:35 +0000, Matt Layman wrote:
> Mark, I agree with the notion of team organization that you are
> describing; however, your last sentence, "More importantly, we lock the
> data when the user provides it themselves," is incorrect. And I
> personally believe that is the real bug here.
>
> My initial report of this bug was a duplicate (and rightfully so
> chronologically), but I reported exactly the opposite behavior of your
> last sentence (a piece of information that is not captured in this bug
> report). If a user has already set their location, another user can
> still change it. I tested this on staging.launchpad.net when I submitted
> the bug, and I tested it again just now to verify that the behavior is
> still the same.

I can't reproduce that. Can you show me the user who's set his own
location and yet you were still able to change it?

I see you've set yours and I don't see the option to edit your location
on your profile page. I'm also forbidden to access your +editlocation
page (when I manually craft it).

I've set my location too, so you can try changing it and you'll see the
option is not there and you should not have access to
https://launchpad.net/~salgado/+editlocation since I've set it myself.