Edit - Meta Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

1

Your modified suggestion for on hold behavior is way too open to abuse, imo. Aside from that, it's the same as the original suggestion (the gentler term bit and all).

Manishearth
– Manishearth

2013-05-15 21:28:24 +00:00
Commented May 15, 2013 at 21:28
@Manishearth: I see your point. But my main point is that the transition from "[On Hold]" to "[Closed]" should reflect a real change of status, a feature that the original proposal lacks. See the next-to-last paragraph of my updated answer.

Keith Thompson
– Keith Thompson

2013-05-15 22:23:21 +00:00
Commented May 15, 2013 at 22:23
It's not supposed to be a real status change, though. It's just a psychological trick. We want closing to be instantaneous, and to behave the same. However, we don't want to scare newbies off with "[closed]", as "closed" in forum speak usually means "dead forever" (which leads to unnecessary bickering and whining when they can just fix the goddamn question)

Manishearth
– Manishearth

2013-05-16 05:01:10 +00:00
Commented May 16, 2013 at 5:01
@Manishearth: I understand that, in the proposal, the transition from "[On Hold]" to "[Closed]" is not supposed to be a real change in status. I'm saying that I think that's a bad idea that will cause confusion. I think it would be better to leave it as "[On Hold]" indefinitely or to make the transition a real one.

Keith Thompson
– Keith Thompson

2013-05-16 15:06:13 +00:00
Commented May 16, 2013 at 15:06
Agreed. Is it true that the only difference between "on hold" and "closed" is that the triggering event occurred in the last 5 days? I'm still not sure.

bmm6o
– bmm6o

2013-06-27 01:51:04 +00:00
Commented Jun 27, 2013 at 1:51

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »