Wiki Issues

From Openmoko

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.

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.

Categories

General issues with categories

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.

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 may need to be created instead User, which is not enough specific term. Kempelen

In effect navigation templates create a subset of important pages presented sequentially. This corresponds more or less to a chapter in the user manual. We should not force them where they cannot create a CONSISTENT forth-and-back navigation between a GROUP OF PAGES.

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.

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)

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

Views

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.

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.

Categories

General issues with categories

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.

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 may need to be created instead User, which is not enough specific term. Kempelen

In effect navigation templates create a subset of important pages presented sequentially. This corresponds more or less to a chapter in the user manual. We should not force them where they cannot create a CONSISTENT forth-and-back navigation between a GROUP OF PAGES.

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.

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)

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