| Editing: (07:58, 29 October 2009 (UTC)) This page is being edited by LeadMan: your comment...|
If this note persists without edits in the history, feel free to remove the Editing template from the page.
Period 2009-10-15 to 2009-10-28
Small and simple virtual keyboard for OpenMoko FreeRunner, inspired from fatfingershell. The idea was to use XShape extention to display the virtual keyboard above the terminal
xminimokostatus is the background on the root window of Minimoko, a fast and lean Desktop based on shr, openbox and idesk using DBUS in C with glib
ffalarms is a finger friendly alarms application. Notes:
web-manager provides a web-based management console to the Neo Freerunner. It can do it for any phone on which you can manage to run it but it is developed for and on a Neo Freerunner. At this time the following features are implemented:
Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc..
- gry* Illume Theme 0.2 and gry* Elementary Theme 0.8 released.
- fast as hell! (as fast as the nEo themes, probably faster in some situations)
- shiny, inspired by the b&w smooth as silk theme
- survive opkg upgrade
- are still beauties even with software_16
- integrate well with default shr etk theme
- allow 'launcher' users to use dark as well as bright backgrounds while maintaining labels readable
- flower power! (the flowers were removed due to environmental reasons, but i still like to think the theme is powered by daisies and sunflowers)
Questions/Suggestions should be posted here
- Amit Abhishek wrote a nice review about Neo FreeRunner on his blog. It might be a good lecture for those hesitating to buy FreeRunner.
- 2009-11-08 LinuxAlt Lecture about Openmoko and community meeting.
- 2010-02-6/7 FOSDEM sign up to Fosdem 2010 if you're going to be there and tell us what you're willing to do
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.
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.
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.
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.