ISSUE-115: Revising the Activity Statement for each Activity every 6 months

ActivityStatementRevision

Revising the Activity Statement for each Activity every 6 months

State:
CLOSED
Product:
Process Document
Raised by:
Steve Zilles
Opened on:
2014-08-26
Description:
Section 5 Activities has the following,
"The progress of each Activity is documented in an Activity Statement. At least before each Advisory Committee meeting, the Team SHOULD revise the Activity Statement for each Activity that has not been closed."

Issue: Should we put this requirement on charters?

Suggested Resolution:
No, if Activities have no formal structure in the Process, then there should be no requirement in the process to keep them up-to-date, whatever that means. When the decision to remove Activities was being discussed, it was observed that users of the W3C website found groupings of the various WGs to be useful. That however should become the domain of the Communication Team and they should be free to structure such groupings in ways that make the W3C website more effective and user friendly.
Related Actions Items:
Related emails:
  1. Summary of Resolutions re Process 2015 (from szilles@adobe.com on 2015-01-13)
  2. Re: Agenda Process Task Force Telcon on 30 September (from jeff@w3.org on 2014-09-23)
  3. RE: ISSUE-115 - group status information (from szilles@adobe.com on 2014-09-22)
  4. agenda requests... (from chaals@yandex-team.ru on 2014-09-18)
  5. Re: ISSUE-115 - group status information (from chaals@yandex-team.ru on 2014-09-16)
  6. New draft available (from chaals@yandex-team.ru on 2014-09-13)
  7. ISSUE-115 - group status information (from chaals@yandex-team.ru on 2014-09-13)
  8. Re: Agenda Process Task Force Telcon on 2 September (from chaals@yandex-team.ru on 2014-09-02)
  9. Agenda Process Task Force Telcon on 2 September (from szilles@adobe.com on 2014-09-01)
  10. w3process-ISSUE-115 (ActivityStatementRevision): Revising the Activity Statement for each Activity every 6 months (from sysbot+tracker@w3.org on 2014-08-26)

Related notes:

There was significant interest in having a requirement that Regular reports at the time of AC meetings on all WGs be made. This is already done and the requirement would be to formalize this practice. See ACTION-32

Steve Zilles, 26 Aug 2014, 14:41:03

Display change log ATOM feed


David Singer <singer@apple.com>, Chair, Dominique Hazaƫl-Massieux <dom@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $