On Thursday 26 December 2002 04:00 am, Tom Parmenter wrote:
Rule or no rule, an empty summary field is bad manners.
You can always cut and paste something from your change. The statement that writing a summary can be more onerous than making the change is ludicrous.
Tom Parmenter Ortolan88
Not when fixing formatting. Having to fill-in an edit summary would significantly slow me down so I definitely would object to having to perform the needless keystrokes for these mundane changes. However, when I do make an edit worth documenting I do so nearly every time and if anything I over document. This should stay a 'rule to consider' for at least logged-in users.
It would be OK by me if this was a requirement for non-logged-in users (along with taking-away their ability to mark edits as minor). Anything to slow the rate of useless experiment page creation AND give non-logged-in users another reason to log-in or at least use the preview function is a good thing.
-- Daniel Mayer (aka mav)
WikiKarma payment. Have you had your Wiki today? http://www.wikipedia.org/wiki/Herb_Ritts (new)
|From: Daniel Mayer maveric149@yahoo.com |Sender: wikien-l-admin@wikipedia.org |Reply-To: wikien-l@wikipedia.org |Date: Sat, 28 Dec 2002 01:06:28 -0800 | |On Thursday 26 December 2002 04:00 am, Tom Parmenter wrote: |> Rule or no rule, an empty summary field is bad manners. |> |> You can always cut and paste something from your change. The |> statement that writing a summary can be more onerous than making the |> change is ludicrous. |> |> Tom Parmenter |> Ortolan88 | |Not when fixing formatting. Having to fill-in an edit summary would |significantly slow me down so I definitely would object to having to perform |the needless keystrokes for these mundane changes. However, when I do make an |edit worth documenting I do so nearly every time and if anything I over |document. This should stay a 'rule to consider' for at least logged-in users.
If you are slowed down by typing "markup fixes" I suggest drinking coffee. If the fixes are mundane, that's what I put in, and usually make the change Minor.
If the changes are more substantive, I usually take the opportunity to explain what I am doing "alternate form of article title bolded", or "album titles in italics, songs in quotes" so that they will appear in Recent Changes and perhaps pass along the knowledge to someone else.
Rule or no rule, an empty summary statement is bad manners. The statement that writing a summary can be more onerous than making the change is ludicrous.
Tom Parmenter Ortolan88
| |It would be OK by me if this was a requirement for non-logged-in users (along |with taking-away their ability to mark edits as minor). Anything to slow the |rate of useless experiment page creation AND give non-logged-in users another |reason to log-in or at least use the preview function is a good thing. | |-- Daniel Mayer (aka mav) | |WikiKarma payment. Have you had your Wiki today? |http://www.wikipedia.org/wiki/Herb_Ritts (new) | |_______________________________________________ |WikiEN-l mailing list |WikiEN-l@wikipedia.org |http://www.wikipedia.org/mailman/listinfo/wikien-l |
On Saturday 28 December 2002 04:06, Daniel Mayer wrote:
Not when fixing formatting. Having to fill-in an edit summary would significantly slow me down so I definitely would object to having to perform the needless keystrokes for these mundane changes. However, when I do make an edit worth documenting I do so nearly every time and if anything I over document. This should stay a 'rule to consider' for at least logged-in users.
When I fix a typo, I usually put an edit summary that just says "sp". If I ever make a change and don't put a summary, it's a mistake and the software should not allow it.
phma
Daniel Mayer wrote:
Not when fixing formatting. Having to fill-in an edit summary would significantly slow me down so I definitely would object to having to perform the needless keystrokes for these mundane changes. However, when I do make an edit worth documenting I do so nearly every time and if anything I over document. This should stay a 'rule to consider' for at least logged-in users.
I'm pretty much the same as Mav. I make a lot of minor edits. It's not too hard to hit TAB, type "typo" and press RETURN, but makign summaries mandatory would be a pain.
It would be OK by me if this was a requirement for non-logged-in users (along with taking-away their ability to mark edits as minor).
Agreed.
... give non-logged-in users another reason to log-in
It's nice when IPs become named users. But some irritating users are wise to the fact that once they register we have a harder time banning them for bad behavior (both technically and as a matter of principle...).