Task:Defining maemo
(→Tasks) |
(→Objectives: * Document processes in maemo.org) |
||
| Line 7: | Line 7: | ||
* Produce an initial Who is Who in maemo.org based on the user profiles, to be expanded in a decentralized way. | * Produce an initial Who is Who in maemo.org based on the user profiles, to be expanded in a decentralized way. | ||
* Produce a list of remarkable maemo projects. | * Produce a list of remarkable maemo projects. | ||
| - | |||
== Tasks == | == Tasks == | ||
Revision as of 20:23, 26 June 2008
 |
This article is continued discussion from the maemo.org brainstorm Please see the 100 Days agenda for more. |
Contents |
Objectives
- Define maemo, maemo.org and Internet Tablet OS / OS2008.
- Identify the blocks of the maemo software architecture and the projects behind.
- Define the roles of Nokia, the maemo community, the open source upstream projects and other organizations related to the maemo platform i.e. companies and universities.
- Produce an initial Who is Who in maemo.org based on the user profiles, to be expanded in a decentralized way.
- Produce a list of remarkable maemo projects.
Tasks
Help is welcome in all of them.
Completed
- Define the Maemo brand.
- Bug
maemo white paper architecture picture needs to be updated(WONTFIX)
Ongoing
From the maemo.org June sprint:
- Publish a "Who's who in maemo", including Nokia engineers working with the community, contractors and volunteers. Encourage people to update their information to keep the document up to date - Dave
- Documenting companies involved in maemo development - Dave
- User profile improvements defined and started + bug Automatic data in user profiles - Oskari
Backlog
- Task:Components and packages that define Maemo - Soumya
- Task:Upstream projects Maemo relies upon - Volunteers needed
- Task:Remarkable community projects around Maemo - Volunteers needed
Discussion
What is maemo
Discussion moved to Task:Maemo brand.
Describing the maemo community
Many people see the maemo community as a group of people having Nokia as a counterpart. A more accurate picture would:
- Have Nokia as a community player, describing the activities that are done at a community level.
- Show the relationships with related upstream projects: where the collaboration is happening beyond just using the free software provided.
- Add the many organizations involved in maemo development or research, from companies to universities.
Also, what about
- Go a bit deeper inside the "group of people" and identifying core contributors: more work on karma and user profiles would be needed.
Now the most visible are the one shouting louder and more often. It would be useful though to identify key contributors in the many community areas: application development, platform hacking, documentation, support, bug reporting, news, marketing... --qgil 05:57, 5 June 2008 (UTC)
--From a practical point-of-view, isn't maemo pretty much completely dependent on Nokia right now? Are there any viable non-Nokia maemo platforms out there? How much core development is not directed by the Nokia mothership? Claiming independence is counterproductive if it isn't tied to reality. - mee 04:28, 7 June 2008 (UTC)
Categorise the Community - thoughts
The section above describes Maemo's place in the greater community. However, who is maemo serving? (this may be a start on going a bit deeper)
Tech Level 1:
- Users : Windows/Mac desktop users who bought an N800 and want new wallpaper, a neat clock etc.
Tech Level 2:
- Power Users : Install more apps, alternative launchers, alpha/beta sw, up to new distros (eg Debian). More complex networking, ssh, scripting, python, documentation...
Tech Level 3:
- App Developers : Porting/writing gui apps and daemons; may want api info. Need to get to know the various environments.
- WM Developers : Starting to hack on gtk or QT4, the X server etc etc
- Kernel Developers : Fixing kernel bugs, tweaks, backporting, hardware support.
Each of these user types needs information : even an experienced kernel hacker will want to know the current best practice to setup the dev environment (SB1 or 2?) More importantly pages should be written with an awareness of the target tech level.
Whilst thinking about the levels of user involvement I thought that we could help users self-categorise using some old Doom terms: "Easy", "Bring it on", "Hurt me". Saves newbies complaining when they start down a path labelled 'Hurt me'... lbt 10:47, 12 June 2008 (UTC)
Building a strong brand
Discussion moved to Task:Maemo brand.