Community Updates/2009-10-28

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(doopa: Update about the community survey)
(H:1)
Line 26: Line 26:
 
Other={{unknown}}
 
Other={{unknown}}
 
}}
 
}}
 +
{{DistributionBox|
 +
Name=Hackable:1 [rev5]|
 +
Description=Hackable:1 is a community distribution for  hackable devices like the Neo Freerunner. It is based on Debian and implements the GNOME mobile platform. See Architecture for details.
 +
 +
The goals are:
 +
 +
    * provide a Stable platform for development
 +
    * encourage Quick start
 +
    * enjoy Ease of development |
 +
Screenshot=http://www.hackable1.org/wiki/Screenshots|
 +
Codename='chuck'|
 +
Homepage=http://www.hackable1.org/|
 +
Image=[http://www.hackable1.org/wiki/Image:Screenshot-today.png]|
 +
TestedOnHardware=Freerunner|                              <!--Neo, FreeRunner-->
 +
Neo1973={{yes}}|                            <!-- yes-->
 +
FreeRunner={{yes}}|
 +
HTC-Dream={{unknown}}|
 +
Other={{unknown}}
 +
}}
 +
  
 
==Applications==  
 
==Applications==  

Revision as of 00:52, 16 October 2009

Need improvement: This article or section needs improving. Feel free to add content.
NOTE:
  • Take a moment and look at Discussion page to get a clue on how to contribute to Community Updates while following OM wiki editing guidelines please.
  • I you are planning longer edition, please use {{Editing|your_username_here|date_here|editing_summary_here}}tag. Remember to remove/comment out it right after you save your work.
  • Please fill in everything you think the community should know.
  • On 2009-10-28 this content will be _moved_ to http://wiki.openmoko.org/wiki/Community_Updates/2009-10-28, feel free to do it.
  • Post a note about CU release on the community mailing list.


Contents

Period 2009-10-15 to 2009-10-28

Distributions

System boot.png Distro Name [version]

Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.


Codename: 'codename'
Homepage: http://www.homepage.org
Image: images

{{{Works}}}

150px Hackable:1 [rev5]

Hackable:1 is a community distribution for hackable devices like the Neo Freerunner. It is based on Debian and implements the GNOME mobile platform. See Architecture for details. The goals are: * provide a Stable platform for development * encourage Quick start * enjoy Ease of development


Codename: 'chuck'
Homepage: http://www.hackable1.org/
Image: [1]

{{{Works}}}


Applications

New Applications

System boot.png Exampleapp 0.0.1

Exampleapp 0.0.1 is an application to do some stuff..


Homepage: http://wiki.openmoko.org/
Package: Exampleapp
Tested on: SHR-Unstable,Om2009T5


Application Updates

System boot.png Exampleapp 0.0.1

Exampleapp 0.0.1 is an application to do some stuff...

  • new example feature 1
  • new example feature 2


Homepage: http://wiki.openmoko.org/
Package: Exampleapp
Tested on: SHR-Unstable,Om2009T5


Community

Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc..

Event News

Openmoko Development Survey

Kerstin from Open Innovation Projects has completed a survey on the influence of open source development in the openmoko project. The full results are available here: http://open-innovation-projects.org/openmoko-survey-results/

The results of the survey shouldn't be too much of a surprise given the nature of this particular project. The overwhelming majority of respondents agree with statements like "I really care about the fate of the project" and "I enjoy being part of this community". The community is mostly male, young (average age = 30) and well educated with over half of respondents indicating they have at least a university level degree.

Work Distribution

With regard to the split between developers and users, the community seems to be led by a small number of lead developers committing the majority of the work. The largest group indentify themselves as part of the community with just under a third identifying themselves as end-users.

Documentation

Access to documentation is important for the members of the openmoko community. The level of access granted to the community is satisfactory with over half of members indicating a strong degree of satisfaction with the level of access to software documentation and just under half for the hardware documentation. The community is satisfied with the ease of access to the community documentation with less than 5% of respondents finding it difficult to access software/hardware documentation. The community documentation is deemed to be useful by the majority of respondents. However, the number of respondents finding it difficult to contribute due to lack of information suggests a disparity between the perceived ease of access and value of documentation and the breadth of coverage. Few respondents were completely satisfied by the available information. The story is a little worse for 3rd party documentation as is to be expected. This can be considered an area for improvement. The level of access granted to documentation has a bearing on the satisfaction of developers as shown by the level of satisfation with the completeness of the documentation.

Community Influence

Despite the fact that few respondents indicated a leading role in the development of software and identified themselves as end users or community members they majority felt they were able to influence the direction of the project. This indicates that the lead developers are listening to users and there seems to be a high level of satisfaction amongst users with their ability to influence the direction of development.

Personal tools
Need improvement: This article or section needs improving. Feel free to add content.
NOTE:
  • Take a moment and look at Discussion page to get a clue on how to contribute to Community Updates while following OM wiki editing guidelines please.
  • I you are planning longer edition, please use {{Editing|your_username_here|date_here|editing_summary_here}}tag. Remember to remove/comment out it right after you save your work.
  • Please fill in everything you think the community should know.
  • On 2009-10-28 this content will be _moved_ to http://wiki.openmoko.org/wiki/Community_Updates/2009-10-28, feel free to do it.
  • Post a note about CU release on the community mailing list.


Period 2009-10-15 to 2009-10-28

Distributions

System boot.png Distro Name [version]

Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.


Codename: 'codename'
Homepage: http://www.homepage.org
Image: images

{{{Works}}}


Applications

New Applications

System boot.png Exampleapp 0.0.1

Exampleapp 0.0.1 is an application to do some stuff..


Homepage: http://wiki.openmoko.org/
Package: Exampleapp
Tested on: SHR-Unstable,Om2009T5


Application Updates

System boot.png Exampleapp 0.0.1

Exampleapp 0.0.1 is an application to do some stuff...

  • new example feature 1
  • new example feature 2


Homepage: http://wiki.openmoko.org/
Package: Exampleapp
Tested on: SHR-Unstable,Om2009T5


Community

Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc..

Event News

Openmoko Development Survey

Kerstin from Open Innovation Projects has completed a survey on the influence of open source development in the openmoko project. The full results are available here: http://open-innovation-projects.org/openmoko-survey-results/

The results of the survey shouldn't be too much of a surprise given the nature of this particular project. The overwhelming majority of respondents agree with statements like "I really care about the fate of the project" and "I enjoy being part of this community". The community is mostly male, young (average age = 30) and well educated with over half of respondents indicating they have at least a university level degree.

Work Distribution

With regard to the split between developers and users, the community seems to be led by a small number of lead developers committing the majority of the work. The largest group indentify themselves as part of the community with just under a third identifying themselves as end-users.

Documentation

Access to documentation is important for the members of the openmoko community. The level of access granted to the community is satisfactory with over half of members indicating a strong degree of satisfaction with the level of access to software documentation and just under half for the hardware documentation. The community is satisfied with the ease of access to the community documentation with less than 5% of respondents finding it difficult to access software/hardware documentation. The community documentation is deemed to be useful by the majority of respondents. However, the number of respondents finding it difficult to contribute due to lack of information suggests a disparity between the perceived ease of access and value of documentation and the breadth of coverage. Few respondents were completely satisfied by the available information. The story is a little worse for 3rd party documentation as is to be expected. This can be considered an area for improvement. The level of access granted to documentation has a bearing on the satisfaction of developers as shown by the level of satisfation with the completeness of the documentation.

Community Influence

Despite the fact that few respondents indicated a leading role in the development of software and identified themselves as end users or community members they majority felt they were able to influence the direction of the project. This indicates that the lead developers are listening to users and there seems to be a high level of satisfaction amongst users with their ability to influence the direction of development.