Introducing
Your new presentation assistant.
Refine, enhance, and tailor your content, source relevant images, and edit visuals quicker than ever before.
Trending searches
Solve problems
and answer needs.
with the N900 and Maemo 5, the community has split greatly to community members and developers and non-participating members are growing in number
Infinite possibilities together
Once united, all community members were there to learn, to teach, to participate in the community and develop themselves.
number of users = number of device masters = number of community members = number of developers
with the introduction of Maemo 6 and a consumer grade Maemo device, how do you lay out a clear path for users to learn, participate and develop?
List of auto featured for 3 domains
Dashboard
your actions
your initiated actions (e.g. bugs, brainstorm, questions)
Participation path
Path for OSS devel-test-publish
Learning path
breadcrumbs for paths
Path for testing
easy movement between bugs and brainstorms
Path for reporting
leads to an action
leads to an action on selected solutions
Any path should be on limited steps, as process reacts slowly to everychanging environment.
Concentrate on trying to bring it down to Issue - action pairs. [issue can represent learning step, brainstorm idea/solution, bug, championing topic]
Path for proposing
Publish
Intro to Maemo community
Promote it
Beginner
Get help
Power user
Updates
Report it
Test it
Champion it (take the task)
Documentation
Learn development
Intro to Maemo
Propose it
Learn to be a community member
Council
Updates
Updates, featured
Ask for help
Developer
Write it
See the samples
Discuss it
Community champion
Intro to Maemo development
Community member
Set up your environment
Overall action handling system, with dependecy and grouping possibility!
Karma system
based on learning actions taken
promotion tasks taken
reports
proposals
testing
writing
champion tasks
council tasks
development
can be used for
Standard action definition:
- title
- description
- owner
- status
- deadline, priority
(contributors?)
(comments, logged history)
(dependency on other actions)
actions can be taken up by Nokia, council, champion, developer (role to be visible, so users can understand)
actions can be dropped
log of action statuses and ownership
NO deadline? how to avoid too much formalization
you can only volunteer for actions?
std action statuses:
- draft
open
work in progress
closed
cancelled
On any issue or action,
you have stakeholders.
Stakeholder is practically
a notification list,
usually interested in:
- status changes
- deadline changes
- ownership changes
Standard issue definition:
- title
- description
- who opened the issue
- severity
- defined actions
- status
(comments, logged history)