View source for Wiki Issues

From Openmoko

Jump to: navigation, search

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Administrators.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page:

Templates used on this page:

Return to Wiki Issues.

Personal tools

If you think something is wrong with a Wiki page, please fix it. If the problem is larger with this Wiki in general, please add your thoughts on this page and mail the openmoko documentation mailing list. You may just want to read existing proposals and put your vote on them, Wiki Maintainers will appreciate. Wiki Maintenance Agenda.

When adding an issue please

  • Provide a reason
  • Provide your name as vote for the action to be taken (you can automatically enter your username by typing "

~~~ ")

WARNING: Comments without name might be deleted without consideration. We may need to ask for more information before implementing a proposal. Thanks for understanding.

Accepted and implemented requests should be deleted. Rejected requests should be moved to the bottom of the page to avoid requesting them again.

Wiki Pages

I think that we should use specific "editor's notes templates" rather that nominate individual pages here. We can make automatic list of pages using a given template by having a Category:X tag inside the template. See for example the Category:ToDo . MinhHaDuong 09:44, 7 October 2008 (UTC)

Pages capable of development

Redundant Pages

Tidy up

Pages proposed for deletion

This is a place for proposing pages of this wiki for deletion and discussing the proposal. See Openmoko Wiki Editing Guidelines#Deleting pages for details.

Old proposals

These pages were proposed for deletion before the new policy was introduced. Please continue the discussion in the appropriate sections below

Page Reason Yes kill it votes No keep it votes
gsmd outdated (according to Mickey), not updated for over a year Marko Knöbl,(I vote "yes", if it is for sure, not used anymore.How can we check it?-LeadMan)
Neo FreeRunner case all relevant information has been moved to the page CAD models Marko Knöbl,LeadMan
FreeRunner unable to work with 3G SIM cards This problem has been fixed a long time ago with the new GSM firmware Marko Knöbl,LeadMan
Wiki Maintenance Agenda It is duplicating the efforts of Openmoko Wiki Editing Guidelines Marko Knöbl,LeadMan
Roadmap/Telephony Outdated, never updated. Marko Knöbl,LeadMan
Migration to bad block tolerant builds Outdated, not relevant anymore. Marko Knöbl,LeadMan
Building Openmoko from scratch (pre-BBT) Outdated, not relevant anymore. Marko Knöbl,LeadMan
Application UI Design Recommendations Outdated Marko Knöbl,LeadMan
SMSTool Outdated Marko Knöbl LeadMan
Om 2009 get active Outdated Marko Knöbl,LeadMan
Summer of Code 2007 Old ideas, some parts already implemented. Content not modified since ~2007 (only minor fixes) LeadMan
Summer of Code 2008 Old ideas, some parts already implemented. Content not modified since ~2008 (only minor fixes) LeadMan
Openmoko 2008 Summer Intern Program/zh tw No English version, looks like connected with Summer of Code 2008-so maybe not needed anymore, might be wise to contact with authors before deletion, content not modified since ~2008 (only minor fixes)--LeadMan LeadMan
Personas Outdated, this was intended to help the Openmoko team develop the right products. LeadMan


Neo FreeRunner case

Problems with certain SIM-cards

I think most information concerning problems with some SIM-cards can be deleted. This problem has been fixed a long time ago with the new GSM firmware (see GSM/Flashing). Therefore I'm proposing to remove most of the page FreeRunner unable to work with 3G SIM cards (just leaving an explanation of the problem there, and redirect pepole who might have bought a FreeRunner with an older firmware to GSM/Flashing), delete Carriers, Carriers/Rogers and the section of "Status of AT&T SIM Cards" in Carriers/ATT. --Marko Knöbl 16:17, 8 February 2010 (UTC)

Wiki Maintenance Agenda

I'm proposing deleting the page Wiki Maintenance Agenda. It is duplicating the efforts of Openmoko Wiki Editing Guidelines --Marko Knöbl


I'm proposing Roadmap/Telephony for deletion. It's showing the outdated roadmap from 2007-12 which was never updated. --Marko Knöbl

missing bad block table support

The earliest software for the Neo 1973 did not support bad block tables. As this issue is not present anymore I think the associated pages can be deleted: Migration to bad block tolerant builds, Building Openmoko from scratch (pre-BBT) --Marko Knöbl 19:12, 11 February 2010 (UTC)

Application UI Design Recommendations

This comes from the time when there was only one official Openmoko distribution. These recommendations are not relevant anymore. --Marko Knöbl 19:23, 11 February 2010 (UTC)


  • This is a very old, unfinished program. --Marko Knöbl 19:44, 11 February 2010 (UTC)
  • We should take care for source code of SMSTool before deleting this page. I know it is python, but it would be waste to loose the code. --LeadMan

Om 2009 get active

Outdated, Om 2009 is not developed anymore --Marko Knöbl 19:53, 11 February 2010 (UTC)

Pages that especially need work

Application pages

Maturity level ideas from the documentation list copied by Kempelen 19:05, 1 October 2008 (UTC):

  • It might be nice to have a single word stating the code maturity, perhaps only 3 simple options like prototype, functional, mature
  • Why not stick with pre-alpha, alpha, beta, stable, mature

Decision postponed. :-) (Feel free to vote here anyway.)


Main article: Category talk:Categories


We have discussed design on the mailing list, with the conclusion that revising was not a big priority. However, the wiki should be skinnable from user-space by editing : . And for development, each user can have his/her own CSS to eat his own dogfood. But I can't seem to make this feature work here. Reference: MinhHaDuong 12:26, 12 September 2008 (UTC).

  • The gutter is too wide
  • Too much footer's padding
  • Could shave 1 or 2 em of vertical space in the header
  • The tabbed navigation layout is non-standard (no framing effect)
  • The search box is below the fold (depends on window height of course)
  • The toolbox (bottom left) has no border
  • Mediawiki's user personal toolbox is prohibited
  • Too many links in the navbar that belongs to the home page but not to every page


We should explore another wiki organization tool: portals. A portal is an introductory page for a given topic. It complements the main article of the subject by introducing the reader to key articles, images, and categories that further describe the subject. Portals also help editors find related projects and things they can do to help. MinhHaDuong 13:53, 20 September 2008 (UTC)

Navigation templates

(FYI Description moved to Openmoko_Wiki_Editing_Guidelines#Navigation_templates, Kempelen)

  • The Distributions page feature a non-templated navigation box
  • We should name these templates distinctly. I suggest using a prefix like "NavBox:".
  • Visual design is by hand (not CSS), and not beautiful
  • Need to test positioning at bottom of article.


First discussion in the mailing list (Note: in the middle of a thread about left navboxes)

  • Yes votes: Kempelen (For real wikipedia like navigation templates at the bottom, not at TOC position, we should move this section to editing guidelines as soon as template implementation improves a bit. Do not delete this please!)

DolfjeBot1 proposals

Their is a bot on the openmoko wiki that's controlled by User:Dolfje. If you have tasks for the bot, please put them here. A request has been made to tag DolfjeBot1 user account with the 'bot' flag. Here is the lists of users with permissions at the necessary `bureaucrat' level.

Wiki engine issues

Can we please install/fix the following features for this wiki:

Report to Openmoko IT on 26,Dec 2008. You can check for detail.
  • GraphViz works with the commonly known dot language - it allows us to draw graphs using easy markup.
  • AnyWikiDraw allows us to draw svg diagrams directly on the wiki page.
  • Make visited links a different color.

Change Sitename

The name of this wiki is currently "Openmoko". I think it should be "Openmoko Wiki" for the following reasons:

Yes votes: Marko Knöbl, Minh

No votes:

OpenmokoIT still do some research now. coolcat
Then fix the search function (by restoring the standard MediaWiki search function). Anyway they are Special:Allpages/Openmoko:. Anyway, any links like Special:Allpages/Openmoko: will break, unless you use Special:Allpages/Project:. Furthermore, the longer the name of the Project ($wgSitename) becomes, the longer the UTF-8 translations of it will become, and as e.g., for Chinese UTF-8 at 3*3=9 ASCII %XX%XX%XX per character, you'll end up with mile long URLs before long, that is if one day the site becomes fully translated. Jidanni 01:04, 22 November 2008 (UTC)

Organize translations

I suggest moving the translations to sub-wikis, like the way wikipedia does it. Currently all translations show up in searches and under category-lists. --Johndoesacc 12:03, 25 August 2008 (UTC)

+1. See issues and solutions for a multilingual mediawiki at: Also, the correspondence between translation should be maintained with tags: The request has been heard but maybe not in the right places. What is the best operational frequency to ping the hosting engineers for that ? MinhHaDuong 13:02, 10 September 2008 (UTC)

After discussion on the Documentation ML, sub-wikis are out. We want to try namespaces. MinhHaDuong 09:31, 7 October 2008 (UTC)


Symlinks in download directories

This is not strictly Wiki issue, but discussed on the documentation list as being a serious usability disadvantage. Symlinks and .tar.gz files should be removed from the release directories because they confuse users. Ref: [1]

Improve README.html


It should at least link to: Om_2008.9_Update#Download_and_Flashing

Rejected requests

When a requested Wiki Issue is voted for not to be done, it must be moved here, to make sure it won't get continously requested again.

  • Don't translate the wiki - rejected proposed by Minime August 2007, moved to rejected by Kempelen August 2008: the Documentation Team looks to support the idea.
  • Use namespaces to separate user-oriented and developper-oriented content. Assuming the default namespace is user-oriented that would exclude developper-oriented pages from searches (unless the user ticks the box, but who does ?). And it can't be done purely in the wiki, it needs admin time. Better to use categories and a prefix in the page name (like BlendeWiki). MinhHaDuong
  • Use category pages instead List Pages Good list pages are allowed and encouraged, as the documentation team today agreed on the mailing list. Kempelen 21:27, 30 August 2008 (UTC)