ISSUE-141: Improve Errata management in W3C

Errata

Improve Errata management in W3C

State:
OPEN
Product:
Process Document
Raised by:
Jeff Jaffe
Opened on:
2014-09-18
Description:
How to motivate the W3C Community and WGs to expeditiously and consistently issue errata? In the modern specification development world, agile development methodologies ensure that most "standards" continue to evolve. Also, with a larger number of distinct products implementing W3C standards, we are more likely to find bugs and errata.

For reasons of process and practice, W3C working groups do not necessarily issue errata in an expeditious fashion. We should fix the W3C Process so that it encourages groups to consistently issue errata. We should also explore Best Practices that groups could adopt to improve their handling of this issue.
Related Actions Items:
Related emails:
  1. Re: Call for Review, W3C Process2015 (from [email protected] on 2015-03-20)
  2. Re: New Process Draft... - diff without must, should ... (from [email protected] on 2015-03-06)
  3. Re: New Process Draft... (from [email protected] on 2015-03-06)
  4. Call for Review, W3C Process2015 (from [email protected] on 2015-03-06)
  5. 2nd Draft Announcement of Process2015 Wide Review (from [email protected] on 2015-03-03)
  6. Draft Announcement of Process2015 Wide Review (from [email protected] on 2015-03-02)
  7. RE: w3process-ISSUE-155 (Errata Access in RECs): Errata access from TR page [Process Document] (from [email protected] on 2015-02-09)
  8. Re: w3process-ISSUE-155 (Errata Access in RECs): Errata access from TR page [Process Document] (from [email protected] on 2015-02-09)
  9. Re: w3process-ISSUE-155 (Errata Access in RECs): Errata access from TR page [Process Document] (from [email protected] on 2015-02-09)
  10. Issue timing Re: w3process-ISSUE-155 (Errata Access in RECs): Errata access from TR page [Process Document] (from [email protected] on 2015-02-08)
  11. w3process-ISSUE-156 (Errata vs REC track process): Do we need separate Errata and REC Track Processes? [Process Document] (from [email protected] on 2015-02-08)
  12. RE: w3process-ISSUE-155 (Errata Access in RECs): Errata access from TR page [Process Document] (from [email protected] on 2015-02-07)
  13. Re: w3process-ISSUE-155 (Errata Access in RECs): Errata access from TR page [Process Document] (from [email protected] on 2015-02-07)
  14. w3process-ISSUE-155 (Errata Access in RECs): Errata access from TR page [Process Document] (from [email protected] on 2015-02-07)
  15. Re: errata again, responding to the november proposal (from [email protected] on 2015-01-20)
  16. RE: errata again, responding to the november proposal (from [email protected] on 2015-01-19)
  17. Re: errata again, responding to the november proposal (from [email protected] on 2015-01-19)
  18. Re: Agenda Process Document Task Force 20 January 2015a (from [email protected] on 2015-01-19)
  19. Agenda Process Document Task Force 20 January 2015a (from [email protected] on 2015-01-19)
  20. RE: errata again, responding to the november proposal (from [email protected] on 2015-01-19)
  21. call is at 1500Z (not 1400) EoM Re: Agenda Process Document Task Force 13 January 2015a (from [email protected] on 2015-01-13)
  22. Re: Errata - a proposal (from [email protected] on 2015-01-13)
  23. Re: Errata - a proposal (from [email protected] on 2015-01-12)
  24. Agenda Process Document Task Force 13 January 2015a (from [email protected] on 2015-01-12)
  25. Re: Errata - a proposal (from [email protected] on 2015-01-12)
  26. Re: Errata - a proposal (from [email protected] on 2015-01-11)
  27. RE: Errata - a proposal (from [email protected] on 2015-01-11)
  28. Errata - a proposal (from [email protected] on 2015-01-10)
  29. Agenda Process Document Task Force 16 December 2014; Last Telcon of 2014; correcting the date (from [email protected] on 2014-12-16)
  30. Agenda Process Document Task Force 17 December 2014; Last Telcon of 2014 (from [email protected] on 2014-12-15)
  31. Agenda Process Document Task Force 10 December 2014 (from [email protected] on 2014-12-08)
  32. RE: WHATWG/W3C collaboration proposal and the discussion of Issue-141 (from [email protected] on 2014-11-25)
  33. Re: Agenda Process Task Force Telcon on 11 November, 2014 (from [email protected] on 2014-11-11)
  34. Re: Agenda Process Task Force Telcon on 21 October (from [email protected] on 2014-10-22)
  35. Re: Agenda Process Task Force Telcon on 21 October (from [email protected] on 2014-10-21)
  36. Re: Agenda Process Task Force Telcon on 21 October (from [email protected] on 2014-10-20)
  37. Re: Proposal for Publishing REC Errata (from [email protected] on 2014-10-17)
  38. Re: Proposal for Publishing REC Errata (from [email protected] on 2014-10-17)
  39. Re: Proposal for Publishing REC Errata (from [email protected] on 2014-10-15)
  40. Re: Proposal for Publishing REC Errata (from [email protected] on 2014-10-15)
  41. RE: Proposal for Publishing REC Errata (from [email protected] on 2014-10-15)
  42. Re: Proposal for Publishing REC Errata (from [email protected] on 2014-10-15)
  43. Draft Minutes of 14 Octobe Process TF Telcon (from [email protected] on 2014-10-14)
  44. Re: Agenda Process Task Force Telcon on 14 October (from [email protected] on 2014-10-14)
  45. Re: Agenda Process Task Force Telcon on 14 October (from [email protected] on 2014-10-14)
  46. Improving our processes Re: Normative references and stable documents (from [email protected] on 2014-10-13)
  47. Re: Normative references and stable documents (from [email protected] on 2014-10-12)
  48. w3process-ISSUE-141 (Errata): Improve Errata management in W3C [Process Document] (from [email protected] on 2014-09-18)

Related notes:

See also ISSUE-96

Charles 'chaals' (McCathie) Nevile, 14 Oct 2014, 09:26:00

ISSUE-96 is also relevant, was one of the 2014 AC review issues we agreed to address, and has links that are not otherwise tracked here, but was closed since it is basically subsumed by this one.

Charles 'chaals' (McCathie) Nevile, 11 Jan 2015, 15:48:41

In the 1/20/2015 Process Document TF Telcon
http://www.w3.org/2015/01/20-w3process-minutes.html#item02
Issue-141 was resolved with David Singer's proposed text together with the modification he proposed during the Telcon.
David distributed the revised text, incorporating the modification, in
20 Jan 2015, 19:16:59

Transferred to https://github.com/w3c/w3process/issues/5

David Singer, 21 Apr 2017, 18:27:07

Display change log ATOM feed


David Singer <[email protected]>, Chair, Dominique HazaĆ«l-Massieux <[email protected]>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <[email protected]>.
$Id: 141.html,v 1.1 2020/03/09 13:49:28 carcone Exp $

Follow Lee on X/Twitter - Father, Husband, Serial builder creating AI, crypto, games & web tools. We are friends :) AI Will Come To Life!

Check out: eBank.nz (Art Generator) | Netwrck.com (AI Tools) | Text-Generator.io (AI API) | BitBank.nz (Crypto AI) | ReadingTime (Kids Reading) | RewordGame | BigMultiplayerChess | WebFiddle | How.nz | Helix AI Assistant