Wiki Plan

We should layout some goals for the wiki. What scope should it have etc.

**So far **

To Do

Separate wiki content into three clearly distinct areas (two different themes?) i.e. end-user, engineering (we could split 'engineering' into development / service management) and community development (noting the wish below for a marketing space)
Installation instructions -- yes, I know they are elsewhere, too.
Unit tests -- tests/ui is referenced but missing
API -- documentation / wishlist for an API (see this presentation)
Data migration -- migrating data from other silos (such as Facebook) / ideas that will also relate to DataPortability.org
Backup & Disaster Recovery -- tips/tricks/how-tos
Security optimisation -- testing/fuzzing tools to audit Diaspora security such as Ronin
Scalability - how-tos etc., getting ready for large scale solutions / systems i.e. 1000s of nodes (see High Scalability)
Marketing / getting the word out - How we're going to clearly communicate the benefits of Diaspora to the people who would be interested but aren't using it... yet!
As per other open source initiatives it will be good to have a 'code of conduct' to refer to when issues arise, KDE has a good one we could learn from.

Please add pages you would like added, including a brief outline of the scope of that page.

Provide feedback