# Wiki Issues

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.

• 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)

### Redundant Pages

• I suggest merging the editing help pages:
• applications:

### Pages proposed for deletion

Please help cleaning these: Check if there is a red (nonexisting) link in this table, click it, click "What links here" in the toolbox and update the broken links. When done, remove the deleted entry from this table.

Nothing is propsed for deletion at the moment

### 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.)

## Categories

Main article: Category talk:Categories

## CSS

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 : http://wiki.openmoko.org/wiki/MediaWiki:Common.css . 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: http://en.wikipedia.org/wiki/Help:Monobook MinhHaDuong 12:26, 12 September 2008 (UTC).

• The gutter is too wide
• 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

## Portals

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)

(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.

References

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

### Disappearing Pre-formatting

There is an issue with pre-formatting disappearing when people edit. See for instance recent edits here:

Actually I thing it's whitespace in general that is lost since python/ruby code is also messed up. I have confirmed that this happens cross browser (both firefox3 and opera), but not on all pages, and not for all people.

Gromgull 10:47, 9 November 2008 (UTC)

Yes, it is driving me bananas and must me due to some hook the maintainers have added.

In standard MediaWiki, a mere space at the beginning of these lines
will produce this box. But no, here on this wiki, one needs

<pre> , and your spaces get eaten.
The problem can be isolated as even returning mangled code in the edit box when you hit
the preview button. Never on real MediaWiki has anything dared to return a mangled edit box before.
Indeed the contents of this very paragraph have been jumbled by it. I have no control. Indeed, do
you see that gap above? It grows with each edit.

On the wikis I maintain, I never go hog-wild adding too many hooks.

This bug got me. I managed to fix the page I accidentally broke, but apparently it causes the preformatted text to slowly sink into ordinary text with each edit, making the wiki less readable, for example see: http://wiki.openmoko.org/index.php?title=GPRS_FSO&oldid=55571 and http://wiki.openmoko.org/index.php?title=GPRS_FSO . This should be fixed ASAP, as it makes the quality of the wiki do down. :-( zub 00:47, 18 November 2008 (UTC)

#### Emergency: eating categories off the bottom of pages

##### Proof of Category eating

...Oh, the categories only disappear temporarily, due to http://www.mediawiki.org/wiki/Extension:SelectCategoryTagCloud . OK, sorry for the alarm. Jidanni 04:08, 16 November 2008 (UTC)

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

• Math - the Tex math markup does not work currently. Test:
• $z =\left (1-\left(\frac{P_{ind}}{101.325}\right)^{0.190263} \right ) \times \frac{87.828}{0.00198122}$
• $P_{ind}$
• Syntax Highlighting - makes code much more readable
• 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:

OpenmokoIT still do some research now. coolcat

## 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: http://www.mediawiki.org/wiki/Multilingual_MediaWiki Also, the correspondence between translation should be maintained with tags: http://en.wikipedia.org/wiki/Help:Interlanguage_links 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)

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]