RE: Can we discuss ISSUE-137 (rationalise heartbeats) please

> I propose we remove section 6.2.7 Working Group "Heartbeat" Requirement.

DL;DR - fix it don't kill it

In my mind this is tied up with the "graveyard of /TR" issue (there's probably a politically correct name/number I forget).  The high order bit for me is to ensure that what is in /TR reflects the WG's current state of consensus about what is being worked on in editors drafts.  Publishing a shapshot of the editor's draft every n months doesn't help anyone, but motivating chairs to regularly assess stability, consensus, implementation, etc. status and ensure that reality is reflected in the /TR version of a spec should address some of the real issues that have come up in the Living Standards perma-debate.


-----Original Message-----
From: chaals@yandex-team.ru [mailto:chaals@yandex-team.ru] 
Sent: Monday, October 6, 2014 7:55 AM
To: Revising W3C Process Community Group
Subject: Can we discuss ISSUE-137 (rationalise heartbeats) please

Hi,

I think ISSUE-137 is very low hanging fruit. Can we open it and put it on the next agenda please?

TL;DR: I propose we remove section 6.2.7 Working Group "Heartbeat" Requirement.

Details:
As written it requires groups to publish *something* every 3 months. Given that most groups make editors' drafts publicly available, and work on a public mailing list, the requirement to prove they are still doing something is redundant.

In addition the mechanism is redundant, since the current process includes, in chapter 7, a requirement that groups SHOULD publish new Working Drafts when there has been a significant change - or every six months where that hasn't happened.

The most significant change in practice would be making the Process about 1.5% shorter (based on the current draft).

cheers

Chaals

--
Charles McCathie Nevile - web standards - CTO Office, Yandex chaals@yandex-team.ru - - - Find more at http://yandex.com

Received on Monday, 6 October 2014 16:36:26 UTC