CONTACTS 
0201 - SRI International                    650 326 6200
020101 - Mr. Lee Iverson
020102 - leei@ai.sri.com

SUBJECTS
ZWiki-style Collaborative Document System, 000427
Existing Capability, Start with What is Available, 000302
Pilot Test New Capabilities, 000227
Pilot Test Email for Organizing and Thought Tracking, 000428
DKR Starter Technologies, Email, Begin Using a System, 000504
ZWiki Zope Applies Wiki Technology

1608 -    ..
1609 - Summary/Objective
1610 -
161001 - Follow up ref SDS 7 3944, ref SDS 6 3944.
161002 -
161003 - Received ref DRT 1 0001 from Lee Iverson notifying the DKR seed team
161004 - for SRI that he has set up a Wiki web site, per planning on 000504.
161005 - ref SDS 4 9000
161006 -
161007 -
161008 -               http://bootstrap.org:8080/OHS
161009 -
161010 -
161011 - Lee has loaded Joe's Glossary, Eric's Requirements and Eugene's Use
161012 - Cases, and done a first pass at breaking them down into smaller
161013 - pieces. ref DRT 1 0234
161014 -
161015 - Lee advises these materials should be done further, especially the
161016 - Requirements, ref DRT 1 3034, however, he does not explain or provide
161017 - an example of what this means.
161018 -
161019 -      [On 000615 Lee discusses management ideas for Zwiki web site.
161020 -      ref SDS 13 9000
161021 - ..
161022 - Lee discloses that anybody can edit these pages, add new pages,
161023 - add comments etc.  He has started a document describing community
161024 - standards for operating within the ZWiki.  Please feel free to differ
161025 - with me or extend them. ref DRT 1 0630
161026 -
161027 -
161028 -           http://bootstrap.org:8080/OHS/GroundRules
161029 -
161030 -
161031 - Lee reminds that Zwiki is a very crude tool, but will hopefully allow
161032 - us to be a little more focused than is possible with EMail.
161033 - ref DRT 1 3375.
161034 -
161035 - This may advance Doug's request for email with addressability, cited
161036 - recently on 000601, ref SDS 9 2760, and set as a priority by Eugene at
161037 - the meeting yesterday. ref SDS 11 2760  It begins the process of pilot
161038 - testing starter technologies from work proposed by Lee at SRI on
161039 - 000504. ref SDS 4 9000
161040 -
161041 -     [On 000622 sent letter to Marcollo Hoffmann with example using
161042 -     addressability in email. ref SDS 14 6829
161043 -
161044 -
161045 -  ..
1611 -
1612 -
1613 - 2122 Experiment with Wiki
1614 -
161401 - Logged onto the Wiki web site and found Eric's specs.
161402 -
161403 -
161404 -                http://bootstrap.org:8080/OHS/Requirements
161405 -
161406 -
161407 - ...which says it is v0.8, ref DRP 1 0001, which was received on
161408 - 000605. ref SDS 10 5820
161409 - ..
161410 - Noticed that the section on Data Structures....
161411 -
161412 -
161413 -        http://bootstrap.org:8080/OHS/DataStructures
161414 -
161415 -
161416 - ...does not mention nor incorporate Eric's letter on 000605 that adds
161417 - a lot of detailed requirements, which are reviewed in the record.
161418 - ref SDS 10 6984
161419 -
161420 -
1615 -

SUBJECTS
Accountability Essential Needs Authority, Open Source, Empowerment, D
Empowerment Slippery Slope to Entropy
Entropy in Communications/Information
Accountability
Responsibility Assigned in Writing
Engineering Management Requires Accountability
ZWiki Zope Applies Wiki Technology
Original Docs Should Not Be Changed, 000609
Zwiki Permits Editing Other People's Original Work, Rod
Weblogs Like Webmail
Webmail Enhances Collaboration Enterprise Adds Value to Internet by A

3714 -
371401 -  ..
371402 - Engineering Requires Accountability, Control of Changes
371403 - Responsibility, Accountability Required for Effective Engineering
371404 -
371405 - Was able to access the environment and began to incorporate this new
371406 - material into the CDS requriements on the Wiki site, as was done for
371407 - the v0.8 on 000605. ref DRP 1 3981
371408 -
371409 - This offers a considerable increase in empowerment for team members.
371410 -
371411 - On 960510 empowerment was lauded as an important ingredient of better
371412 - management to increase earnings. ref SDS 1 0002
371413 -
371414 - Decided against making this change to the Wiki version, because the
371415 - Wiki web site is the only official version available for common
371416 - communication.  Changes must be controlled to maintain accountability
371417 - and integrity of original work, including in this case the project
371418 - specs.
371419 -
371420 - On 000601 explained scenario for commenting on original work without
371421 - making changes. ref SDS 8 4968
371422 -
371423 -      [On 000614 Eric Armstrong offers ideas on engineering management
371424 -      of Wiki web site:  requires discipline to play DKR, tricky and
371425 -      risky. ref SDS 12 0895
371426 -
371427 -      [On 000615 Lee discusses management ideas for Zwiki web site.
371428 -      ref SDS 13 9000
371429 -
371430 -      [On 000703 Morris objected to changing original work. ref SDS 16
371431 -      6030
371432 -
371433 - Changes to the official version should be submitted, reviewed, then
371434 - entered by an authorized person with a date and time of the entry,
371435 - linked to the record of review.
371436 -
371437 - In one sense, the Wiki environment provides "empowerment," but Intel's
371438 - report on 970710 shows this is a slippery slope to entropy in the
371439 - record. ref SDS 2 1431 and ref SDS 2 2009
371440 -
371441 -
371442 -  ..
3715 -
3716 -
3717 - 2201 sent letter to Lee
3718 -
371801 - Submitted ref DIT 1 0001 responding to Lee's letter, ref DRT 1 0001
371802 - and explaining effort to pilot test Wiki, per his instructions.
371803 -
371804 - Explain initial effort to incorporate the Data Structures, ref DIT 1
371805 - 1485, per above. ref SDS 0 3330
371806 -
371807 - Advise that decided to pull back per reasoning above. ref SDS 0 1008
371808 -
371809 -     [On 000614 Eric Armstrong offers ideas on engineering management
371810 -     of Wiki web site:  requires discipline to play DKR, tricky and
371811 -     risky. ref SDS 12 0895
371812 -
371813 -     [On 000615 Lee offers ideas on managing the glossary in a
371814 -     responsible manner, which provides a template for other knowledge
371815 -     resources on Wiki. ref SDS 13 6381
371816 -
371817 -     [On 000623 Jack proposes Bead Master (sounds like Com Manager),
371818 -     ref SDS 15 0784
371819 - ..
371820 - If anyone can put anything they feel might go here or there in
371821 - product specs, we would have a mess, akin to allowing anyone to modify
371822 - the design of your car or your house.  Not sure I would want to take
371823 - that car out for a spin, or trust the roof in a house constructed by
371824 - such a method.  The point I am leading toward is responsibility and
371825 - accountability. We have been discussing Eric's requirements in
371826 - meetings and correspondence, and then Eric has exercised professional
371827 - judgment in assessing the record, and deciding what to add and remove
371828 - from the requirements. ref DIT 1 2294
371829 -
371830 - Explain a better design emerges if assessments are collaborative,
371831 - analysis of pros and cons are entered in the record with attribution,
371832 - which itself is called out in the current draft, ref SDS 5 2079, yet
371833 - in fact is missing from the draft, reported on 000505, ref SDS 5 2356,
371834 - and then professional judgments are made based on the record. Since,
371835 - the DKR project has not had time to follow that procedure, Eric has
371836 - done an outstanding job in the absence of such support. ref DIT 1 2160
371837 -
371838 -
371839 -  ..
371840 - Assign Responsibility; Align for Accountability to Maintain Quality
371841 -
371842 - Recommend project team members continue to discuss requirements
371843 - through email or the pending Zope methods, and that requirements,
371844 - glossary, use cases, or whatever, be assigned to individuals and
371845 - teams, who have sole responsibility to publish project work product,
371846 - subject to review and approval of DKR management, as it eventually
371847 - develops. ref DIT 1 1394 Such assignments should be made in writing,
371848 - going back to Eugene's presentation on 000330 explaining good practice
371849 - for governance. ref SDS 3 6036
371850 -
371851 -     [On 000614 Eric Armstrong offers ideas on engineering management
371852 -     of Wiki web site:  requires discipline to play DKR, tricky and
371853 -     risky. ref SDS 12 0895
371854 -
371855 -     [On 000615 Lee offers ideas on managing the glossary in a
371856 -     responsible manner, which provides a template for other knowledge
371857 -     resources on Wiki. ref SDS 13 6381
371858 -
371859 -
371860 -
371861 -
3719 -

SUBJECTS
Engineering Management Tricky Require Discipline, Risky, 000614
Wiki Comment Procedures Require Discipline Play DKR, Tricky, Risky, 0
Risky Comment Procedures Play DKR for Wiki, Tricky, 000614
Discipline Required Play DKR for Wiki, Risky, 000614
Anchors Addressability Add to Docs, 000609
Link Addressability Anchors Original Docs
Linking Connections
Anchors Addressability for Linking Original Docs

4611 -
461101 -  ..
461102 - Alignment Builds Shared Meaning, Common Culture
461103 - Anchors in Zwiki Supports Traceability, Accountability
461104 -
461105 - A powerful use of ZWiki, or any accessible web site, is to have a
461106 - systematic way to put anchors in the record, so that requirements,
461107 - definitions, use cases, etc., can be easily cited in communications
461108 - and related work product.  This builds a common culture by allowing
461109 - everyone to work from common resources.  The more people rely on the
461110 - record, the more valuable it becomes, and this builds interest in
461111 - wanting to influence its content.  Such influence, however, needs
461112 - careful management. ref DIT 1 6794
461113 -
461114 - Doug Engelbart has a major objective of adding anchors for
461115 - addressability to his archived research documents.
461116 -
461117 -     [On 000614 Eric Armstrong offers ideas on engineering management
461118 -     of Wiki web site:  requires discipline to play DKR, tricky and
461119 -     risky. ref SDS 12 0895
461120 -
461121 -     [On 000623 Jack Park reports on 000622 team discussed adding
461122 -     anchors to original documents; Jack wants anchors added above
461123 -     documents. ref SDS 15 5475
461124 -
461125 -
461126 -
4612 -
4613 -
4614 - 2243 received letter from Lee
4615 -
461501 - Received ref DRT 1 0001 from Lee saying
461502 -
461503 -     Anchors, at least in the HTML sense, are available, and perhaps we
461504 -     can add something to the Ground Rules about making them visible
461505 -     (as with the purple numbers). ref DRT 2 5200
461506 -
461507 - This does not address the need for accountability and assignments
461508 - authorizing people to modify official project records, per above.
461509 - ref SDS 0 2880
461510 -
461511 -      [On 000615 Lee discusses management ideas for Zwiki web site.
461512 -      ref SDS 13 9000
461513 -
461514 -
461515 -
461516 -
461517 -
461518 -
461519 -
461520 -
461521 -
4616 -