Socialwg/Addressing Issues

From W3C Wiki
Jump to: navigation, search

Addressing Issues

To progress to CR, we must formally address all issues that have been raised against a spec, and make available a list which shows their disposition [1]. We're using Github Issues [2] to track issues, and a fixed list of labels [3] to record their disposition.

Commenter Satisfied

Issues are labelled as 'commenter satisfied' if:

  • Commenter expressed they were satisfied (either with the outcome or with the WG's handling of the issue).
  • The person who opened the issue closed it.
  • An editor closed the issue saying they'd done what the commenter asked/suggested. (More recent best-practice is to ask the commenter to close the issue.)
  • Someone else picked up the commenter's discussion and eventually appeared satisfied, with no more participation from original commenter.
  • Commenter or editor opened another issue which supercedes this one.
  • Issue is about something that is no longer relevant/in scope due to significant changes to the spec.
  • If in doubt, attempted to apply common sense based on knowledge of issue, commenter, and current state of spec. If still in doubt, marked as 'waiting'.

- Amy Guy (talk) 19:19, 19 June 2016 (UTC)

Ongoing issue disposition tracking

ActivityStreams 2.0

Issue Commenter Contacted Resolved
313 @shevski 2016-06-24 timeout 2015-07-05
295 @karlitschek & @DeepDiver1975 2016-06-24 timeout 2015-07-05
293 @MerelyAPseudonym 2016-06-24 (gh) timeout 2015-07-05
292 @dmitrizagidulin & @cwebber2 2016-06-24 2014-06-24
288 @bengo 2016-04-24 pending
285 @kevinmarks & @justquick 2016-06-24 timeout 2015-07-05
284 @cathalgarvey 2016-04-24 (gh) timeout 2015-07-05
274 @sgoendoer 2016-06-24 (gh) timeout 2015-07-05
266 @rpeinl 2016-06-24 2016-06-26
242 @rpeinl 2016-06-24 2016-06-26
240 @rpeinl 2016-06-24 2016-06-26
245 @aaronpk 2016-06-24 timeout 2015-07-05
182 @aaronpk 2016-06-24 timeout 2015-07-05
235 @kleiinnn 2016-06-24 timeout 2015-07-05
233 @dissolve 2016-06-24 2016-06-25
231 @annando 2016-06-24 (gh) timeout 2015-07-05
208 @elf-pavlik 2016-06-24 timeout 2015-07-05
134 @elf-pavlik 2016-06-24 timeout 2015-07-05
132 @elf-pavlik 2016-06-24 timeout 2015-07-05
93 @elf-pavlik 2016-06-24 timeout 2015-07-05
82 @elf-pavlik 2016-06-24 timeout 2015-07-05
74 @elf-pavlik 2016-06-24 timeout 2015-07-05
65 @elf-pavlik 2016-06-24 timeout 2015-07-05
57 @elf-pavlik 2016-06-24 timeout 2015-07-05
30 @elf-pavlik 2016-06-24 timeout 2015-07-05
25 @elf-pavlik 2016-06-24 timeout 2015-07-05
24 @elf-pavlik 2016-06-24 timeout 2015-07-05
20 @elf-pavlik 2016-06-24 timeout 2015-07-05
19 @elf-pavlik 2016-06-24 timeout 2015-07-05
18 @elf-pavlik 2016-06-24 timeout 2015-07-05
14 @elf-pavlik 2016-06-24 timeout 2015-07-05
133 @abigdreamer 2016-06-24 timeout 2015-07-05
108 @oshepherd 2016-06-24 timeout 2015-07-05
86 @akuckartz 2016-06-24 timeout 2015-07-05
85 @akuckartz 2016-06-24 timeout 2015-07-05
69 @dret 2016-06-24 2016-06-28
53 @dret 2016-06-24 2015-07-05
52 @lanthaler 2016-06-24 timeout 2015-07-05