After a short opening to define the goals of the workshop and participants' introduction, the group started discussing how far are software development processes and tools from the wiki philosophy:

• Simple
• Open
• Incremental
• Organic
• Mundane
• Universal
• Overt
• Unified
• Precise
• Tolerant
• Observable
• Convergent

• Simplicity: code is more complex and formal, several languages, …
• Tolerance: “bad code” can easily break the “codebase”; test-coverage and tests must be reinforced;
• Openness: can be a problem in some communities/organizations
• Awareness of changes among…
• Different projects might have different requirements in terms of “wiki philosophy” (opensource, companies, …)
• Trust
• Granularity of “code changes” is different from “text changes”

We found interesting to have wikis satisfying the following requirements:

• support for both structured/unstructured contents
• wiki as a learning place: implicit links, explicit links
• search capabilities for software-specific contents
• wikis as “public spaces” for software projects
• to support software as if were “green fields” (freedom to play with)
• to support script-pages understandable by end-users
• internationalization/localization support
• how to motivate software developers to dump their knowledge (into wikis?)
• evolve wiki syntax to make it extensible and more powerful

• Ruby DSL's vs Structured wikis: will they merge?
• option for “always write-mode”?
• centralized vs distributed source repositories?
• 2011: study points that “self-named programmers” will increase dramatically soon…