Clarify the different architectures of participation (and where they fit)

[hsenot]

Make sure that all audiences are being catered for:

• coders,
• functional experts,
• explorers,
• ...

Each one should have a serious long-term purpose (why you do that), articulated in a engaging/playful way (how you do that).

[hsenot-admin]

Task / activity types (these might evolve as the community transitions from development mode to user mode):

• website code (fix and enhancement): => become a contributor to the GitHub project
• add a new building to the building spatial layer => draw a building in OSM using their OSM username
• add building details => enter data using the dedicated building form
• scout out information about energy efficiency projects in Australian buildings => send an URL to a dedicated email address
• add energy efficiency project data => structure the data from a source into the project section
• verification task => make sure the data entered is correct (cross-check, contact someone, etc ...)

More user-oriented tasks:

• contributing enhancement / fix ideas => adding a "code" task
• contributing content in the forums / FAQ => in the dedicated pages

Byte-sized task make it possible to just take any of it from anywhere (what could be mobile?) and move things forward. It's all about reducing the friction to contribution, allow all users to be contributors.