# Wiki Issues

(Difference between revisions)

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 maintain 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

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

Look & Feel and Look & Feel/de Look & Feel is now a redirect to Artwork which is a totally different subject - therefore many links are unintentionally leading to Artwork Marko Knöbl
Neo software stack only contains of one picture without further explanation Marko Knöbl This page is not implement.coolcat
Openmoko Local User Group, Talk:Openmoko Local User Group, Template:Usergroups duplicate of Openmoko Local Groups Marko Knöbl [Openmoko Local User Group]]had removed, and replaced with [Openmoko Local User Groups]].Template:Usergroupsis a template listed every user user groups page of wiki.
SH1, SH1/es outdated, information was about Neo 1973 shipment Marko Knöbl
SIM/de no english page Marko Knöbl English version move to GSM, So I delete the SIM page. And redirect SIM/de page to GSM/de too. Hope the translater can translate it.coolcat
Wallpaper I think this is too specific for this wiki Marko Knöbl
Installation_guide, Installation guide/it Empty Kempelen

## Categories

### General issues with categories

• There are way too many categories.
• The categories index is static and therefore out of date.
• The wiki index is another static categorization. It is therefore out of date. Moreover, it seems strictly hierarchical, while actually pages should be described with multiple categories, and categories can have multiple parents.
• There should be a small number of a orthogonal category trees, each describing one consistent conceptual taxonomy.
• Ideally categories should not include language, if we don't do so the list of pages is cluttered.
• There should be only one category taxonomy for the "Neo type" with subcategories "FreeRunner", "Neo1973", "GTA03"... Otherwise, categories should not include the Neo type.
• Another big taxonomy can be based on the layers model. "Hardware", "Drivers", "Operating system", "Framework", "Applications", "Distributions". With many subcategories here.
• A taxonomy of technical level of expertise "General public", "Beginners", "Users", "Experts".
• A taxonomy by function or by subsystem: "Phone", "Wifi", "GPS/GPRS modem", "USB", "Bluetooth", "Accelerometers", "Audio", "Power", "SD card", "Serial bus", "Display", "Accessories", "Debug board"
• A taxonomy by maturity: "Wishlist", "Experimental", "Unstable", "Testing", "Stable".

MinhHaDuong 10:47, 24 August 2008 (UTC)

### Too general category names

These categories end up in mixed content. They could be removed and content migrated to more specific category names.

Category:Technical Kempelen, Marko Knöbl

Status: Openmoko Inc related info from Openmoko to a new Openmoko Inc category. Openmoko, Documentation and Information categories has been renamed and articles reassigned.

### The Category:ideas

Problem 1: Many pages have Wishlist: in the title. This syntax is potentially confusing because there is no Wishlist: namespace. I suggest a mass rename from "Wishlist:(.*)" to "Wishlist/\1" ?

Problem 2: A significant minority of pages in the "Category:ideas" are missing the prefix in the title.

Problem 3: There are two templates, { { Wishlist } } and { { Unimplemented } } . Is that unnecessary redundancy, or is there a subtle distinction . MinhHaDuong 20:23, 30 August 2008 (UTC)

### Category structure

Please see that below, because it was too long to include here.

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

(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

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:

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

## Category structure discovering and planning

This is a discovery of the current category structure and notes about how it should be changed. Please contribute, add your comments what should be changed and how. Thanks, Kempelen

• I don't understand why this is done manually, there are tags for that (see in the Discussion page).
• Technical is meaning-poor. It looks like it's about the "Phone environment" in an ecosystemic sense. Things that are outside us but in which we live.

MinhHaDuong 14:53, 9 September 2008 (UTC)

Minh: This is done manually here because I plan to add comments, move things around, rearrange, rename. There is no way to do the planning with the automatic category trees, that would require editing hundreds of articles to see how things could be changed. ;-) I removed notes which are done: split skill level from Community, and split Software to main categories. Kempelen 22:24, 12 September 2008 (UTC)

### Applications

This will hold application articles directly in the category, but when there are multiple applications for a specific area, subcategories could be created, for example "Category:GPS Applications". Kempelen 22:24, 12 September 2008 (UTC)

### Guides

General documentation categorized by target audience. The Guides root should not contain articles. Kempelen 22:24, 12 September 2008 (UTC)

### Technical

Applications category contains subcategories for various application groups, like GPS, Networking... This may be a problem if e.g. GPS belongs to Applications and Hardware too (and most of these stuff will belong to both). Maybe we could simply add articles to Applications AND GPS, which won't be subcategories of each other. Kempelen 20:54, 29 August 2008 (UTC)

Basic End User and Advanced End User categories have been created instead User, which was not enough specific term. (And contained only WishList items!) Kempelen

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

### Redundant Pages

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

### Pages proposed for deletion

Look & Feel and Look & Feel/de Look & Feel is now a redirect to Artwork which is a totally different subject - therefore many links are unintentionally leading to Artwork Marko Knöbl
Neo software stack only contains of one picture without further explanation Marko Knöbl This page is not implement.coolcat
Openmoko Local User Group, Talk:Openmoko Local User Group, Template:Usergroups duplicate of Openmoko Local Groups Marko Knöbl [Openmoko Local User Group]]had removed, and replaced with [Openmoko Local User Groups]].Template:Usergroupsis a template listed every user user groups page of wiki.
SH1, SH1/es outdated, information was about Neo 1973 shipment Marko Knöbl
SIM/de no english page Marko Knöbl English version move to GSM, So I delete the SIM page. And redirect SIM/de page to GSM/de too. Hope the translater can translate it.coolcat
Wallpaper I think this is too specific for this wiki Marko Knöbl
Installation_guide, Installation guide/it Empty Kempelen

## Categories

### General issues with categories

• There are way too many categories.
• The categories index is static and therefore out of date.
• The wiki index is another static categorization. It is therefore out of date. Moreover, it seems strictly hierarchical, while actually pages should be described with multiple categories, and categories can have multiple parents.
• There should be a small number of a orthogonal category trees, each describing one consistent conceptual taxonomy.
• Ideally categories should not include language, if we don't do so the list of pages is cluttered.
• There should be only one category taxonomy for the "Neo type" with subcategories "FreeRunner", "Neo1973", "GTA03"... Otherwise, categories should not include the Neo type.
• Another big taxonomy can be based on the layers model. "Hardware", "Drivers", "Operating system", "Framework", "Applications", "Distributions". With many subcategories here.
• A taxonomy of technical level of expertise "General public", "Beginners", "Users", "Experts".
• A taxonomy by function or by subsystem: "Phone", "Wifi", "GPS/GPRS modem", "USB", "Bluetooth", "Accelerometers", "Audio", "Power", "SD card", "Serial bus", "Display", "Accessories", "Debug board"
• A taxonomy by maturity: "Wishlist", "Experimental", "Unstable", "Testing", "Stable".

MinhHaDuong 10:47, 24 August 2008 (UTC)

### Too general category names

These categories end up in mixed content. They could be removed and content migrated to more specific category names.

Category:Technical Kempelen, Marko Knöbl

Status: Openmoko Inc related info from Openmoko to a new Openmoko Inc category. Openmoko, Documentation and Information categories has been renamed and articles reassigned.

### The Category:ideas

Problem 1: Many pages have Wishlist: in the title. This syntax is potentially confusing because there is no Wishlist: namespace. I suggest a mass rename from "Wishlist:(.*)" to "Wishlist/\1" ?

Problem 2: A significant minority of pages in the "Category:ideas" are missing the prefix in the title.

Problem 3: There are two templates, { { Wishlist } } and { { Unimplemented } } . Is that unnecessary redundancy, or is there a subtle distinction . MinhHaDuong 20:23, 30 August 2008 (UTC)

### Category structure

Please see that below, because it was too long to include here.

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

(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

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:

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

## Category structure discovering and planning

This is a discovery of the current category structure and notes about how it should be changed. Please contribute, add your comments what should be changed and how. Thanks, Kempelen

• I don't understand why this is done manually, there are tags for that (see in the Discussion page).
• Technical is meaning-poor. It looks like it's about the "Phone environment" in an ecosystemic sense. Things that are outside us but in which we live.

MinhHaDuong 14:53, 9 September 2008 (UTC)

Minh: This is done manually here because I plan to add comments, move things around, rearrange, rename. There is no way to do the planning with the automatic category trees, that would require editing hundreds of articles to see how things could be changed. ;-) I removed notes which are done: split skill level from Community, and split Software to main categories. Kempelen 22:24, 12 September 2008 (UTC)

### Applications

This will hold application articles directly in the category, but when there are multiple applications for a specific area, subcategories could be created, for example "Category:GPS Applications". Kempelen 22:24, 12 September 2008 (UTC)

### Guides

General documentation categorized by target audience. The Guides root should not contain articles. Kempelen 22:24, 12 September 2008 (UTC)

### Technical

Applications category contains subcategories for various application groups, like GPS, Networking... This may be a problem if e.g. GPS belongs to Applications and Hardware too (and most of these stuff will belong to both). Maybe we could simply add articles to Applications AND GPS, which won't be subcategories of each other. Kempelen 20:54, 29 August 2008 (UTC)

Basic End User and Advanced End User categories have been created instead User, which was not enough specific term. (And contained only WishList items!) Kempelen

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