ICANNWiki Code of Conduct
Assume Good Faith
Assuming good faith means that we act on the assumption that everyone who makes an edit is doing so to provide relevant, accurate information. No matter the change, we give people the benefit of the doubt and trust they have come to build, not break ICANNWiki.
Realize that everyone makes mistakes. The nature of Wiki renders it nearly impossible to break and makes corrections easy. By assuming good faith and working together we keep in mind that errors are often unintentional.
By acting openly and honestly in accordance with Real People, we demonstrate our good faith in the community. Working to Be A Builder is another manifestation of good faith because we trust the community to move forward with our work and to respect our contribution.
Be a Builder
This value is much more than building wiki pages that are aesthetically-pleasing or highly informative and useful (although all these are valuable qualities), but building the ways in which people work together to create, and the ways ideas interlace and adhere. The building is as much about the process of creating something valuable as it is about the finished product (especially considering we have no defined endpoint).
Being a builder involves building quality content; it is important to keep the other values in mind during the process of building, since creation typically involves creative destruction.
In order to Be A Builder, it is important not to sweat the small stuff. Remember that Change Is Cheap. You can perfect the page later, but the first step is to get it started. The idea can be likened to building with Legos, you start somewhere and let the creation take shape, adding and subtracting, constantly Refactoring what you are building. This will also allow a jumping off place for the rest of the community. Focus on the big picture, knowing that others can, and will, fine-tune your work and ideas.
To achieve this, click "edit" and "save" often. Doing so creates a visual history of your thoughts and changes that others can use to understand and build on top of your work. Clicking "edit" and "save" a lot also allows you to quickly jump into a document and get your hands dirty. This is similar to the "Release Early Release Often" philosophy common in the Open Source community:
People seed a page with an idea that's often vague and poorly worded. It is rough and that's okay, that's expected. It's a beginning. Other people come along and Refactor' it. There should be freedom from fear that others are going to judge your effort as unworthy, in fact, the expectation is that others will judge your efforts as highly valuable.
Change is Cheap
This value represents our belief in constructive edits and the process of Wiki. Building off the tenets of Be A Builder and Assume Good Faith, we arrive at the conclusion that Wiki allows us to embrace change to an unprecedented extent.
With Wiki, each page is equipped with a complete history of every edit. This allows us to freely plumb the past and move forward knowing that no good idea or innovation is lost. We can feel free to make changes secure in the knowledge that our work will be recognized for its own merit and that it will become the foundation for further effort and construction.
"One's words are a gift to the community. For the wiki nature to take whole, you have to let go of your words. You have to be okay with that. This goes into the name, called Refactoring. To collaborate on a work, one must trust. The reason the cooperation happens is we are people and it is deep in our nature to do things together." -- Ward Cunningham, quoted in Corante; On The Crucible of Creativity", 17-October-2005
Contributing to a Wiki is an exercise in trust. You must trust the community to engage positively and productively with you in your work, and in our staff to protect your work. Trust grows with time and experience. Test us out by making a constructive edit or building out your own page, then watch the result: recognition, and the knowledge that you have helped build the commons.
We believe that people and organizations take you seriously sooner when you act with responsibility as a real person. Using your real name, backed up by things like your picture and interests, makes real-world interactions in culture, politics and business possible, realistic, effective and useful. Isn't a person more likely to join a community online, if they see that there are real people involved, instead of characters like RedDog88, Snivelcritter, etc.?
Professionalism, trust, and community all emerge when real people are involved, standing behind their work. Using your real name substantiates your commitment to transparency and allows others to better collaborate with you. It also creates a greater investment in your work.
Using a real name, however, is not a requirement for participation -- look around, get your bearings, and once you've come to know the vibrant, trusting community at ICANNWiki, make the switch.
Refactoring is a term common to computer programming for reorganizing and improving the internal structure of a program while retaining its exterior functionality and behavior. In the world of wiki, it refers to reorganizing and improving a wiki page while staying true to its function and the intent of its community of editors.
Wiki vs. Web: Refactoring vs. Commenting
Generally, when you're reading something on the web that isn't quite right, you lack the ability to fix it. On Wiki, you have the ability to reorganize and improve the page in front of you. You can Be A Builder and make Efficiently Expressed Suggestions. You have the power, but remember, in the words of Peter Parker, with great power comes great responsibility.
Transparency involves our commitment to openness and accountability. Transparency builds trust. If you are using a false name, not your own, people may wonder why. It may not be desirable to reveal everything about yourself but a name is something to build upon. Communities can only really begin to develop if the members of that community know each other.
Using references is an important part of keeping our content transparent. If you make statements on a wiki, especially bold ones, you should be able to back them up with verifiable references.