License – Open source. It’s free (BSD) and you can contribute to the project.
- BSD License (3 Clause)
The Open Source Advantage
- Four main points:
- Collaborative development
Open source projects hinge entirely on contributors.
Social Architecture – building an Open Source community
- A successful community recognizes problems and organizes itself to solve them.
- 5.5 (main release, annual)
- 5.5.2 (bug fixes)
- Web accessibility matters.
- Standards Compliance
- Markup and Stylesheets
- 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
- 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 forum and the newsgroup
- Contribution of source code submitted to Bug Tracker
- Infrastructure: repository changelog, issue tracker, ...
- 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.
- we excel at doing stuff, and are lousy about talking about it
Who decides what happens?
- If something is not being done, it’s because no one has decided to do it.
- Development culture means that people work on what they’re interested in.
main advantages of WackoWiki
principles to maintain
- Principle – The LessIsMoreFeature to help against creeping featurism.
- uses a minimalistic approach
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
A good specification lets diverse people work together without confusion or conflict.
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.
the classic case of perfect being the enemy of the good
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
- One way to undermine social media monopolies is to refuse to contribute to the communicational economy they are based upon: don’t generate exploitable signals, stay quiet — and ask how this might be developed as a common response. Given the naturalized assumption that ‘more communication’ will automatically produce ‘more freedom’, suggestions, like this one, that are based on doing less of it might provoke hostility. However, in the case of the social media industries, communication is cultivated not in the interests of freedom, but in the interests of growth; social media wants to capture more of you through your transactions. Moreover, through this process communications are not made ‘more free’ but tend rather to become less open — certainly in the sense that they are commoditized. With this in mind, this paper asks if a media politics might be generated based on the potentials of silence, on speaking in tongues — and on relying on the resources of metaphorical language rather than on learning to speak or write in ways more amenable to code.