!/Licence – Open source. Itís free (BSD) and you can contribute to the project.

  • BSD License (3 Clause)

The Open Source Advantage

  • Four main points:
    1. Availability
    2. Collaborative development
    3. Transparency
    4. Education

Open source projects hinge entirely on contributors.

Social Architecture – building an Open Source community

The 5 Types of Open Source Projects

Unix philosophy

nobody will do it for you (and therefore they will)

Release cycles

  • 5.0 (main release, annual)
    • 5.0.2 (bug fixes)
  • 5.5
  • 7.0

Semantic Versioning





  • together we have much more power to encourage other people to get involved and reduce fragmentation
  • we really have to pool our limited resources in an effective way 
  • breaking down the language barriers
  • building a good shared infrastructure
  • community before code

Teaching/Learning Community

  • The community of WackoWiki users should be respectful and cordial to encourage problem-solving and idea exchange, not ego-boosting, point-scoring, or one-upmanship.

Process of decision making

  • Open, Transparent Planning and Execution
    • Discussions over the mailing list and the newsgroup
    • Contribution of source code submitted to Bug Tracker
  • Infrastructure: Hg Changelog, BT, ...

Producing Open Source Software. Itís all about managing and promoting healthy open source developer communities.
How To Ask Questions The Smart Way


  • Politeness lets us learn from those we disagree with.
  • The more you know, the less you see.

Take a break. Perhaps youíve been working too hard. If so, resolve to take some breaks. Taking breaks can help you see the bigger picture, and spot important aspects of project development you may have missed. It also helps you to recharge.


main advantages of WackoWiki

principles to maintain

  • Principle – The LessIsMoreFeature to help against creeping featurism.
  • uses a minimalistic approach
  • JavaScript should not be required for basic usage (No reliance on JavaScript)

Simplicity Oriented Design

  • Design by removing problems, not adding features
  • Simplicity beats functionality
  • Discover the core problems
  • Solve them minimally
  • Use that to discover next set of problems

Community and roles

main language and how to enable participation of users not speaking English

intended Audience

Architectural Issues
A good specification lets diverse people work together without confusion or conflict.

Compatibility Concerns

Project Status
Upcoming Project Milestones
What we are currently working on
What needs to be done before R7.0
Collecting ideas for R7.0

RFC for WackoFormatter


Every time you provide an option, youíre asking the user to make a decision.

avoid high tool overhead

  • When your team starts routing around the tools you've offered them, pay attention: it may be a sign that you're offering the wrong tools.
  • The more we invest in structure and organization, the stupider we become.

Build small things

  • Small units of code are good. The smaller it is, the easier it is to understand.
  • Create and use simple, readable code