View source for Community transition
From Openmoko
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to Community transition.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Return to Community transition.
Sean Moss-Pultz (CEO of Openmoko Inc.) decided that the best path forward for the phone business is to turn the future of the Freerunner over to the community. (See the announcement for details)
In brief :
List here for what kinds of things OM can do to smooth this transition.
With the transition alot of work is awaiting the community. This list gathers all neccessary tasks to keep the freerunner alive. If you want to serve the community, here is the place to find out what help is needed.
The kernel will be maintained by a group of volunteers. They have received commit rights to the kernel repository.
These are the most important bugs that need to be fixed now.
This is the complete report with all the bugs (some of them might be invalid, please ask on IRC or in the mailing list before trying to fix one).
There is a current ongoing effort to get basic GTA02 support in the mainstream Linux kernel, the patches have been sent. Once this basic support is ready other drivers can be submitted as well. Many of the drivers need additional work to be suitable for upstream inclusion.
There are still Freerunners available for purchase. According to Sean's email there are plenty of the A7 in stock.
For North Americans experiencing the buzz on their phones, SDG Systems will be running a buzz repair service. The phones must be sent to SDG no later than July 15th, 2009. See this email for details.
No. Openmoko Inc. has committed to continuing to support the community by funding the resources available on openmoko.org.
From Sean's email announcement: "Openmoko Inc. then will act as the sponsor of this effort. We will continue to fund all necessary server infrastructure..."
Discussions have started to create an organization of Openmoko community members to continue the work started by the company.
(This is all pre-alpha. Feel free to get involved by changing things up and making additions.)
In order for development to continue on the Freerunner and any potential successors, the community needs to create an organization that can facilitate the project. We need an organization that will:
Jon 'maddog' Hall has offered for the Openmoko community to operate as a sub-group of Linux International. The offer has already received some support on the mailing list.
The Gta02-core team is currently working on an improved version of the Freerunner.
GTA02-core needs an organization that can finance and arrange for production.
Paroli and Om2009 were both lead directly by Openmoko Inc. The community organization could take over as sponsor of these projects.
Part of creating a new organization is developing a structure and set of processes for how decisions will be made. Developing the structure entails creating positions, board(s) and committees that will have authority over various parts of the organization. Processes should cover:
Process and structure are like the source code for an organization. Ideally we will develop processes that give all members opportunity to provide input, and do not become an obstacle to getting work done. It's important to remember right from the start that our goal is to foster development, not burden it down with bureaucracy!
This email from Jon on the openmoko-community mailing list contains some notes and advice on developing an organization that are well worth reading.