CONTACTS 
0201 - Bootstrap Institute
020101 - Mr. Douglas C. Engelbart, Ph.D.

SUBJECTS
Bootstrap, SRI, 000324
Colloquium Unfinished Revolution, 000106

0504 -
0504 -    ..
0505 - Summary/Objective
0506 -
050601 - Follow up ref SDS 39 0000, ref SDS 37 0000.
050602 -
050603 - Eugene made an excellent presentation today for a project plan,
050604 - ref SDS 0 6036, and laid out several key tasks that require first
050605 - order attention.  Next week Eric will explain progress on requirements
050606 - for the XML Editor. Doug is looking into arrangements with SRI to
050607 - facilitate sponsor support.
050608 -
050609 -    [On 000407 asked Eugene for comments on this record. ref SDS 51
050610 -    2150
050611 -
050612 -
050613 -
0507 -

SUBJECTS
Hoffman, Marcello; Lang, Ruth; Bosak, Jon

0803 -
0804 - Discussion
080501 -  ..
080502 - Introductions - Diverse Skills Focused on DKR Project
080503 -
080504 - Follow up ref SDS 39 2079.
080505 -
080506 - Marcello Hoffman
080507 -
080508 -    Has been working with Doug for many years.  He helped organize the
080509 -    Colloquium at Stanford.  Marcello is the leading thinker at SRI on
080510 -    Knowledge Management.
080511 -
080513 -  ..
080514 - Ruth Lang
080515 -
080516 -    Has been working with Doug for many years at SRI on technology
080517 -    issues for developing a DKR.
080519 -  ..
080520 - Jon Bosak
080521 -
080522 -    Contributed by speaker phone. Jon advised he cannot participate in
080523 -    each weekly meeting, but can give a presentation on XML, and
080524 -    provide other focused support.
080525 -
080526 -
080527 -
080528 -
0806 -

SUBJECTS
Sponsor/Stakeholder Planning

1003 -
100401 -  ..
100402 - Sponsors Looking for Projects in Knowledge Management Arena
100403 -
100404 - Follow up ref SDS 39 4877.
100405 -
100406 - Eugene reviewed advantages of assigning a team for sponsor outreach to
100407 - accomplish the objective Doug set last week for submitting a proposal
100408 - through SRI or in partnership with SRI, to prospective sources of
100409 - funding.
100411 -  ..
100412 - Team members can participate in formulating agreements with the
100413 - project team, SRI and sponsors to ensure the interests of all parties
100414 - are addressed.
100416 -  ..
100417 - Doug seemed to indicate he is handling this.
100419 -  ..
100420 - No assignments were made, per below. ref SDS 0 4622
100421 -
100422 -
100423 -
1005 -

SUBJECTS
Hoffman, Marcello
Dilemma Industry Doesn't Know How to Design KM
Market Conditions
Other DKR Projects Trying to Create OHS
Evaluate Market Conditions; Progress Prospects
Augment, Doug Engelbart's System at SRI Beginning in 1960s
Market Potential, Killer Application
KM Solution No One Has Done This

2410 -
241101 -  ..
241102 - Search for "Killer App" Focuses on Knowledge/Enterprise Management
241103 - Knowledge Management Difficult, Elusive; Doug's Work Sets Goals
241104 -
241105 - Follow up ref SDS 39 4877.
241106 -
241107 - Marcello Hoffman, SRI's leading KM expert, ref SDS 0 2079, was asked
241108 - about making a presentation on defining "knowledge" and "management"
241109 - in order to orient the project team toward developing Knowledge
241110 - Management capability that will offer a unique contribution in
241111 - relation to efforts by other organizations.
241113 -  ..
241114 - We hear a lot about the "knowledge management dilemma" and so it would
241115 - seem that the project might initially frame the issue to be solved,
241116 - i.e., what is the dilemma?
241117 -
241118 -     Marcello indicated that Doug's work over the past 40 years
241119 -     provides a good foundation for understanding "knowledge" and the
241120 -     special requirements for providing this valuable resource.
241122 -      ..
241123 -     On 000307 Doug asked team to develop definition of KM similar to
241124 -     Bellinger's work. ref SDS 31 4820
241126 -      ..
241127 -     On 000327 Doug submitted his 1972 paper that explains knowledge
241128 -     management in relation to handling daily working informtion from
241129 -     calls, discussion, correspondence, pending tasks, analysis,
241130 -     comments, arguments, etc. ref SDS 43 3971
241131 -
241132 -         [On 000419 Doug asked the team to define knowledge.
241133 -         ref SDS 53 4964
241135 -          ..
241136 -         [On 000420 vector set to demonstrate Augment. ref SDS 55 5922
241138 -          ..
241139 -         [On 000504 Doug advised help is needed to explain knowledge
241140 -         management. ref SDS 60 5555
241142 -          ..
241143 -         [On 000518 Doug requested glossary for project definitions;
241144 -         knowledge was defined during presentation by Professor Mary
241145 -         Keeler on the work of Charles Peirce. ref SDS 63 3286
241147 -          ..
241148 -         [On 000608 Augment demonstrated. ref SDS 65 5992
241150 -      ..
241151 -     We considered obtaining a report that explains how knowledge
241152 -     management differs from DBMS, MIS, AI, Data Mining, and other past
241153 -     efforts that have tried to use technology for management support,
241154 -     per review of IBM's Business Intelligence initiative on 980226,
241155 -     ref SDS 8 2146, cited on 000324. ref SDS 39 3422
241157 -      ..
241158 -     Marcello advised today that no one has yet developed a Knowledge
241159 -     Management solution.  There are a lot of projects working on this,
241160 -     cited by Lee Iverson at the meeting on 000324. ref SDS 39 4877
241161 -     Marcello used the phrase "bottom up" to describe progress,
241162 -     suggesting that no established theories or designs have yet been
241163 -     formulated to implement Doug's ideas on knowledge set out in his
241164 -     1972 paper reviewed on 000327. ref SDS 43 3971
241165 -
241166 -         [...below, Doug explains Augment was developed at SRI to
241167 -         support Knowledge Management. ref SDS 0 2075
241169 -          ..
241170 -         [On 000601 Marcello noted "high tech tourism" that promotes
241171 -         inflated claims to win funding is not effective. ref SDS 64
241172 -         1007
241174 -      ..
241175 -     This aligns with Jack Park's report on 000221 that creating a
241176 -     useful "ontology" for organizing information is difficult, like a
241177 -     "Pandora's Box." ref SDS 27 7455
241179 -      ..
241180 -     Previously, on 991217 at a professional conference on Knowledge
241181 -     Management no one could explain knowledge management, and everyone
241182 -     wanted a "Killer Application" program that does KM. ref SDS 16
241183 -     9030
241185 -      ..
241186 -     On 000227 report to Colloquium at Stanford that SDS is best DKR.
241187 -     ref SDS 29 0897
241188 -
241189 -       [On 000405 Jack Park asked about the role of "opinion" and a
241190 -       personal journal in managing "knowledge" using a dynamic
241191 -       knowledge repository, ref SDS 49 2928
241193 -        ..
241194 -       [On 000405 Paul Fernhout explained knowledge representation is
241195 -       difficult, no one has done it. ref SDS 49 5977 and ref SDS 49
241196 -       4611
241198 -        ..
241199 -       [On 000414 Eric Armstrong cites Traction as good DKR program.
241200 -       ref SDS 52 3450
241202 -        ..
241203 -       [On 000420 Eric Armstrong submits list of similar projects.
241204 -       ref SDS 54 4877
241206 -        ..
241207 -       [On 000422 Joe Williams submits DKR design based on use case
241208 -       analysis. ref SDS 56 4933
241210 -        ..
241211 -       [On 000426 Jack Park cites SDS as proof of concept for aspects
241212 -       of DKR. ref SDS 57 3315
241214 -        ..
241215 -       [On 000504 Jack and Eugene Kim cite SDS again. ref SDS 59 0784
241217 -        ..
241218 -       [On 000601 at project meeting Marcello suggested ways to target
241219 -       funding initiatives to individuals. ref SDS 64 4080
241221 -        ..
241222 -       [...Marcello explained need to demonstrate that knowledge
241223 -       management project is more than high tech tourism. ref SDS 64
241224 -       1007
241225 -
241226 -
241227 -
241228 -
241229 -
241230 -
2413 -

SUBJECTS
Property Rights in Knowledge Organization
Commercial Viability
Ownership Investment Risk
Development Investment Risk

2906 -
290701 -  ..
290702 - Legal Issues Arising from Open Source and Sponsor Support
290703 -
290704 - Follow up ref SDS 39 3055.
290705 -
290706 - Eugene reviewed the need to sort out legal issues on open source.
290707 -
290708 - There was consideration for assigning a team to investigate this and
290709 - develop options, and that it needs to be settled in order for
290710 - participants to be comfortable investing a lot of effort in the
290711 - project.
290713 -  ..
290714 - Doug seemed to indicate he is working with SRI on this.
290716 -  ..
290717 - There was no discussion today of prior work on 000203 presented by
290718 - Paul Fernhout for the Colloquium on legal complexities of Open Source
290719 - projects, ref SDS 24 0001, cited in the record of the meeting last
290720 - week. ref SDS 39 3055
290722 -  ..
290723 - There was discussion that BI needs a particular license or tax status
290724 - to operate a project using contributed funds along the lines being
290725 - contemplated.
290727 -  ..
290728 - Doug indicated some BI entity has qualified for this status, but there
290729 - is a snag of some sort that renders it inaposite for use on the DKR
290730 - project.
290732 -  ..
290733 - Doug indicated work is underway with SRI to provide this standing for
290734 - the project.
290736 -  ..
290737 - It appears to be a threshold requirement for the project to develop
290738 - funding to operate.
290739 -
290740 -     [On 000419 Doug reported plans to proceed with SRI for
290741 -     organization support. ref SDS 53 1540
290742 -
290743 -
290744 -
290745 -
290746 -
2908 -

SUBJECTS
Editor XML Linking Support Knowledge Management Initial Project Deli

3903 -
390401 -  ..
390402 - Doug Sets Project Objective to Produce DKR Capability
390403 -
390404 - Follow up ref SDS 39 2808, ref SDS 38 0400.
390405 -
390406 - Joe initially reviewed technology development ideas for implementing
390407 - OHS and DKR per his letter on 000307. ref SDS 31 5837  He used the
390408 - marking board to illustrate process flows that need consideration in
390409 - designing DKR technology, expanding upon suggestions at the meeting on
390410 - 000324. ref SDS 39 4140
390411 -
390412 -        [On 000406 Joe mapped out his ideas again; consideration was
390413 -        made for Joe to formally present this approach. ref SDS 50 7200
390415 -         ..
390416 -        [On 000420 Joe gave formal presentation. ref SDS 55 5880
390418 -      ..
390419 -     No assignment was made to develop the "ontology" requirement, nor
390420 -     to formally present Bellinger's work, cited by Joe at the meeting
390421 -     on 000324, and noted previously by Jack Park and Eric Armstrong
390422 -     beginning on 000221. ref SDS 27 8044
390423 -
390425 -      ..
390426 -     Editor Based on XML Initial Project Deliverable
390427 -     Collaborative Document System and OHS Supported by Editor
390428 -
390429 -     Follow up ref SDS 39 5880.
390430 -
390431 -     Eugene asked Eric to explain at the meeting next week progress on
390432 -     developing requirements for the XML editor to implement Doug's
390433 -     requirements for linking in the OHS/DKR software program.
390434 -     Research on 000125 indicates XML was developing support for
390435 -     linking in 1999, and so this may now be available. ref SDS 20 URWP
390436 -
390437 -         [On 000331 Jack Park asks how SDS records create so many links
390438 -         without using XML? ref SDS 46 TQ52
390440 -      ..
390441 -     Background shows concensus on the team that XML editor can
390442 -     accomplish requirements for Knowledge Management...
390443 -
390444 -     1.  XML method for structuring data in a file from different
390445 -         program formats, e.g., spreadsheets, wordprocessing,
390446 -         pictures, etc., that provides a common viewing environment
390447 -         where comments can be entered to explain what is displayed
390448 -         from other programs, reviewed 000125. ref SDS 20 7568
390450 -          ..
390451 -     2.  Java data objects may be related to XML and structured data,
390452 -         also explained on 000125. ref SDS 20 7568
390454 -          ..
390455 -         Linking support is under development. ref SDS 20 URWP
390457 -          ..
390458 -     3.  XML supports collapsable hierarchy to control visible
390459 -         presentation that helps grasp structure without detail, and
390460 -         obtain detail with clicking a node, reviewed 000129.
390461 -         ref SDS 21 PTVQ
390463 -          ..
390464 -     4.  Java data objects (JDO) research seems to correlate with
390465 -         objectives for XML applcation to Knowledge Management, shown
390466 -         on 000129. ref SDS 21 GD6J
390468 -          ..
390469 -     5.  XML editor development using Java explained in connection with
390470 -         masters thesis cited by Jack Park on 000131. ref SDS 22 R264
390472 -          ..
390473 -     6.  Xeena IBM editor XML was propopsed for the OHS/DKR project at
390474 -         SRI on 000223 by Eric Armstrong. ref SDS 28 QQ96
390475 -
390476 -
390477 -
3905 -

SUBJECTS
Augment, Doug Engelbart's System at SRI Beginning in 1960s
Augment Human Capabilities

4204 -
420501 -      ..
420502 -     Augment Project at SRI in 1960s Sets Design Objectives
420503 -
420504 -     Doug explained innovations he and his team at SRI developed in the
420505 -     1960s for a system of Augment, described in some degree by Doug's
420506 -     paper in 1972, tendered to the current team on 000327 identifying
420507 -     goal to improve handling of daily working information. ref SDS 43
420508 -     3971  Doug indicated today that Augment provides strong rationale
420509 -     and foundation for the DKR project.
420511 -      ..
420512 -     There was discussion about demonstrating that system and reviewing
420513 -     the design materials, e.g., specification, flow diagrams,
420514 -     descriptions, etc., as guidance for the DKR project.
420516 -      ..
420517 -     Doug indicated the system does not run on current systems.  Some
420518 -     design materials may be available.  Doug will investigate how
420519 -     this early work might be presented at a team meeting.
420520 -
420521 -        [On 000420 Doug and Lee Iverson will try to assemble a system
420522 -        to run Augment for demonstrating capability. ref SDS 55 5922
420524 -         ..
420525 -        [On 000608 Doug demonstrated Augment; team favorably impressed.
420526 -        ref SDS 65 5992
420527 -
420528 -
420529 -
420530 -
420531 -
420532 -
420533 -
420534 -
4206 -

SUBJECTS
Project Planning, Objectives
Plan Needed for Guidance
Management and Governance
Accountability Essential Needs Authority, Open Source, Empowerment, D
Open Source Development Freeware
Open Source Lacks Management Accountability
Disputes Resolved by Leadership
Accountability
Detailed Written Record of Meetings Unnecessary, 000330
Assignments Require Authority, Made in Writing
Legislative, Executive, Judicial, 00030
Open Source Similar Empowerment, No Authority, No Responsibility
Open Source Assignments Require Authority

6015 -
601601 -  ..
601602 - "Plan" to Attract Sponsors Requires Good Management, Accountability
601603 - -------------------------------------
601604 - Follow up ref SDS 39 6036, ref SDS 20 2397.
601605 -
601606 - Eugene gave an excellent presentation for the project plan.
601607 -
601608 - He proposed a system of management based on a...
601609 -
601610 -
601612 -              ..
601613 -             Legislative     Executive       Judicial
601614 -
601615 -
601616 -
601617 - ...where Doug provides "judicial" oversight to resolve major issues.
601618 -
601620 -  ..
601621 - Eugene seemed to describe the members of the post-Colloquium SRI
601622 - meetings are the "legislature" responsible for getting things done.
601624 -  ..
601625 - Executive role was unclear.
601627 -  ..
601628 - Doug noted that SRI has a lot of manuals on managing projects that can
601629 - be adapted to demonstrate due diligence on managing the project.
601631 -  ..
601632 - Adam Cheyer's idea to develop email enhancements using XML was
601633 - presented in summary form by Eugene, which seemed to reflect Eric
601634 - Armstrong's idea on 000120. ref SDS 18 3871
601635 - ..
601636 - Eugene proposed the first order of business is to make
601637 - assignments for getting things done.
601639 -  ..
601640 - He stressed the importance of accountability to maintain progress of
601641 - the work, which is a major aspect of responsibility that requires
601642 - authority to use resources for performing the work.  Accountability is
601643 - aided by traceability to original sources, which requires capturing an
601644 - effective record so there is an original source that can be aligned,
601645 - called by ISO criteria reviewed on 950721. ref SDS 5 1740
601646 -
601647 -     [On 000609 Wiki empowers team members with enhanced email to
601648 -     change project specs; impacts accountability. ref SDS 66 3330
601650 -  ..
601651 - At the meeting on 000324 the team elected to manage the project using
601652 - Open Source methods where work is accomplished by volunteers, rather
601653 - than assignments, since there is no authority. ref SDS 39 4729
601655 -  ..
601656 - On 000326 Doug Engelbart provided guidance on need to develop an
601657 - effective project record to provide the "intelligence" for managing
601658 - the project. ref SDS 41 5972
601660 -  ..
601661 - Eugene asked Rod Welch to help make assignments today.
601662 - ..
601663 - Rod suggested that Eugene write up a draft of the record for the
601664 - meeting today, since he was the lead speaker, as a predicate for
601665 - guiding the work.  Assignments flow from understanding the record in
601666 - order to create knowledge from information at the meeting today that
601667 - identifies action items, within the meaning of Communication Metrics.
601669 -  ..
601670 - There was considerable discussion that a detailed record of the
601671 - meeting is not needed.  Concensus formed not to prepare formal meeting
601672 - notes.  Attendees generally feel that everyone is in agreement on what
601673 - happened at the meeting today, so a record would be extra work that
601674 - is not needed.
601676 -  ..
601677 - Someone proposed that a few action items might be identified.
601679 -  ..
601680 - Rod explained that action items come from the record.
601682 -  ..
601683 - No one was assigned to identify action items.
601685 -  ..
601686 - Su-Ling seemed to have tape recorded the meeting, so possibly this was
601687 - thought to be adequate for managing the project.
601688 -
601689 -     [On 000427 Doug plans for Sue Ling to provide Com Manager
601690 -     function. ref SDS 58 2867
601691 -
601692 -     [On 000504 Eugene explains his practice to take lots of notes and
601693 -     provide structure that aids understanding and follow up.
601694 -     ref SDS 59 6205
601696 -      ..
601697 -     [On 000511 Eugene assigned to lead team meetings. ref SDS 61 0784
601699 -      ..
601700 -     [On 000516 Eugene directs preparation of formal record for project
601701 -     meetings. ref SDS 62 3740
601703 -      ..
601704 -     [On 000518 Howard Liu took notes. ref SDS 63 8160
601706 -      ..
601707 -     [On 000613 received excellent notes edited by Eugene for the
601708 -     meeting on 000601, showing that Eugne's plan today for sound
601709 -     management practice can be accomplished. ref SDS 67 0001
601711 -  ..
601712 - Eugene asked Eric to explain next week progress on requirements for
601713 - the XML Editor.
601715 -  ..
601716 - Doug was asked if he wanted to schedule Twisted Systems to explain
601717 - Traction, their journaling system at the meeting on 000413?
601719 -  ..
601720 - Doug seemed to indicate this is not a priority at this time.
601721 -
601722 -
601723 -
601724 -
601725 -
601726 -
601727 -
6018 -

SUBJECTS
Preliminary Project Plan

6103 -
6104 -   ..
610401 - Follow up ref SDS 39 9776.
610402 -
610403 - Possible Issues for Eugene, Jack, Eric, Joe to Consider
610404 -
610405 -   1.  Mission of the project?
610406 -
610407 -       a.  Augment human capabilities, ref SDS 17 3011, using ABC
610408 -           process, per record on 991222? ref SDS 17 1550
610409 -
610410 -           What capabilities will be augmented?
610412 -            ..
610413 -           It was not clear that Eugene covered this as developed on
610414 -           000324. ref SDS 39 0638
610415 -
610416 -             [On 000404 Eric Armstrong submitted a letter proposing
610417 -             that human reasoning be augmented. ref SDS 48 7844
610419 -            ..
610420 -       b.  Solve world problems and enterprise problems
610421 -
610422 -           Will capability directly solve problems, i.e., provide a
610423 -           service to implement DKR that solves problems; or,
610424 -
610425 -             This was not discussed today.
610427 -            ..
610428 -           Provide capability deployed by people working on world
610429 -           problems to enhance their ability to collaborate, develop
610430 -           and implement solutions, similar to the way alphabet
610431 -           technology is used to "lift all boats" to a higher cognitive
610432 -           plane, per review on 991108? ref SDS 14 5628
610433 -
610434 -             This was not discussed today.
610436 -            ..
610437 -           Will same capability solve Enterprise Management problems
610438 -           cited by Chemical Bank presentation at Colloquium?
610439 -           ref SDS 39 5092
610440 -
610441 -             This was not discussed today.
610442 -           ..
610443 -       c.  Attract sponsor support
610444 -
610445 -           Define project deliverable for review with participating
610446 -           organizations/sponsors, per Doug. ref SDS 39 7030
610447 -
610448 -             Eugene proposed assignments be made on this,
610449 -             per above. ref SDS 0 4877
610451 -            ..
610452 -           Sponsors need something that earns a reward.
610454 -            ..
610455 -           Commercial success - can something that solves world
610456 -           problems be commercially successful?
610457 -
610458 -             [On 000403 Eric Armstrong submitted compelling analysis on
610459 -             business models, ref SDS 47 0004, and explained challenges
610460 -             of open source efforts. ref SDS 47 5956
610461 -
610462 -       ..
610463 -   2.  What will be produced?
610464 -   
610465 -       Project plan on OHS/DKR to attract sponsors.
610466 -
610467 -       a.  OHS XML (WBI) Editor with lots of features? per Doug.
610468 -           ref SDS 39 5880
610469 -
610470 -           Engineering Management first kind of work to augment, per
610471 -           meeting on 000324. ref SDS 39 5964
610472 -
610473 -           •  Does it replace wordprocessing?
610474 -
610475 -              This was not addressed today.
610476 -
610477 -           •  How will it support ABC augment, per Joe? ref SDS 39
610478 -              4140
610480 -               ..
610481 -              This was not addressed today.
610482 -
610483 -           •  What will it do that is very useful that nobody else has
610484 -              thought of doing or knows how to do, per Warren's
610485 -              suggestion? ref SDS 39 2387
610487 -               ..
610488 -              This was not addressed today.
610489 -
610490 -           •  How will it achieve commercial success?
610491 -
610492 -              This was not addressed today to supplement ideas on
610493 -              000324. ref SDS 39 6224
610494 -
610495 -                 [On 000403 Eric Armstrong submitted compelling
610496 -                 analysis on business models, ref SDS 47 0004, and
610497 -                 explained challenges of open source efforts.
610498 -                 ref SDS 47 5956
610499 -
610501 -            ..
610502 -       b.  Other Applications??
610503 -
610504 -              This was not addressed today.
610506 -            ..
610507 -       c.  DKR to support ABC Augment
610508 -
610509 -              This was not addressed today to supplement ideas on
610510 -              000324, ref SDS 39 3611, and Doug's 1972 paper reviewed
610511 -              on 000327. ref SDS 43 3971
610512 -
610513 -              [On 000331 reviewed issue. ref SDS 46 5973
610515 -               ..
610516 -              [On 000405 Jack Park requests comment on whether DKR
610517 -              should include opinion, how it should be represented, and
610518 -              whether a personal journal should be in the DKR?
610519 -              ref SDS 49 2928
610520 -        ..
610521 -   3.  Staff and skills available to produce DKR.
610522 -
610523 -              This was not addressed today to supplement ideas on
610524 -              000324. ref SDS 39 7074
610525 -
610526 -              [On 000403 Eric Armstrong submitted analysis setting out
610527 -              challenges of open source efforts. ref SDS 47 5956
610529 -        ..
610530 -   4.  Budget for resources needed to get what we need?
610531 -
610532 -             This was not addressed today to supplement ideas on
610533 -             000324. ref SDS 39 5482
610534 -
610535 -       ..
610536 -   5.  Participation and Reward
610537 -   
610538 -             This was not addressed extensively today to supplement
610539 -             ideas on 000324. ref SDS 39 1450
610540 -
610541 -             Eugene proposed assignments be made on this,
610542 -             per above. ref SDS 0 4877
610544 -               ..
610545 -              [On 000403 Eric Armstrong submitted analysis setting out
610546 -              challenges of open source efforts. ref SDS 47 5956
610547 -
610548 -       ..
610549 -   6.  Open Source
610550 -   
610551 -             This was not addressed extensively today to supplement
610552 -             ideas on 000324. ref SDS 39 7371
610553 -
610554 -             Eugene proposed assignments be made on this,
610555 -             per above. ref SDS 0 4877
610557 -               ..
610558 -              [On 000403 Eric Armstrong submitted analysis setting out
610559 -              challenges of open source efforts. ref SDS 47 5956
610560 -
610561 -       ..
610562 -   7.  Schedule - Define Practical Scale of Tasks
610563 -   
610564 -             This was not addressed today to supplement ideas on
610565 -             000324. ref SDS 39 2640
610566 -
610567 -             [On 000405 Doug Engelbart submitted outline of tasks for
610568 -             discussion at meeting on 000406.
610569 -
610570 -
610571 -
610572 -
610573 -
610574 -
610575 -
610576 -
6106 -
6107 -