abbr-design-pattern-issues: Difference between revisions
PatrickLauke (talk | contribs) m (i can't understand why, but there's oodles of spam links appearing on the page just before the "open issue". seeing if this fixes it.) |
m (Replace <entry-title> with {{DISPLAYTITLE:}}) |
||
| (19 intermediate revisions by 8 users not shown) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:abbr design pattern issues}} | |||
These are externally raised issues about [[abbr-design-pattern]] with broadly varying degrees of merit. Thus some issues may be REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. | These are externally raised issues about [[abbr-design-pattern]] with broadly varying degrees of merit. Thus some issues may be REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. | ||
| Line 9: | Line 9: | ||
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted. | Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted. | ||
== Closed Issues == | |||
Resolved issues that have no further actions to take. | |||
* See [[abbr-design-pattern-issues-closed]]. | |||
== Resolved Issues == | |||
Resolved issues that have outstanding [[to-do]] items. | |||
* See [[abbr-design-pattern-issues-resolved]]. | |||
== Issues == | == Issues == | ||
No open issues currently. | |||
== Template == | == Template == | ||
{{issues-format}} | |||
== See Also == | == See Also == | ||
* [[abbr-design-pattern]] | * [[abbr-design-pattern]] | ||
* [[abbr-design-pattern-issues-closed]] | |||
* [[abbr-design-pattern-issues-resolved]] | |||
* [[accessibility-issues]] | * [[accessibility-issues]] | ||
* [[dfn-design-pattern]] (proposal) | |||
Latest revision as of 16:20, 18 July 2020
These are externally raised issues about abbr-design-pattern with broadly varying degrees of merit. Thus some issues may be REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — Tantek
Please add new issues to the top of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.
Closed Issues
Resolved issues that have no further actions to take.
Resolved Issues
Resolved issues that have outstanding to-do items.
Issues
No open issues currently.
Template
Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.
Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter.
<div class="hentry">
{{OpenIssue}}
<span class="entry-summary author vcard">
<span class="published">2011-MM-DD</span>
raised by <span class="fn">~~~</span>
</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2
</div>
</div>