Bulbapedia:Code of conduct: Difference between revisions

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to navigationJump to search
m (dash fix)
Line 9: Line 9:
There are hundreds and hundreds of edits made to the main space every day. Most of them aren't conflicting, everyone humming along and improving Bulbapedia at their own pace. Sometimes, however, users come into conflict over specific phrases, pictures, templates, or other aspects of the Wiki.
There are hundreds and hundreds of edits made to the main space every day. Most of them aren't conflicting, everyone humming along and improving Bulbapedia at their own pace. Sometimes, however, users come into conflict over specific phrases, pictures, templates, or other aspects of the Wiki.


On regular pages, if you think somebody's wrong about a fact, and they don't think they're wrong, an edit war can ensue. While that is going on, '''do''' try to talk it out politely on the talk pages. Outline why you think they're wrong--factually, not stylistically--and expect them to do the same for you. Call in an arbitration. '''Do not''' insult them, demean them, or otherwise bash them in order to prove your point. It doesn't improve your image in the community and won't win you any points in the argument.
On regular pages, if you think somebody's wrong about a fact, and they don't think they're wrong, an edit war can ensue. While that is going on, '''do''' try to talk it out politely on the talk pages. Outline why you think they're wrong—factually, not stylistically—and expect them to do the same for you. Call in an arbitration. '''Do not''' insult them, demean them, or otherwise bash them in order to prove your point. It doesn't improve your image in the community and won't win you any points in the argument.


If you disagree with someone stylistically--for instance, if you think a template or picture is wrong, or a bad choice, talk to the creator or post on that template's talk page before making changes. Be nice about it--point out the specific deficiencies, and why your idea provides a more effective solution. Don't degrade their work--remember, they worked hard on it. Remember, too, that ideas have inertia, and it may take someone a little while to leave their design and come around to yours. Be patient, understanding, and, again, kind when dealing with another user. It may slow the process of change down a little bit, but the changes will be more pleasant to everyone.
If you disagree with someone stylistically—for instance, if you think a template or picture is wrong, or a bad choice, talk to the creator or post on that template's talk page before making changes. Be nice about it—point out the specific deficiencies, and why your idea provides a more effective solution. Don't degrade their work—remember, they worked hard on it. Remember, too, that ideas have inertia, and it may take someone a little while to leave their design and come around to yours. Be patient, understanding, and, again, kind when dealing with another user. It may slow the process of change down a little bit, but the changes will be more pleasant to everyone.


==Userspace and talkspace interaction==
==Userspace and talkspace interaction==
Line 30: Line 30:


===Other aspects of the user space===
===Other aspects of the user space===
Subpages are cool, as are userpages. Almost all of us have them. But don't use them to bash people, or create lists of disliked people. It would also help if there were no lists of people you liked especially, either; that can cause an atmosphere which encourages cliques, and that's bad. If there are people whom you're working on a project with--for instance, Project Dex--and you want to thank them or give them credit somehow or somewhere, that's fine. But an "A-list" of sorts, that describes your 'best buddies,' can lead to rising tensions, and has few positive consequences.
Subpages are cool, as are userpages. Almost all of us have them. But don't use them to bash people, or create lists of disliked people. It would also help if there were no lists of people you liked especially, either; that can cause an atmosphere which encourages cliques, and that's bad. If there are people whom you're working on a project with—for instance, Project Dex—and you want to thank them or give them credit somehow or somewhere, that's fine. But an "A-list" of sorts, that describes your 'best buddies,' can lead to rising tensions, and has few positive consequences.


This does not apply to affiliations or statements of solidarity made with userboxes, or anything of that sort.
This does not apply to affiliations or statements of solidarity made with userboxes, or anything of that sort.


==User feuds==
==User feuds==
There are a handful of long-running feuds between some users. Kiss and make up. Bury the hatchet. Drain the bad blood. It would be a really great thing if every user who knew they had someone they really didn't get along with extended their hand--metaphorically--and apologized for wronging the other.
There are a handful of long-running feuds between some users. Kiss and make up. Bury the hatchet. Drain the bad blood. It would be a really great thing if every user who knew they had someone they really didn't get along with extended their hand—metaphorically—and apologized for wronging the other.


Accept that apology if it drops your way. Apologize back for anything you might have done to wrong them. Because we're all in this together, at the end of the day, and there's no reason to make enemies when you could have friends.
Accept that apology if it drops your way. Apologize back for anything you might have done to wrong them. Because we're all in this together, at the end of the day, and there's no reason to make enemies when you could have friends.