How a TC can keep folks up to date

[Deborah Aleyne Lapeyre <dalapeyre@mulberrytech.com>]

1) Agreed: that formal minutes (as most of us know from doing them)
take almost real-time of the meeting to write.  That is a burden
most committees can't/won't handle.

2) We probably cannot legislate anything to committees about how
to go about bringing a person up to speed.  But I still feel we
should try to steer if not to legislate, maybe suggest alternatives,
provide examples, ???.

Possibilities:

a) Resolutions recorded is not good enough, as the particularly
vapid notes for this committee show.  Robert's is no help here.

b) Annotated Issues list (think how Ken needed this to join us
in San Jose)

c) From each meeting: a Decisions List
Form:

Decision:  statement of decision
optional one or two sentence justification, rationale,
or summary of the discussion or opposing view.

d)  Alternative, from each meeting: an Issues List
Form: (same as Decision List)

e) For TCs working on specs, there should be the archive of the
current draft and all previous drafts of the spec.

We are not working on a spec, but we are working on a document.
Do we have such an archive, or is it buried in, er, included
in the list archive?

What else?

--Debbie

======================================================================
Deborah Aleyne Lapeyre               mailto:dalapeyre@mulberrytech.com
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9633
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
  Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================