What is accepted
| Type | Must include | Not accepted |
|---|
| Correction | Page URL, what is wrong, and the basis (version, screenshot, command output) | 'This is wrong' alone |
| Additional measurement | The six-part template: question / control / environment / raw data / conclusion / what does not generalise | A conclusion without raw data |
| Question | Host version, OS, what you tried, the full error | A single pasted error line |
Response times
- Corrections: factual errors first; usually fixed on the page within a week.
- Additional measurements: your raw data gets checked; on acceptance it is merged with attribution.
- Questions: no guarantee of an individual reply. This is a documentation site, not a help desk — if a question deserves a section, it becomes page content; otherwise silence means it is not yet general enough.
Archiving
| State | After | Then |
|---|
| Merged into a page | Immediately | The thread stays and links to the section it became |
| Answered, not adopted | 30 days | Kept; new evidence can reopen it |
| No reply | 90 days | Archived, no longer listed; still searchable |
One hard rule: feedback without an environment is not accepted. Every conclusion here carries host version, model, and permissions; feedback carries the same three. Without them there is no way to tell your environment from a content problem — and the thread turns into persuasion instead of diagnosis.
Check every line. All of them pass or the job is not done.
Symptom, cause, what to do — written in the order it actually happens.
Verified means measured here. Compiled means every line carries a source.
