A contributor to the discussion, Scott Kitterman, recommended that the appropriate action for this bug is to close it as "works as designed", and invite you to submit a specification for "system changes to reduce the risk of accidental data loss by new users."
> That's, I think, the right way to deal with this type of design issue. Also
> it gives them a chance to be involved in the discussion and the community and
> feel valued.
I believe I agree with that. That would be the best way to get the right kind of discussion, and maximum community interaction, to find the best possible solution.
A contributor to the discussion, Scott Kitterman, recommended that the appropriate action for this bug is to close it as "works as designed", and invite you to submit a specification for "system changes to reduce the risk of accidental data loss by new users."
> That's, I think, the right way to deal with this type of design issue. Also
> it gives them a chance to be involved in the discussion and the community and
> feel valued.
I believe I agree with that. That would be the best way to get the right kind of discussion, and maximum community interaction, to find the best possible solution.