Dealing with engineers that frequently leave their jobs
It's true. This question does not meet the core criteria for this site.
But it generated some fantastic answers.
Can we please lock this question so that others may learn from it too?
-
1+1 top voted answer stands out indeed. A handful other answers look pretty decent, too. Locking may be a reasonable option– gnatSep 8, 2012 at 21:19
-
1Hm, why? It's not in any danger of getting deleted and more importantly it was last active today. Locking prevents any further activity on the question or its answers, what would be the point of locking it?– yannisSep 8, 2012 at 21:21
-
@Yannis Rizos: I thought that a closed question may be deleted at any time. Am I mistaken? Also, I don't think this question will ever be eligible for re-opening. Am I mistaken? // I just don't want to lose such great answers. I actually think that this question should be seriously considered for the blog.– Jim G.Sep 8, 2012 at 21:24
-
1I flagged the question to be moved to workplace.stackexchange.com– SongoSep 9, 2012 at 11:47
-
2@songo Please don't flag old questions for migration, we won't migrate any of them, especially to beta sites (unless the target site's community asks for them specifically).– yannisSep 9, 2012 at 13:57
Add a comment
|
1 Answer
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 inbound links on the post, and
- The post is contentious; i.e. it has been closed and reopened at least once, or deleted and undeleted at least once
If the question remains closed:
- There is a risk of it being deleted at some later point. We rarely delete highly upvoted questions without very good reason, however I can't promise that three 10K+ users or a fellow moderator won't vote to delete it.
- It and its answers are still editable and can be voted on (including re-open votes for the question)
- It appears in site searches.
If the question gets a historical lock:
- It will be frozen as is, no more edits or (any kind of) votes.
- It won't appear in site searches, and will only be accessible via its url.
The historical lock is more intended for questions that are already deleted or, for whatever reason, are very close to being deleted. For example if we where doing an organized cleanup, similar to stci and we were targeting project-management questions, then yes, it would make sense to lock it. But right now the question isn't really on a path to deletion, or if you prefer that path is extremely long, it already survived stci (check revision 5).
I wouldn't mind locking it, the whole process is just a click of a button really, but given that one of its answers was edited earlier today, and the question has a pending re-open vote, it seems that its current state is preferable. Is there a very specific reason we should froze it?
-
4