Administrators, upwizcampeditors
0
edits
Chalo Chatu:Contributing to Chalo Chatu: Difference between revisions
From Chalo Chatu, Zambia online encyclopedia
Chalo Chatu:Contributing to Chalo Chatu (view source)
Revision as of 05:46, 11 July 2017
, 11 July 2017→How to write an edit summary
| Line 51: | Line 51: | ||
* ''Summarize''. Summarize the change, even if only briefly; even a short summary is better than no summary. | * ''Summarize''. Summarize the change, even if only briefly; even a short summary is better than no summary. | ||
* ''Explain''. Give reasons for the change, if you think other editors may be unclear as to why you made it. | * ''Explain''. Give reasons for the change, if you think other editors may be unclear as to why you made it. | ||
* ''Abbreviations''. Abbreviations should be used with care. They can be confusing for new contributors. For an explanation of some commonly used abbreviations, see this | * ''Abbreviations''. Abbreviations should be used with care. They can be confusing for new contributors. For an explanation of some commonly used abbreviations, see this edit summary legend. | ||
* ''Expand on important information''. Readers who see only the summary might not get the entire picture. Prevent misunderstanding: If an edit requires more explanation than will fit in the summary box, post a comment to the article's | * ''Expand on important information''. Readers who see only the summary might not get the entire picture. Prevent misunderstanding: If an edit requires more explanation than will fit in the summary box, post a comment to the article's talk page to give more information, and include "see talk" or "see discussion page" in the edit summary. | ||
** If you are | ** If you are copying text within Chalo Chatu, you must at least put a link to the source page in the edit summary at the destination page. | ||
* ''Talk pages''. When editing | * ''Talk pages''. When editing talk pages, consider copying your comment to the edit summary, if it is brief; this allows users to check Recent changes, Page history and User contributions (see below) very efficiently. | ||
==== What to avoid in edit summaries ==== | ==== What to avoid in edit summaries ==== | ||
* ''Avoid misleading summaries''. Mentioning one change but not another one can be misleading to someone who finds the other one more important. You could add something like "and misc." to cover the other changes. | * ''Avoid misleading summaries''. Mentioning one change but not another one can be misleading to someone who finds the other one more important. You could add something like "and misc." to cover the other changes. | ||
* ''Avoid vagueness''. While edit summaries can be terse, they should still be specific. Providing an edit summary similar to "I made some changes" is functionally equivalent to not providing a summary at all. | * ''Avoid vagueness''. While edit summaries can be terse, they should still be specific. Providing an edit summary similar to "I made some changes" is functionally equivalent to not providing a summary at all. | ||
* ''Avoid inappropriate summaries''. You should explain your edits, but without being overly critical or harsh when editing or reverting others' work. This may be perceived as | * ''Avoid inappropriate summaries''. You should explain your edits, but without being overly critical or harsh when editing or reverting others' work. This may be perceived as uncivil, and cause resentment or conflict. Explain what you changed, citing the relevant policies, guidelines or principles of good writing, but do not target others in a way that may come across as a personal attack. | ||
* ''Avoid incivility. ''Snide comments, personal remarks about editors, and other aggressive edit summaries are explicit | * ''Avoid incivility. ''Snide comments, personal remarks about editors, and other aggressive edit summaries are explicit edit-summary "don't's" of the Chalo Chatu Civility policy. | ||
====Use of edit summaries in disputes==== | ====Use of edit summaries in disputes==== | ||
