Emphasise the "official" bit, de-emphasise the "lock" bit
Update: The language and appearance of the policy notice has been updated to be very close to what has been suggested here (see above for exact appearance)
In my opinion, the more important thing here is "This is not your average question, this is an ...
On these locked posts, as demonstrated by this one, the "Close" button (granted by close vote privileges) has been hidden for me. I'm also told that the "Delete" button is invisible on this post, even to community moderators.
That all makes sense, but why is the "Edit" button still visible if it just yields a "This post is ...
support edits suggested-edits
What should users do if they believe that a Policy Locked post needs an update?
Should they flag the question for moderator attention?
Should they ask a new question on the Meta site proposing a change?
Should they use the Contact link to directly petition the Community Team?
Should they comment on the post?
feature-request help-center status-completed
It's probably worth adding some points about this new lock type to Help Center article about locks, especially since the lock banner contains a direct link to it.
How commonly will this be used? For example, should we expect every or nearly every post by the Community Team to be Policy Locked as a matter of course, or will this be something that is used only on the most problematic posts?
As we have one example of a locked answer...
Could we make it act like an accepted answer? To be maybe pin it under an accepted answer, but atleast be on top of other ones.
It would be easier to find an official answer this way. I ask this as sometimes an official answer can be downvoted a lot. Being able to see the official answer should be easy, even when ...
bug spam flags status-review
I can flag this question as spam or rude/abusive. I don't think that's intentional – other locked posts I can only flag for moderator attention.
(flag has been retracted meanwhile)
Here's how your story "reads" to me. You wanted to comment. You couldn't. You experienced frustration. You might have even believed you were in a Catch-22 -- that your lack of rep was keeping you from doing the only possible thing that would gain you rep, commenting in order to gain the clarifications you needed to answer a question. (Error 1.)
Then you ...
I'd rather not give this information to people who are eagerly awaiting the lock's expiration so they can get right back to their comment argument or edit war or whatever. The goal of the lock is to delay things long enough that they cool down (or forget about it and move on); giving them a timer seems counter to that.
But I agree that it's not clear ...
Ok...my bad. It wasn't immediately obvious or clear that this was your original work. If that happens again please provide a link when flagging.
Can I recommend that you add a pre-amble at the start of your answer along the lines of:
I wrote about this on my blog here: http://lu4242.blogspot.co.uk/2012/05/understandingjsf-2-and-wicket.html
That will ...
In these cases, it's better to:
Rollback the edit (click "Edit", then "Rollback" to the appropriate revision)
Flag the answer and ask a moderator to step in
Stack Overflow is collaboratively edited; it doesn't make sense to kill the very feature that sets us apart from the forums.
That blog is a Internet copy machine, mostly BalusC (Bauke Scholtz) posts:
http://kumarnvm.blogspot.co.uk/2012/01/jsf-2.html copies from What are the main disadvantages of Java Server Faces 2.0?, or was excerpted from this blog post by BalusC.
In http://kumarnvm.blogspot.co.uk/2012/01/using-mvc-design-pattern-with.html the blog owner claims to be BalusC ...
For one-offs, just leave a comment. You can do that. You can even move the other comments to chat or just delete them if need-be.
Heck, edit a big-ass "THIS QUESTION IS LOCKED BECAUSE OF SOMETHING THAT HAS NEVER HAPPENED BEFORE AND WILL NEVER HAPPEN AGAIN" banner at the top of the post if you want. It's a unique occurrence, for which no one was prepared; ...
To expand on my comment
The point of making announcements visible by other means then the post owner would simply be solved by a mod-only tag. Policy that needs its exact wording to remain, can simply be put in a quote block. So this is way over the top for the things you want to achieve. It almost feels like you distrust us, which is something that ...
I think locking it is a good idea, though not for the voting aspect, but for the media attention the question gets (and hence the noise generated by it being unlocked).
Just today, we've already already had comments about it being unlocked that we've deleted, and there's no sense in having a lightning rod around. Lock it, wait for everything to blow over, ...
That's a good idea, but actually another thing confuses me as much as the fact I can actually flag it.
"This comment" sounds a bit misleading because it is not really only this comment, but all the comments can't be voted on (and it is not possible to lock only one comment, as I know). So I propose this wording:
This post is locked; voting on comments ...
You asked a question which was asked a thousand times before, it gets asked probably a few times a the week. You asked on the main site first, which isn't taken very good either by community members.
Also, your post lacks decent formatting and it reads more like a rant. You didn't do any research on the subject, since you would have easily found the answer.
I won't status-completed this because we've only done a small portion of your request so far, which is to make it clearer in the lock dialog what the lock is actually going to do:
Bit of a wall-o-text at the top, but hopefully it's helpful - and it links out to the help center in case more information is needed.
As for the other bits, we've kicked off some ...
Considering it's historically locked, the question and answers shouldn't be updated. That banner shows the content should be taken with a grain of salt already, so I wouldn't feel obligated to get the content adjusted.
If you want to remove your name from it, you can request disassociation of the specific post. That's explained here. Do keep in mind (as in ...
This is now status-completed with the rollout of the new post notices:
This applies to both questions and answers: as you can see, the screenshot above was taken from an answer.
Hovering over the number of days will show the date and time it will be unlocked.
Experimental research suggests the following posts are included (as long as they're not deleted, like e.g. spam posts):
Locked questions which
are not closed
have not been merged
All locked answers
Historical locks are sometimes treated differently than other lock types, but not here.
It's not possible to filter for non-merged questions, but otherwise ...
For some cases, a moderator might unlock and relock a post, however, I don't think that should be the case for this post and this type of edit.
From the FAQ you reference (emphasis mine):
Historically locking a post ends the debate over whether a question should be kept on the site or deleted, and is often the final state of a question that has been ...
Voting arrows do not mean you can vote on the post. If they did, that would mean we'd have to remove them:
when you're not logged in
when you don't have enough rep to vote
when you don't have enough rep to downvote (the down arrow would be removed)
when you are post's author
when you have used all your votes for the day
Voting arrows are shown in all these ...
No, at least not because the question is being voted on.
Locking the question is only needed to prevent noise being posted (taunting comments, nonsense answers, etc.). We should care less if Frosty receives additional votes on that question or not. It's not as if internet points pay for his legal defense.
If the question attracts more noise again, then ...
Trivia: many years ago now, there were three types of votes that could be cast on comments...
The first is the upvote arrow. The second is the delete link (only visible to comment authors and mods). The third was the flag option, until we redesigned the flagging system and stopped storing those as votes.
So at one time, this ...
No, well not for logged-in users that would otherwise have the privilege to vote. The request is (as Shadow Wizard noted in comments) logged and queryable to some extent, but there's no 'feedback' if you're registered.
If you're unregistered or not logged in, it is recorded, you can try voting on this while incognito, the feedback is sent.
Let us not.
You're forgetting an important class of people. Students who just remove the code they shouldn't have posted. These users just wait out the lock period and then remove the code once again. This has happened many times.
The issue is, we can't lock for a significantly long period, say a semester (5 months) or a quarter (3 months). If we had ...