9

I'm going to give the community a chance to disagree, but I think it should be deleted. I don't think that the low view count warrants the historical lock. The net score of the question and top answers is also rather lackluster. There's also not that much insightful (from my perspective, anyway) in the answers, either.


9

I don't see a purpose in deleting this question. I removed the low quality tag of junior-programmers and deleted all of the negatively scored answers. I've also removed the mod notice about long answers. Right now, the question is closed as too broad and has a historical lock placed upon it. This should be a clear indicator to any visitor that this type of ...


8

The recourse for having a post locked is to post on Meta. Now that it's here, all of the mods are notified. The lock is temporary (unfortunately, the options are rather limited, though) and can be lifted early once a resolution is achieved. Continually rolling back valid edits to your post is not constructive, and a lock is the only mechanism available to ...


8

After looking at the question, the edit history and the discussions about both so far, I want to add a few notes. The lock on the question is not because the question itself is bad or wrong or unsuitable. The question got locked because there is a disagreement on how to formulate certain parts of the question and is only meant to avoid polluting the history ...


7

You seem to believe that question locked for content dispute at meta should remain at main site as originally posted ("Lock question as-is"). This approach doesn't make sense to me. For the purpose of meta discussion, it is insignificant what particular revision is hanging on the main site because full revision history and original version are always ...


7

I reviewed the question, the comments, the edits... The post was locked because of repeated attempts to change the question in a way that the community was in disagreement with. Besides that I am largely in agreement with ThomasOwens. Note that my post specifically implements the tactics referred to in that post to achieve usefulness as a subjective ...


7

The answers were...abysmal. Yes, it had a lot of views, but I don't see how it can serve as a useful reference based on the answers there.


6

As someone who answered this question in 2011, I agree with you on both points: In its current form, it shouldn't exist: it's a poll and most answers are less than constructive. The lock makes it impossible to improve both the question and the answer. A year ago, I was writing a very detailed article on three vs. two monitors setup, and recalled that I ...


5

Deleted. The low view count was more than enough to me.


5

The question doesn't really qualify for the historical lock (emphasis mine): When is it appropriate to lock a question for historical reasons? Questions can be historically locked when: The post is Off-Topic or Not Constructive, and The post is stellar, in spite of its off-topic nature, and There are a large number of views, upvotes and ...


4

This is sort of an edge-case. When a migration is rejected, its answers are deleted on the target site, it is locked, and the reverse happens on the origin site - so right now on SO, that question is just marked closed; it could be re-opened, deleted, edited, etc. - unless you check the history, there's no evidence it was ever migrated. Normally, folks ...


4

The question was migrated from Stack Overflow. If the migration is rejected by the question getting closed as Off Topic or Not a Real Question it's deemed to be a bad migration and the question locked down. I can unlock it if you think it's salvageable. Once unlocked you'll be able to cast reopen votes as well as editing it. Once you've finished improving ...


4

Questions older than 60 days can no longer be migrated, not even by moderators. Your question, albeit being off topic on both Programmers and Stack Overflow, is fairly popular and generated a few very useful answers. This, I assume, is why Thomas decided to place a historical lock on it. The lock will prevent it from being deleted by the community, which is ...


4

I saw no reason at all for this to still exist and now it doesn't


3

First, you surely noted that your question was already asked in a comment in 2011, and that comment was already answered in the following comment: Remember that an accepted answer is not an answer that is universally accepted from all the users; it's the answer that is accepted from the OP, who chooses the answer that helped him more. Only the OP can ...


3

I've deleted it as it seemed to have minimal redeeming value.


3

EDIT: I received 5 downvotes so I unlocked and deleted I was the one who historical locked it responding to a flag requesting the same. Here is my opinion on historical locks: It is at least 3 years old It has at the very least (n years X 1000 views) in total views It has at least one good attempt to answer either a question with a number of problems as ...


3

locked:yes views:0..2000 score:0..3 duplicate:no migrated:no After a few days, we should have enough agreement on this batch of 49 questions to move forward with the actions in the below headings. The following questions should remain closed but not deleted https://softwareengineering.stackexchange.com/questions/88359/is-the-spark-view-engine-for-asp-net-...


3

I'll put my cards on the table. I didn't vote to close your question, but if it was open when I noticed it, I would've voted to close it as 'Unclear What You're Asking' because: I'm not sure which problem you're trying solve. It's difficult to imagine a tool that could do what you're asking for. And if you're looking for a tool, then we should close it as ...


2

The question was migrated over a year ago - March 2011 - so the stub has long been deleted, April 2011 in fact. I'd unlock the question if it were newer and potentially more constructive, but I don't think any amount of editing can salvage it now. I was waiting for somebody to spring to the question's defence, but as that wasn't forthcoming I've just ...


2

I think this behavior might have to do with the migration being rejected. But the behavior is not that intuitive, and it might be something different. My understanding is that if a question is migrated and then closed on the receiving site, the migration is rejected. The question simply ends up closed on both sites.


2

I can only speculate, but it did have 5,000+ views so perhaps maple_shaft thought it was worth locking for that reason. If something, while being off topic, is popular (looking at its age, votes and views) then we do consider locking rather than deleting. This is so that we preserve any incoming links. This was probably a borderline case, almost enough ...


2

I wholeheartedly agree. I unlocked and deleted this question. The views just don't justify keeping it around. If you disagree and would like Wiki Answer Lock this instead then please volunteer. I think it is too much work for too little benefit honestly. As a side note, I am astonished at 40+ answers and < 2,000 views. That is a high answer to view ...


2

TL;DR Suggest to undelete the question since it was edited to a better shape and made match the top answer. After that, remove "poll item" answers invalidated by the question edit and reopen. I think that in its current shape the question staying visible is not okay, even as historically locked. Low quality "historical context" seems to totally obscure ...


Only top voted, non community-wiki answers of a minimum length are eligible