THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net
S U M M A R Y
DIARY: April 19, 2000 07:18 PM Wednesday;
Rod Welch
Doug Engelbart plans funding with SRI support; seed team to define role.
1...Summary/Objective
2...Tool System Launch Needed to Avoid Losing Opportunity for Funding
3...OHS Editor High Immediate Utility, Unique Usage to Outside Users
....Plan for Target 1...
....Funding Targets SRI, SPC, IBM, Sun
4...Seed Team Role: Define Knowledge; Develop Open Source Applications
5...Collaboration Demonstrated by Seed Team
..............
Click here to comment!
CONTACTS
0201 - Bootstrap Institute
020101 - Mr. Douglas C. Engelbart, Ph.D.
SUBJECTS
Sponsor/Stakeholder Planning
Killer Application
Engelbart, Doug
Objective OHS Development Vector, Doug, 000405
Editor Development
Schedule for OHS Development Vector, Doug, 000405
Email Hyperdocuments Integrate
Open Source Development Freeware
Cultivate Pro-active Users for OHS Critical
OHS Vector Priority
2312 -
2312 - ..
2313 - Summary/Objective
2314 -
231401 - Follow up ref SDS 8 0000, ref SDS 7 0000.
231402 -
231403 - Doug plans actions to develop funding for project, noting urgency of
231404 - moving forward while there is interest in the effort. ref SDS 0 5778
231405 - Proposes SRI for organizational sponsor, ref SDS 0 1540, who can
231406 - provide project manaqgement. ref SDS 0 5063 Characterizes current
231407 - post-Colloquium group as "seed team," and suggests this group define a
231408 - role for itself, suggesting that it define KM. ref SDS 0 4964
231409 -
231410 -
231411 -
231412 -
231414 - ..
2315 -
2316 -
2317 - Progress
2318 -
231801 - Tool System Launch Needed to Avoid Losing Opportunity for Funding
231802 - OHS Editor High Immediate Utility, Unique Usage to Outside Users
231803 -
231804 - Follow up ref SDS 8 5778.
231805 -
231806 - Received ref DRT 1 0001 from Doug Engelbart supplementing his letter,
231807 - ref DRP 3 0001, received on 000405, ref SDS 8 5778, explaining need
231808 - for progress on DKR project in order to avoid losing current
231809 - opportunities to obtain funding. ref DRT 1 1161
231810 -
231811 - [On 000509 Paul Fernhout commented on need for progress with
231812 - coding. ref SDS 21 4980
231814 - ..
231815 - This aligns with planning on 000324 for sponsor finance to be
231816 - priority. ref SDS 5 7030 and ref SDS 5 4622
231817 - ..
231818 - On 000407 action item for finance was set. ref SDS 10 6973
231820 - ..
231821 - On 000326 Doug set goal for DKR team to create DKR tools and use
231822 - them to develop improvements. ref SDS 6 5972
231823 - ..
231824 - Doug says today that...
231825 -
231826 - Open-Source Hyperdocument System (OHS) has the most solid position
231827 - for a Tool-System "launch foundation." ref DRT 1 4810
231828 -
231829 - On 000405 Doug wanted to links in email to support project DKR,
231830 - ref SDS 8 2484, may be same thing, but not sure.
231832 - ..
231833 - [On 000601 Doug calls for addressability in email.
231834 - ref SDS 25 2760
231836 - ..
231837 - [On 000614 Bootstrap priorities include improving ability to
231838 - discuss the work. ref SDS 26 7483
231840 - ..
231841 - Cultivating pro-active users is critical to estblishing effective
231842 - co-evolution within Human, ref DRT 1 6156, and...
231843 - ..
231844 - Tool Systems
231846 - ..
231847 - Launch for strategic bootstrapping targets two issues, ref DRT 1
231848 - 3721...
231849 -
231850 - 1. Support project DKRs of software projects.
231851 -
231852 - 2. Support the "meta community's" DKR evolution.
231853 -
231855 - ..
231856 - Plan for Target 1...
231857 -
231858 - "For Discussion: Early OHS development candidate vector:",
231859 - ref DRT 1 7392
231860 -
231861 - http://www.bootstrap.org/dkr/discussion/0840.html
231863 - ..
231864 - Part 2: "Vector addition 1:"
231865 -
231866 - http://www.bootstrap.org/dkr/discussion/0787.html
231867 -
231868 -
231869 -
231870 -
2319 -
SUBJECTS
SRI Organizational Platform, Project Management
Project Manager
Management and Governance
SRI Organizational Platform, Doug, 000419
SRI Project Management, Doug, 000419
DKR Project Management
SRI Organizational Platform, Project Management, 000419
Plan Needed for Guidance
Project Management
Personnel
Funding Targets SRI, Sun, SPC, IBM
SRI Organization Platform for Project Management
3514 -
351501 - ..
351502 - Funding Targets SRI, SPC, IBM, Sun
351503 -
351504 - Doug plans to begin seeking funding and participation in the
351505 - project. He says...
351506 -
351507 - SRI is organizational platform to start planning. ref DRT 1 5800
351508 -
351509 - It has good position within business, industry, government,
351510 - universities, foundations, professional societies, etc.
351512 - ..
351513 - It has project management infrastructure, and a good, initial
351514 - set of the requisite knowledge and talent.
351516 - ..
351517 - SRI shows interest in project, including Curt Carlson, the
351518 - CEO.
351519 -
351520 - [On 000420 issue not discussed during weekly project
351521 - meeting at SRI. ref SDS 12 3055
351522 -
351523 - [On 000426 reviewed SRI support. ref SDS 15 0187
351525 - ..
351526 - [On 000504 Lee Iverson has been assigned by SRI to work on
351527 - DKR project full time. ref SDS 20 2079
351529 - ..
351530 - [On 000601 SRI providing limited support due to cash
351531 - shortage. ref SDS 25 1760
351533 - ..
351534 - [On 000601 Doug looking for organizational operational
351535 - support from Millenium Project, as an example. ref SDS 25
351536 - 1624
351538 - ..
351539 - [On 001017 report NIH agrees to fund OHS/DKR project with
351540 - SRI as organizational platform. ref SDS 27 0784
351542 - ..
351543 - [On 030527 1100 Pat advised that ultimately NIH senior
351544 - officials refused funding because Microsoft told NIH that
351545 - Sharepoint would be released that following year in 2002,
351546 - and would accomplish OHS/DKR support for collaboration at
351547 - less cost. ref SDS 28 XD90
351549 - ..
351550 - This addresses in part business issue action items cited on
351551 - 000407, ref SDS 10 6973, and possibly leadership requirment
351552 - from work on 000324. ref SDS 5 7371
351554 - ..
351555 - On 000324 SRI legal department has issues to resolve on open
351556 - source terms. ref SDS 5 3055 Doug does say in his letter
351557 - what has been decided on this matter.
351558 -
351559 - [On 000513 Paul Fernhout comments on open source
351560 - objective. ref SDS 23 0001
351562 - ..
351563 - Werner Schaer, CEO of Software Productivity Consortium (SPC),
351564 - located in the Washington D.C. area...
351565 -
351566 - http://www.software.org
351567 -
351568 - ...will meet in the morning on 000425 at SRI with Curt Carlson,
351569 - Doug Engelbart and other SRI staff who could take on support
351570 - responsibilities with associated proposals and contracts.
351571 - ref DRT 1 6386
351573 - ..
351574 - Is this the same meeting that was planned for 000410, as
351575 - reported on 000406? ref SDS 9 4877
351577 - ..
351578 - [On 000427 no report on results of meeting. ref SDS 16 4877
351580 - ..
351581 - On May 22 Doug will be in D.C. for most of the week, including
351582 - an all-day invited session at DARPA. That day could include
351583 - exploratory presentation and discussiion of this proposed
351584 - "vector." And there are a number of other long-time connections
351585 - which will be explored. ref DRT 1 1770
351586 -
351587 - [On 000420 project team set priority to develop support
351588 - information for Doug's trip. ref SDS 12 8667
351590 - ..
351591 - Doug cites possibilities of getting support from Sun, IBM and
351592 - others, for the project.
351594 - ..
351595 - In order to turn these possibilities into action, specific work
351596 - needs be accomplished....
351597 -
351598 - [On 000601 SPC and SRI cannot finance project; need
351599 - stronger sponsor outreach effort. ref SDS 25 1760
351600 -
351601 - 1. On 000324 sponsor outreach planning was proposed.
351602 - ref SDS 5 7030
351604 - ..
351605 - 2. On 000407 identified sponsor outreach as action item,
351606 - ref SDS 10 6973, and for report on results of meeting on
351607 - 000410. ref SDS 10 2975
351608 - ..
351609 - 3. Doug's letter today does not discuss planning,
351610 - proposals or strategies for pursuing these opportunities.
351612 - ..
351613 - 4. On 000407 sent letter to Adam with copy to Doug on ideas to
351614 - submit showing the ability to deliver unique KM capability
351615 - that justifies funding. ref SDS 10 0001
351616 -
351617 -
351618 -
351619 -
351620 -
3517 -
SUBJECTS
Open Source Apps, 000419
Knowledge Define, Distinguish Data, Information
Seed Team Define Knowledge, 000419
Seed Team Develop Open Source Stuff, 000419
Core Capability DKR Convert Information into Knowledge, 000227
Define Knowledge, 000307
Intelligence
Knowledge Space Paradigm Shift from Documents
Seed Team Define Role
DKR Concepts Possibilities Recommendations by Seed Team
4712 -
471301 - ..
471302 - Seed Team Role: Define Knowledge; Develop Open Source Applications
471303 - Collaboration Demonstrated by Seed Team
471304 -
471305 - Doug wants "OHS Seed Team" to develop potential role in the planning
471306 - and pursuit of launch process, ref DRT 1 5762, explained above.
471307 - ref SDS 0 5778
471308 -
471309 - Team should develop DKR about basic concepts, possibilities,
471310 - assessments, recommendations, etc. which could affect the course of
471311 - projects and planned-for application communities. A very important
471312 - need will exist for extensive and deep knowledge development about
471313 - the basics of Collective IQ, DKRs, and about knowledge and its
471314 - development. ref DRT 1 5120
471315 -
471316 - [On 000420 new team member supports Doug's request. ref SDS 12
471317 - 5555
471319 - ..
471320 - [On 000503 Eric supports call for definition of "knowledge" in
471321 - order to develop KM tools. ref SDS 18 5033
471323 - ..
471324 - [On 000504 Doug Engelbart denied NSF grant because needed
471325 - definition of knowledge. ref SDS 20 4C4F
471327 - ..
471328 - [On 000504 Eugene Kim submits working definition of information
471329 - and knowledge. ref SDS 19 5003
471331 - ..
471332 - [On 000510 Joe Williams submits definition of knowledge.
471333 - ref SDS 22 0004
471335 - ..
471336 - [On 000515 Mary Keeler scheduled to make presentation to project
471337 - team at SRI on 000516. ref SDS 24 0001
471339 - ..
471340 - [On 001017 core team will be selected from seed to work on OHS
471341 - project funded by NIH.
471343 - ..
471344 - Doug's request for project team to define knowledge aligns with
471345 - work on...
471346 -
471347 - 1. 000120 called for definition of KM. ref SDS 1 5063
471348 -
471349 - 2. 000208 Eric Armstrong asks for core of KM and OHS/DKR
471350 - system, ref SDS 2 2345, ideas were submitted. ref SDS 2
471351 - 4905
471353 - ..
471354 - 3. 000212 Eric identifies innovation. ref SDS 3 9790
471356 - ..
471357 - 4. 000307 Doug Engelbart cites work by Bellinger and asks team
471358 - to develop comparable work to define KM. ref SDS 4 4820
471360 - ..
471361 - 5. 000327 Doug cited 1972 paper explaining KM. ref SDS 7 3971
471363 - ..
471364 - 6. 000407 action item proposed to define KM. ref SDS 10 2805
471366 - ..
471367 - Another role could be to actively produce some of the open-source
471368 - innovations. Here it may need to consider how it could evolve a
471369 - "business platform" from which to handle grants, proposals,
471370 - contracts, and/or to provide technical or even operational support.
471371 - ref DRT 1 3078
471372 -
471373 - [On 000423 14 add on projects are developed for open source to
471374 - compliment SDS. ref SDS 13 8000
471376 - ..
471377 - [On 000503 proposed in letter to Jack and Eric. ref SDS 17 5152
471379 - ..
471380 - Doug further suggests the "seed team" can demonstrate value of
471381 - collaboration. ref DRT 1 6435
471382 -
471383 - This sounds like the current team might be replaced by permenant
471384 - funded staff, and Doug is suggesting that this current group
471385 - define a role for itself.
471387 - ..
471388 - [On 001017 production on OHS will be performed by CodeSourcery
471389 - and by subcontractors. ref SDS 27 9O9O
471390 -
471391 -
471392 -
471393 -
471394 -
471395 -
471396 -
471397 -
471398 -
4714 -
Distribution. . . . See "CONTACTS"