Dota Imba Legends v2.0.w3x It is on the source of the agreements, it is merely a description ofthem, Of course, if it is successful, people will stan citing it as a source of authority in itself; but that just means it reflects the overall will of the group accurately. This is the document alluded to in the section called "Developer Guidelines" in Chapter 2, Getting Started, Naturally, when the project is very young, you will have to lay down guidelines without the benefit ofa long project history to draw on. But as the Dota Imba Legends v2.0.w3x development community matures, you can adjust the language to reflect the way things actually tum out. Don't try to be comprehensive, No document can capture everything people need to know about participating in a project, Many of the conventions a project evolves remain forever unspoken, never mentioned explicitly, yet adhered to by all. Other things are simply too obvious to be mentioned, and would only distract from important but non-obvious material. For example, there's no point writing guidelines like "Be polite and respectful to others on the mailing lists, and don't start flame wars," or "Write clean, Dota Imba Legends v2.0.w3x readable bug-free code."