Closed Bug 446070 Opened 16 years ago Closed 15 years ago

Relabel "Edit Summary" in editor

Categories

(support.mozilla.org :: Knowledge Base Software, task)

task
Not set
trivial

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: cilias, Assigned: paulc)

References

()

Details

(Whiteboard: tiki_string, tiki_upstreamed)

Attachments

(1 file)

People are not summarizing their edits, or citing references.

Let's rename "Edit Summary" to:
"Describe your edit and cite a reference"
probably more effective to make the field required, but I agree "Edit Summary" always seems like you're editing the summary of the article rather than the edit.
Great idea. I've filed bug 446201.
Seems very trivial, and would make the UI easier to understand.
Severity: normal → trivial
Target Milestone: --- → 1.4
Note to self to check other places where "Edit Summary" may show up :)
Assignee: nobody → paul.craciunoiu
So we'll stick with "Describe your edit and cite a reference"?
That's a bit wordy. What if we just put "Describe your edit"? If references are much needed, however, we can make it as Chris suggested.
Is edit friendly enough? we could say "changes" instead, but maybe edit is more consistent with other references?
Why the "cite a reference" part? That confuses me, as most of my edits don't have references. 

How about something like "Describe the changes you made:" ?
Sometimes people make edits with info that we can't confirm; so we want to encourage new contributors to cite references.
What's the final word on this?
Chris, it sounds like we're making the label harder to understand in order to avoid rare cases of people making claims that aren't validated. If this happens only "sometimes," I'd rather a reviewer ensures that the info is correct by e.g. testing it than relying on the author's reference (which might still be incorrect). Saying "cite a reference" for people that don't have one is going to be confusing.

My suggestion is still "Describe the changes you made:". What do you think?
This is more about instilling good practices. (Particularly in cases in which solutions cannot be tested on-demand, because we can't replicate the problem to begin with. :-) )

If it's going to cause more harm (confusion) than good, "Describe the changes you made:" sounds good.
Okay, you guys have to agree before I post a patch :)
Attached patch patch, v1Splinter Review
Also placed the colon inside the {tr}, yay!
Attachment #387709 - Flags: review?(smirkingsisyphus)
Attachment #387709 - Flags: review?(laura)
Attachment #387709 - Flags: review?(laura) → review+
r29661 / r29662
Is 1.2.1 the next release?
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: 1.4 → 1.2.1
Attachment #387709 - Flags: review?(smirkingsisyphus)
Whiteboard: tiki_string ?
Whiteboard: tiki_string ? → tiki_string, tiki_upstreamed
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: