On the page
http://wiki.maemo.org/Extras-testing

What does "Try to hint the blockers first" mean?

On the page:
http://wiki.maemo.org/Extras-testing/QA_Checklist

The checkbox template for blockers entry at #6 "Optification ok" seems to have been revised from an earlier use of "Too much memory used in root partition" from the explanations later in the page.

If this is the case, the later heading of "Too much memory used in root partition" should be revised to "Optification OK" so that it the description is apparent in its relation, and the information can be used by the reader in QA..

On the page
http://wiki.maemo.org/Extras-testing/QA_Checklist

Relation of the later descriptions and checks for the earlier listed blockers is torturous to correspond with the blockers themselves.

If the blockers in the checklist are enumerated, then the later descriptions should be preceded by the same number at the beginning of a section on that particular blocker so that the reference is plain.

Example: "1." before "Lack of bug reporting database", "2." before "Licensing and legal issues", etc.

On the page
http://wiki.maemo.org/Extras-testing/QA_Checklist

Lack of clarity

remains unclear to someone coming to maemo.org as to what a "blocker" is. It sounds more like a technical component found in code, but could be community slang for anything. The explanation should specifically state what it is maemo.org slang for:

On the page
http://wiki.maemo.org/Extras-testing/QA_Checklist

Loss of utility for testing procedure

Example; "Too much memory used in root partition"
This is an instance of an instructional page becoming vague or changing its focus to design philosophy. The contents of the page should be algorithjic, not narrative. In this section, abandoning additional explanations of "why" and "how" and replacing them explicitly with testing procedure would make it useful for readers to test. There is now no information there besides mentioning dpkg as a tool for listing files - not how it is relevant, or what results should be looked for. Excursions into the links there lead only to more design philosophy, not testing procedure.

A useful entry would have an algorithmic sequence of
tool to use
how to apply it
interpretataion of result
repeat for any additional tools

This type of information would also be appropriate for other sections, such as "Power management issues" and "System performance compromised", even if the only tool is observation. The tool should be specified, the possible results specified, and the results which relate to testing pass/fail specified.

Volunteer wiki editors welcome.

I'll gladly volunteer, but like other things, I can't figure out how.

Also, others will need to address
http://talk.maemo.org/showpost.php?p=896364&postcount=5
I have not yet penetrated the swamp between here & how-to.

If I might add my own private annoyance with a website detail here:

CSS on non-IE browsers

Could someone with a notepad editor and access to the maemo server files set the max-width of the content area to something more reasonable and flexible?

I just sent a private message and the end of my lines just disappear into oblivion over to the right side of the content area. But it´s not just private messages. Other forum areas have that same problem too.

I know max-width isn´t supported by MS, but all decent browser do and for IE width should be enough as well.
Line/word wrapping might be helpfull here too...

This has been annoying me for some time now and it´s really, really easy to fix

Thank you.

* Bows. Nods head. Waves goodbye now *

I was nervous about wiki editing when I first started. But I just began googling wiki techniques and observing what others did, started off slow with minor edits and now it's no big deal.

I'm guessing, but I bet the original author meant "hit" or "find". I've set it to "find" for now.

Dave.