NOTICE: This wiki will be down for maintenance on Tuesday May 22. For more information, please see http://opensourceecology.org/wiki/CHG-2018-05-22

12 Commandments of Collaborative Literacy

From Open Source Ecology
Jump to: navigation, search
  1. Work in the cloud. Make all documents accessible via a web link so a person can view things online. This minimizes any issues related to file downloads and viewing of downloaded files.
  2. Work with editable documents. The only constant is change. Why should documents be static? New versions should
  3. Work with collaborative documents. Multiple people can view and edit at the same time, to leverage collaborative development.
  4. Use versioning. Under the assumption that all documents evolve, use versioning systems to allow for tracking of change. For example, this wiki has version history, and files within the wiki have a version history as well.
  5. Keep a public work log. This allows anyone to see what you are doing to help you and to collaborate with you. This should be public, such that even uninvited collaborators can contribute. Document all that you do on your work log. If you are working as part of an open team, this is the only way that everyone else will know what you are doing. This includes common use of embedding other content.
  6. Use open source and libre software. Only with non-proprietary, open source software are you assured universal and permanent access to software. This allows universal collaboration opportunities, including those people who would otherwise not be able to afford the software. These also provide the 4 Freedoms. This also avoids the risk of running malware on your computer, as potentially any non-libre software can be malware without you knowing it.
  7. Publish early and often. Do not wait until you have a final product to publish your work, because a product is never finished. It can always improve or be adapted further. Do not worry about publishing confusing information. The culture of logs is that stuff should be messy, as the creative process is messy.
  8. Use standard information architecture for documentation. Documentation should be structured so anyone can find out anything about any topic of development.
  9. Use standard development protocols. OSE is developing common protocols for open source product development. This allows everyone to be on the same page regarding the development process, and allows different teams to tag-team on problem solving.
  10. Use the official Development ISO for universal compatibility. OSE will release its official OSE Linux distribution containing all commonly used software (FreeCAD, LibreCAD, Kdenlive, Blender, Pronterface, GIMP, QGIS, KiCad, etc). This is intended to eliminate all possible software cross-platform incompatibilities.
  11. The final product of development work is creation of open hardware as a basis for Distributive Enterprises
  12. The goal of Distributive Enterprise is mass creation of right livelihood as the next economy.