Click here to comment!
1...Why isn't Eric using Traction? Is cost an issue? How much
2...Open source issue needs review vis a vis Twisted System's
3...Question mark on the picture of Pat Lincoln, shows action item
4...There is no record of research Twisted Systems may have done
5...Chris' report does not relate what was presented on this
CONTACTS
0201 - Twisted Systems, Inc.
020101 - Mr. Chris Nuzum; 401 268 9099
SUBJECTS
Traction, Journaling, by Twisted Systems, 000326
Telecon Proposed on Traction by Chris Nuzum
Web Journal Email Organizing System Solves Information Overload Solve
New Way Working Team Communication Email Organizing System Solves Inf
Pictures, Visualization Executive Work Practices
1907 -
1907 - ..
1908 - Summary/Objective
1909 -
190901 - Follow up ref SDS 38 0000, ref SDS 34 0000.
190902 -
190903 - Received examples of work product for Traction that shows powerful
190904 - capability for linking and assembling the record to support analysis.
190905 - However, there is essentially no analysis in Traction work product and
190906 - no traceability to original sources that provide knowledge of
190907 - causation. ref SDS 0 RL8G Perhaps Twisted Systems can reconcile this
190908 - disparity, and/or it offers an opportunity for synergy in marketing
190909 - complementary capabilities in Traction and SDS. ref SDS 0 FV6L Chris
190910 - asks for a date next week to have a telephone call to follow up.
190911 -
190912 - [On 011104 submitted letter to Chris on following up. ref SDS 39
190913 - 0001
190915 - ..
190916 - [On 020619 Traction being tried by CIA under contract with
190917 - In-Q-Tel. ref SDS 41 0001
190918 -
190919 -
190921 - ..
1910 -
1911 -
1912 - Progress
1913 -
191301 - Daily Working Information Incorporated into Traction Environment
191302 - Traction Work Product Improves Email, Strong Support for Pictures
191303 - Pictures Integrated into Traction Work Product
191304 -
191305 - Received ref DRT 1 0001 from Chris Nuzum responding to the call a few
191306 - days ago asking about work product from the meeting at SRI on 000413.
191307 - ref SDS 10 4209 Chris suggests a teleconference next week.
191308 -
191309 - Chris submits a lot of work product he and others have created using
191310 - Traction. This answers questions in letters, ref DIP 4 0001, to Eric
191311 - Armstrong and the OHS/DKR team on 011031 asking for Traction work
191312 - product.
191314 - ..
191315 - Chris' letter supports Eric's report on 011031 of having seen work
191316 - product and links that show Traction revolutionizes email, ref SDS 38
191317 - OE9G, to strengthen team communication using a web journal cited in
191318 - the record on 000326. ref SDS 7 5877
191320 - ..
191321 - Chris provides in a post script the following examples of Traction
191322 - work product over the past several years.....
191323 -
191324 - 1. Traction Memo on 011101 noting receipt of call from Rod and
191325 - proposing action item to discuss via telecon with Chris, Greg
191326 - and Rod. ref DRT 1 J18M
191328 - ..
191329 - A group picture from meeting at SRI on 000413, ref SDS 10 0001,
191330 - shows Rod looking away, which may be intended for orientation
191331 - to get Chris into the subject. ref DRT 1 GH9L The picture
191332 - seems to have been drawn from the record of the meeting at SRI
191333 - on 000413, which Chris submits separately below. ref SDS 0 R66J
191335 - ..
191336 - John Deneen reported recently on value of a picture worth a
191337 - thousand words. ref SDS 31 2X8K Previously advantages of
191338 - pictures were reviewed on 940609. ref SDS 2 4933
191340 - ..
191341 - Chris' memo illustrates ability to use Traction for analysis
191342 - and planning daily work called out by Doug Engelbart in his
191343 - 1972 paper, reviewed on 000327, ref SDS 8 3971, which
191344 - strengthens team communication and coordination cited in the
191345 - Traction overview reported on 000326. ref SDS 7 5877
191347 - ..
191348 - There is no link to Welch work product for the meeting on 000413
191349 - nor to POIMS, ref OF 1 0001, the NWO, ref OF 3 0001, nor to
191350 - other resources at....
191351 -
191352 - http://www.welchco.com
191354 - ..
191355 - Traction seems to be aware of Welch cited in the record....
191356 -
191357 - Commenting on Eric's analysis...... 000824, ref DRT 1 00G5
191358 - Traction planning.................. 000412, ref DRT 1 PY3N
191360 - ..
191361 - There is no analysis nor alignment with Welch work, as was done
191362 - for example on 000326 for Traction, ref SDS 7 0001, later for
191363 - Eric's CDS specs on 000505, ref SDS 15 0001, and more recently
191364 - Lee Iverson's NODAL ideas on 010620. ref SDS 25 0001 Is this a
191365 - good use of Traction, or is it designed to do other things?
191367 - ..
191368 - 2. Letter from Eric Armstrong on 011031 reporting no availability
191369 - of Traction work product. ref DRT 1 0002
191371 - ..
191372 - This letter, ref DRP 7 0001, was reviewed 011031. ref SDS 38
191373 - OE9G It appears that people at Twisted Systems are monitoring
191374 - progress on OHS/DKR email traffic.
191375 - ..
191376 - 3. Traction work product evidently prepared on 011101 by Tim
191377 - noting Eric's letter is interesting and seems new. ref DRT 1
191378 - OP5F
191380 - ..
191381 - Where are connections providing context that explain why Eric's
191382 - letter is "interesting" -- see analysis below. ref SDS 0 RL8G
191383 - ..
191384 - 4. Letter from Eric Armstrong earlier on 011031 reporting
191385 - Traction is effective technology, but is not open source.
191386 - ref DRT 1 FF7N
191388 - ..
191389 - This letter, ref DRP 6 XW6I, was reviewed 011031. ref SDS 38
191390 - U77O
191392 - ..
191393 - Traction work product prepared on 011101 by Chris indicates
191394 - Eric's expression is overstated, but apt. ref DRT 1 0277 Does
191395 - not cite Chris' report on the meeting at SRI on 000413, nor
191396 - provide a link to Traction's record showing what Chris
191397 - presented. ref SDS 0 R66J
191398 - ..
191399 - 5. Letter from Welch dated 011031 asking about Traction work
191400 - product, ref DRT 1 YA7F, and if Traction has been pilot tested.
191401 - ref DRT 1 II9I
191403 - ..
191404 - This letter, ref DIP 4 0001, was prepared in the record on
191405 - 011031. ref SDS 38 0001
191406 - ..
191407 - 6. Traction work product evidently prepared on 011101 by
191408 - Chris about talking to Rod and demonstrating Traction.
191409 - ref DRT 1 0387
191411 - ..
191412 - There is no plan for sending examples of work product, as was
191413 - actually done. Nothing to indicate who is responsible and when
191414 - the work should be performed, what to include. Not clear how
191415 - this supports goal of supporting accountability reported on
191416 - 000326. ref SDS 7 PF6O
191417 -
191418 -
191419 -
191420 -
1915 -
SUBJECTS
Confidentiality Links Cannot be Accessed Protected by Password
Confidentiality Traction Aligns with OHS/DKR Objectives
Security Privacy Balance Intelligence for Collaboration
2305 -
230601 - ..
230602 - Confidentiality Supported by Traction Password System
230603 - Password Control's Access to Maintain Confidentiality
230604 - Intelligence Must Balance Restraints for Confidentiality
230605 -
230606 - 7. Suggestion to check out a list of Traction resources on the
230607 - Internet, ref DRT 1 RG4K requires a log in process at a very
230608 - long address, beginning with....
230609 -
230610 - http://tractionserver.com
230611 -
230612 - ....and continuing with along bunch of stuff.
230614 - ..
230615 - This may be useful for controlling access to the record that
230616 - maintains confidentiality.
230617 - ..
230618 - The list of resources may summarize these attachments in
230619 - some way for demonstrating Traction work product tracks
230620 - chronology.
230622 - ..
230623 - Delay accessing intelligence causes cursory understanding when
230624 - people take short cuts preparing analysis for reasons cited by
230625 - Jack Park on 010908, ref SDS 28 0001, Cursory understanding
230626 - causes continual bumbling, making communication the biggest
230627 - risk in enterprise. This dynamic requires balancing restraints
230628 - on access that take extra time to preserve legitimate interests
230629 - in confidentiality, with the corollary risk that harm avoided
230630 - by strong confidentiality is offset by far greater harm from
230631 - mistake, loss, conflict, crisis and calamity due to lack of
230632 - timely intelligence, as set out in POIMS. ref OF 1 V8P1
230633 - ..
230634 - Examples are reports of too many people having too many
230635 - problems causing the economy to decline on 001207, ref SDS 23
230636 - V54M, and more recently on 010911 lack of analysis damaged
230637 - national security. ref SDS 29 UP5K
230638 -
230639 -
230640 -
2307 -
SUBJECTS
Analysis Context Supports Engelbart's Call for Intelligence
Listening Understanding Follow Up Make Communication Getting
Context Management Positions Information Sources and Times Showing Ca
Organizational Memory Knowledge Repository History, Experience, Lesso
3406 -
340701 - ..
340702 - Organizational Memory Supported by Traction
340703 - Traction Support for Analysis Enables Engelbart's Intelligence
340704 - Analysis Planning Links to Context Supported by Traction
340705 -
340706 -
340707 - 8. Traction work product evidently prepared or updated by Gregory
340708 - on 000405 about Doug Engelbart recommending consideration of
340709 - Traction for supporting a Dynamic Knowledge Repository (DKR);
340710 - includes planning for Chris to meet with OHS/DKR group.
340711 - ref DRT 1 NJ7J
340713 - ..
340714 - This is a good example using Traction for analysis and
340715 - planning, i.e., using the record of work performed to figure
340716 - what work to do, within the meaning of POIMS management cycle
340717 - for adding intelligence to daily information. ref OF 1 6649
340718 - This shows Traction is capable of providing links to relevant
340719 - context for fast access to the record that saves time and
340720 - money, as called out in Traction's overview reported on 000326.
340721 - ref SDS 7 XM4J The fact that links go to a log in screen,
340722 - which wastes time, may be avoidable for inhouse access to speed
340723 - things along.
340724 -
340725 - [...below, review indicates minimal use of chronology,
340726 - context, and connections, suggesting tools may not be
340727 - efficient to use for daily work. ref SDS 0 RL8G
340729 - ..
340730 - 9. Doug's letter on 000326 commending the Traction program for
340731 - knowledge management. ref DRT 1 HO5J
340733 - ..
340734 - This letter, ref DRP 1 0001, was reviewed 000326. ref SDS 7
340735 - 0001
340737 - ..
340738 - No connections in Traction record to Chris' record on the same
340739 - meeting, nor to prior related events, and nothing linked to
340740 - follow up; no analysis of relevance and context.
340742 - ..
340743 - 10. Eric Armstrong's letter on 000327 commenting favorably on
340744 - Traction support for categorizing. ref DRT 1 0542
340746 - ..
340747 - This letter, ref DRP 2 0001, was reviewed previously on 000327.
340748 - ref SDS 9 1350
340750 - ..
340751 - No connections to correlations with Traction objectives and
340752 - capabilities. and nothing linked to follow up nor to
340753 - background; no analysis of relevance and context.
340754 -
340755 -
340756 -
340757 -
3408 -
SUBJECTS
Email Organizing Web Journal System Solves Information Overload Solve
XML Editor Draws on Doug Engelbart's Vision for Intelligence
Limitations Inline Links Not Supported Transclusions
4105 -
410601 - ..
410602 - Email Improved by Traction XML Parser and Translator
410603 - XML Parser, Translator Supported by Traction to Improve Email
410604 -
410606 - ..
410607 - 11. Eric Armstrong's letter on 000825 reporting on meeting with
410608 - Doug Engelbart to discuss OHS design. ref DRT 1 2Y4O
410610 - ..
410611 - This letter, ref DRP 3 0001, was reviewed 000824 ref SDS 18
410612 - 0001
410614 - ..
410615 - There is no express explanation of why Traction shows this
410616 - letter on 000825. The Bootstrap archive shows 000824....
410617 -
410618 - http://www.bootstrap.org/dkr/discussion/1646.html
410620 - ..
410621 - 12. Traction comments on Eric's report about translating plain text
410622 - into XML and then again into HTML for display on a browser.
410623 - ref DRT 1 QM6J
410625 - ..
410626 - Chris notes this goes a little further than Traction, which
410627 - takes HTML or text mail and redisplays it, without the
410628 - translation to a cannonical XML representation. It is fed
410629 - through an XML parser and translator to make it valid.
410630 - ref DRT 1 TE7H
410632 - ..
410633 - How does this correlate to presentation by Chris 000413
410634 - indicating that Traction uses XML for something? ref SDS 10
410635 - 4209
410637 - ..
410638 - Where are connections to the record of Traction capability, and
410639 - analysis of usefulness based on experience showing a deficit
410640 - that needs to be addressed, or an irrelevance because Traction
410641 - has proven to save time and money without such capability?
410642 -
410643 - [...below, review indicates minimal use of chronology,
410644 - context, and connections, suggesting tools may not be
410645 - efficient to use for daily work. ref SDS 0 RL8G
410647 - ..
410648 - 13. Traction comments on Eric's report about idea to siphon off
410649 - standard email messages to build a better email archive.
410650 - ref DRT 1 U17G
410652 - ..
410653 - CJN notes part of Traction's charter, in addition to handling
410654 - web pages and other documents, e.g. Word. ref DRT 1 PUUT
410656 - ..
410657 - Where is link to Traction charter that supports this assertion?
410658 -
410659 -
410660 -
410661 -
4107 -
SUBJECTS
Category Support OHS/DKR, Eric Armstrong
Information Retrieval Reporting Based on Subject Context
4404 -
440501 - ..
440502 - Categories Strong Suit for Traction
440503 -
440504 - 14. Traction comments on Eric's support for categories, ref DRT 1
440505 - NO4N, which aligns with Eric's report on 000327, ref SDS 9 1350,
440506 - and later on 000414. ref SDS 11 1350
440508 - ..
440509 - More recently, on 011003 Eric strongly noted need for
440510 - categories to solve information overload. ref SDS 36 EC5N At
440511 - that time, on 011003 Eric was frustrated because information
440512 - density paralizes productivity; Eric hoped for a system of
440513 - categories to make finding critical details fast and easy.
440514 - ref SDS 36 SW9L
440516 - ..
440517 - Chris notes Traction addresses these concerns comprehensively.
440518 - ref DRT 1 761R
440520 - ..
440521 - Review of Traction work product does not demonstrate support
440522 - for subjects that make analysis fast and easy by finding
440523 - critical details to construct connections that verify accuracy
440524 - and manage context. ref SDS 0 0Y78
440526 - ..
440527 - [On 041208 Murray Altheim requests feedback on pilot
440528 - testing his software project for organizing notes into
440529 - different subjects that aid writing; a survey
440530 - illustrates how to engage customers in paying attention
440531 - to Cyerle for supporting tasks people care about.
440532 - ref SDS 42 P67J
440533 -
440534 -
440535 -
440536 -
4406 -
SUBJECTS
Links Provide Context
Welch POIMS Cited No Links Analysis
Traceability Original Sources Links Missing from Traction Work Produc
4805 -
480601 - ..
480602 - Linking to Original Sources Supported by Traction
480603 -
480604 - 15. Traction comments on Eric's analysis of Rod Welch system
480605 - that links to original sources. ref DRT 1 2W6M
480606 -
480607 - Chris notes easy to do a pass-through; send mail to archive,
480608 - with a CC line. Archive can perform necessary XML translations,
480609 - add links, render in HTML and then forward along to the people
480610 - and return a receipt to the sender. ref DRT 1 PVRY
480612 - ..
480613 - No links are shown and no analysis is presented in Traction
480614 - work product showing anything about the Welch system, explained
480615 - for example in POIMS.....
480616 -
480617 - Traceability original sources.............. ref OF 1 QT5L
480618 - Accountability............................. ref OF 1 KE1T
480619 - Alignment.................................. ref OF 1 2049
480620 -
480621 - ....despite Traction awareness of Welch system reported in
480622 - planning on 000412 for Chris' trip to SRI on 000413. ref SDS 0
480623 - EQ4M
480624 -
480625 -
480626 -
480627 -
480628 -
480629 -
4807 -
SUBJECTS
Email Organizing Web Journal System Solves Information Overload Solve
Armstrong, Eric Reply in Context for Email Enabled by Traction Why Is
Email Core Capability DKR, Collaboration, Eric, 000505
Email Reply in Context, Eric Armstrong 000824
Search Information Retrieval Reporting Based on Subject Context
5607 -
560801 - ..
560802 - Email Reply in Context Supported by Traction
560803 -
560805 - ..
560806 - 16. Traction supports system Eric wants that delivers a reply "in
560807 - context" so that it appears as part of the original message.
560808 - ref DRT 1 YF4N Chris' letter today, seems to demonstrate this
560809 - capability.
560811 - ..
560812 - Chris notes Traction's time dimension features really let you
560813 - work the way Eric wants. ref DRT 1 PB5H
560815 - ..
560816 - Eric's objective was reviewed on 000824, discussing meaning of
560817 - "context." ref SDS 18 G92D
560819 - ..
560820 - All of the work product submitted by Traction today seems to
560821 - meet this requirement. ref SDS 0 3D4H
560823 - ..
560824 - Why isn't Eric using Traction? Is cost an issue? How much
560825 - does Traction cost to help people develop work product like
560826 - Eric wants, and how much time and money does this save?
560827 -
560829 - ..
560830 - Email Search Enabled by Traction
560831 - Search Email Supported by Traction
560832 -
560833 -
560834 - 17. Traction supports system Eric wants to search email. ref DRT 1
560835 - AM6O
560836 -
560837 - 18. Traction support for categories provide capability Eric wants.
560838 - ref DRT 1 01F7
560840 - ..
560841 - 19. Traction work product dated 000421 shows letter from Mary
560842 - Coppernoll dated 000417 submitting a list of people who
560843 - attended the meeting at SRI on 000413. ref DRT 1 PWSP
560844 -
560845 -
560846 -
5609 -
SUBJECTS
Demonstrate Traction Chris Nuzum
Work Product Showing Traction Adds Value to Meeting on 000413 Will be
Open Source Not Marketing Model Adopted by Traction, Chris
Armstrong, Eric Recommends Traction be Used for OHS/DKR Development W
OHS/DKR Meeting at SRI 000413, Open Source Project
6207 -
620801 - ..
620802 - Meeting on 000413 Reported by Traction, Open Source Issue??
620803 - Demo on 000413 Successful, OHS/DKR Decided to Buy Traction
620804 - Traction Work Product Meeting on 000413 Shows Good Pictures
620805 -
620807 - ..
620808 - 20. Traction work product on presentation to Doug Engelbart's OHS
620809 - Group identified at Traction10795: 14 Apr 2000, 1:34 AM
620810 - (updated by cjn), ref DRT 1 VH5K
620812 - ..
620813 - This seems to be a report on the meeting at SRI on 000413 where
620814 - Chris Nuzum demonstrated Traction. ref SDS 10 4209
620816 - ..
620817 - Chris reports strong favorable (love) for Traction, as best
620818 - platform seen so far.
620820 - ..
620821 - Group decided to buy Traction or get a partner like IBM or Sun
620822 - to buy Traction.
620823 -
620824 - Aligns with Eric Armstrong's excellent recommendation on
620825 - 000414. ref SDS 11 3450
620826 -
620827 - On 001126 group decided to learn KM by using IT with
620828 - greater diligence. ref SDS 22 BY4K
620830 - ..
620831 - Open source issue needs review vis a vis Twisted System's
620832 - marketing objectives. ref DRT 1 MA6M
620833 -
620834 - No follow up showing what action was taken to address this
620835 - issue in light of interest expressed by OHS/DKR group in
620836 - the Traction program, reported on 000413. ref SDS 10 SX7J
620838 - ..
620839 - Doug Engelbart proposed bringing other Twisted System staff to
620840 - a follow up meeting. ref DRT 1 BC7J
620841 -
620842 - No follow up showing what action was taken to address this
620843 - issue.
620845 - ..
620846 - There are two pictures showing attendees with names of people
620847 - overlayed. ref DRT 1 PWYW
620849 - ..
620850 - Question mark on the picture of Pat Lincoln, shows action item
620851 - pending to complete the record. ref DRT 1 5G5L
620852 -
620853 - No follow up showing what action was taken to address this
620854 - issue, reported on 000413. Why create a question, if there
620855 - is no mechanism to follow up?
620857 - ..
620858 - Lee Iverson is identified as associated with Stanford, perhaps
620859 - a shortcut description of SRI.
620861 - ..
620862 - Traction has two links to IBM websites, ref DRT 1 0876, but
620863 - nothing in the meeting report is linked to any background, for
620864 - example to Chris' meeting with Doug earlier on 000321,
620865 - ref DRT 1 W96O, nor to any of Doug's papers showing alignment
620866 - with Traction capabilities, as shown for example on 991222.
620867 - ref SDS 5 OS8M
620868 -
620869 -
620870 -
620871 -
6209 -
SUBJECTS
Prepare for Effective Work Assemble Record for Chris to Demonstrate T
Welch POIMS Cited No Links Analysis
Meeting Productivity Improved by SDS Intelligence
70% Day Wasted Unproductive Meetings
7106 -
710701 - ..
710702 - Assemble Background to Be Prepared for Effective Work
710703 - Preparing for Effective Work Supported by Traction
710704 -
710706 - ..
710707 - 21. Traction link resources on background of Doug's ideas for
710708 - augmenting human intellect that contributed to developing
710709 - Traction. ref DRT 1 AH8K
710711 - ..
710712 - Traction link resources on background of OHS/DKR. ref DRT 1
710713 - XJ9N
710715 - ..
710716 - Traction link resources on discussion relating to DKS (possibly
710717 - DKR??) and Traction. ref DRT 1 QL4J
710718 -
710719 - These links go to a Traction location that requires a login
710720 - procedure.
710722 - ..
710723 - 22. Traction work product on 000412 that seems to be a memo from
710724 - Gregory R. Lloyd to Chris with links to correspondence, among
710725 - contributors to OHS/DKR, that can help Chris prepare for
710726 - demonstrating Traction at SRI on 000413. ref DRT 1 IQ5M For
710727 - some reason the address and date of the memo are shown below
710728 - the close. ref DRT 1 585L
710730 - ..
710731 - Eric Armstrong is credited for excellent analysis of issues on
710732 - DKR, knowledge representation, ref DRT 1 LX6M, and business
710733 - model. ref DRT 1 PY3N
710735 - ..
710736 - Doug is cited for journal cross links. ref DRT 1 0Z3L
710738 - ..
710739 - Welch journal capability provides a link to....
710740 -
710741 - http://www.welchco.com
710742 -
710743 - ....with suggestion to see "examples," but no examples are
710744 - provided, and there is no record of actual review. ref DRT 1
710745 - 7Y6F
710747 - ..
710748 - This record shows Traction helps people be prepared to take
710749 - effective action by assembling relevant background to review
710750 - before taking action, as explained on 950327. ref SDS 3 TM5G
710751 - Traction supports Covey's idea to first seek understanding then
710752 - prescribe. ref SDS 1 2229
710754 - ..
710755 - On 960205 report people waste 70% of day in meetings
710756 - because people are not prepared to work productively.
710757 - ref SDS 4 5902
710759 - ..
710760 - There is no record of research Twisted Systems may have done
710761 - following Gregory's letter on preparing for the meeting at SRI,
710762 - although there is an expressed intent to add comments, links
710763 - and suggestions, which likely reflects Traction's strong
710764 - capabilities.
710766 - ..
710767 - 23. Traction work product that seems to be a report on 000322
710768 - by Chris Nuzum relating a 2 hour meeting with Doug Engelbart on
710769 - 000321. ref DRT 1 W96O
710771 - ..
710772 - The report includes a picture of Chris and Doug......
710774 - ..
710775 - Chris quotes Doug saying....
710776 -
710777 - "Well this is fortuitous, I like this. I liked it, except it
710778 - leaves me stimulated." ref DRT 1 0Y8F
710779 -
710780 - This report aligns with Doug's recommendation on 000326
710781 - that OHS/DKR investigate Traction. ref SDS 7 0001
710783 - ..
710784 - In a two hour meeting, one or two big things demonstrated might
710785 - have been related in the record showing alignment with the list
710786 - of Traction capabilities reported on 000326. ref SDS 7 2365
710787 - For example, Chris might have demonstrated how Traction
710788 - provides...
710789 -
710790 - context that supports Doug's proposals for "intelligence"
710791 - collection, reviewed on 991222. ref SDS 5 8064
710793 - ..
710794 - accountability to support Doug's call for ABC continual
710795 - improvement, reviewed on 991222. ref SDS 5 3961
710796 -
710797 -
710798 -
710799 -
7108 -
SUBJECTS
Version Control Transclusion
Links Stable Version Control Major Concern Doug Engelbart at Meeting
Permanent Links Versioning Critical to Doug, Chris Nuzum Meeting with
Linking Core OHS Launch Plan, Doug Engelbart, 001025
7906 -
790701 - ..
790702 - Link Stability Critical Factor of Version Control
790703 - Versioning and Stable References Critical for Doug's Vision
790704 -
790705 -
790706 - Versioning/updating model was discussed.
790707 -
790708 - 24. Doug asked how Traction maintains stable references to an
790709 - intermediate state of an entry which has been updated, and also
790710 - about tagging large documents instead of many small ones.
790711 - ref DRT 1 SZ8K
790712 -
790713 - On 000327 discussed "stability" issue with Doug from related
790714 - perspective. ref SDS 8 8484
790716 - ..
790717 - On 000305 permanent addresses for stable links proposed by
790718 - Xanadu, Ted Nelson. ref SDS 6 0184
790720 - ..
790721 - This might be similar to Eric's specs for CDS reviewed on
790722 - 000614. ref SDS 17 6084
790724 - ..
790725 - Reflects Doug's emphasis on importance of linking in OHS
790726 - Launch plan submitted on 001025. ref SDS 20 BDU6
790727 -
790728 -
790729 -
790730 -
790731 -
790732 -
790733 -
790734 -
790735 -
7908 -
SUBJECTS
Compare Software Advantages Disadvanteges Doug Engelbart Wants System
Software Compare Advantages Disadvantages System to Evaluate Programs
Stable Technology Needed Improve Management Productivity Requires Tes
Information Overload
Rating System Evaluate Explosion of Choices for Technology
8407 -
840801 - ..
840802 - Evaluation System to Understand Compare Software Programs
840803 -
840804 - 25. Doug wanted a system which makes it easier to understand and
840805 - compare the advantages and disadvantages of systems like
840806 - Traction, at a very deep level, in order to guide development
840807 - of future systems and the choice of future prototype Dynamic
840808 - Knowledge Repositories. ref DRT 1 I59G
840809 -
840810 - Chris' report does not relate what was presented on this
840811 - matter.
840812 -
840813 - "Deep level" is not explained in Chris' report.
840815 - ..
840816 - On 011003 Eric Armstrong frustrated by too much information,
840817 - not enough time for evaluation, wants a rating system for
840818 - evaluating technologies. ref SDS 36 SW9L
840820 - ..
840821 - On 000327 discussed need for stability in fundamental tools,
840822 - like the alphabet, in order for people to work productively
840823 - in other fields. ref SDS 8 8484 Without stability, the mind
840824 - has no anchor, and so work is greatly slowed.
840826 - ..
840827 - Experience at SRI over the past two years shows that work
840828 - product is a good indication of usefulness, as requested for
840829 - Traction on 000413, ref SDS 10 HP5M, and again on 011031,
840830 - ref SDS 38 0001, and is provided today by Chris' letter.
840832 - ..
840833 - On 000413 attendees at the meeting where Chris demonstrated
840834 - Traction identified Using a system by the development and
840835 - sales staff is another good indicator of usefulness,
840836 - ref SDS 10 2520, as demonstrated by Chris in his letter today.
840838 - ..
840839 - Doug's article in 1992 proposes gaining experience pilot
840840 - testing systems in order to evaluate usefulness for saving
840841 - time and money. ref SDS 5 5402
840842 -
840843 -
840844 -
840845 -
840846 -
840847 -
840848 -
8409 -
SUBJECTS
Engelbart, Doug's Legacy Pleased Traction Used Papers to Guide Develo
Legacy Work Papers, Henry van Eykan Creating Web Site
Legacy Research Doug Engelbart Life Work Preserved
8805 -
880601 - ..
880602 - Papers by Engelbart Guided Development of Traction
880603 - Engelbart Legacy Advanced by Application in Traction
880604 - Legacy Doug Engelbart Advanced by Application in Traction
880605 -
880606 - 26. Doug was pleased that his papers have helped guide development
880607 - of Traction. ref DRT 1 YJ9M
880608 -
880609 - Traction provides several links to what seem to be Traction
880610 - Internet resources that show correlation with Doug's work.
880611 - Clicking on this stuff goes to a log in window, so not sure what
880612 - is actually presented.
880614 - ..
880615 - Traction application of Doug's papers and discussion in the
880616 - Traction record is a major step toward preserving a rich legacy
880617 - of Doug's contributions the past half century.
880618 -
880620 - ..
880621 - 27. Traction work product showing picture of last visit with Doug
880622 - on 001206 taken at Doug's home. Chris reports that a lot of
880623 - good pictures did not come out due to a failing SmartMedia
880624 - card. ref DRT 1 UK4K
880626 - ..
880627 - There is no explanation of what transpired during the meeting
880628 - and no action items are identified.
880630 - ..
880631 - There is an excellent picture of Chris and Doug at the
880632 - computer.
880634 - ..
880635 - 28. Traction lists additional linked resources on Doug Engelbart
880636 - and Bootstrap that are on file with Traction. ref DRT 1 6J3F
880637 -
880638 - These links go to a Traction location that requires a login
880639 - procedure.
880640 -
880641 -
880642 -
880643 -
8807 -
SUBJECTS
Evaluation Work Product
8903 -
890401 - ..
890402 - Traction Work Product Demonstrates Useful Capability
890403 - Implementation Raises Questions on Deployment, Functionality
890404 -
890405 - Chris' ability to pull relevant information from the Traction record
890406 - demonstrates use of categories, noted above, ref SDS 0 916Q, which
890407 - supports Eric Armstrong's assessment that this is an advantage for
890408 - improving email.
890410 - ..
890411 - Pictures are helpful for marketing, not terribly helpful for getting
890412 - things done.
890414 - ..
890415 - Follow up capability needs review, for example.......
890416 -
890417 - Open source needs imaginative solution........... ref SDS 0 CI9K
890418 - Picture with ? on Pat Lincoln.................... ref SDS 0 CI5N
890419 - Welch cited for review, but no follow up......... ref SDS 0 EQ4M
890421 - ..
890422 - Need examples where Traction is used to design the Traction program,
890423 - and write program code, as reported on 000413. ref SDS 10 2520
890425 - ..
890426 - Doesn't have to be complete so as to disclose IP, just indicate
890427 - process of using Traction for developing intelligence to strengthen
890428 - knowledge work.
890430 - ..
890431 - Would like to see Traction assemble the record on developing code for
890432 - adding addressability to the record, or where Doug's ideas have been
890433 - reviewed, and then incorporated into Traction design, and then coded
890434 - and tested for alignment with performance objectives. Anything along
890435 - these lines to show what the experts seem to call "granularity" that
890436 - is needed for effective analysis, will demonstrate usefulness and
890437 - power of Traction to enable command and control of the record.
890438 -
890439 -
890440 -
890441 -
890442 -
890443 -
890444 -
8905 -
SUBJECTS
Analysis Alignment Context Missing from Traction Work Product
9403 -
940401 - ..
940402 - Connections for Context to Build and Maintain Shared Meaning Missing
940403 -
940404 - Traction work product shows capability to connect relevant context,
940405 - ref SDS 0 915P, that supports analysis and alignment to expand
940406 - awareness and understanding called out in the overview of Traction
940407 - shown on 000326. ref SDS 7 2820
940408 -
940409 - [On 020619 Traction press release notifies of contract with
940410 - In-Q-Tel for using Traction. ref SDS 41 N987
940412 - ..
940413 - There is a consistent pattern of not linking the record backward or
940414 - forward to provide context with alignment and analysis that builds
940415 - shared meaning through chronology of cause and effect, despite
940416 - Traction capability to support this feature, see for example....
940417 -
940418 - Chris' memo planning talk to Rod.......011101, ref SDS 0 6G7K
940419 - Tim on Eric's 1st letter...............011031, ref SDS 0 GF8J
940420 - Chris on Eric's 2nd letter.............011031, ref SDS 0 RG9G
940421 - Chris on Rod's letter..................011031, ref SDS 0 TH5G
940422 - Chris' report meeting with Doug........000322, ref SDS 0 U24J
940423 - Doug's letter recommend Traction.......000326, ref SDS 0 WK5L
940424 - Eric's letter evaluate Traction........000327, ref SDS 0 ZM6K
940425 - Gregory's memo prepare for demo........000412, ref SDS 0 EQ4M
940426 - Eric's letter on SDS DKR architectr....000825, ref SDS 0 6H5L
940428 - ..
940429 - Lack of analysis may reflect limited time, inexperience, social issues
940430 - Jack Park raised on 010908, ref SDS 28 YF5O; or, deficit may indicate
940431 - Traction functionality is limited, and so is not fast and easy to use.
940432 - It might be easy to use, but is slow and awkward so folks rely on the
940433 - gist of things, rather than use subjects to locate relevant context
940434 - and create connections that add intelligence to organizational memory
940435 - for producing knowledge. Thus, even though categories are supported,
940436 - per above, ref SDS 0 S66F, if the application is not fast and easy nor
940437 - comprehensive, then it is only useful for preparing presentations that
940438 - justify investing a lot of time in order to make a sale.
940440 - ..
940441 - Review of Traction work product aligns with experience showing that
940442 - the CRIT team did not use CRIT to perform daily work, but rather fell
940443 - back on email, reported on 000420. ref SDS 12 4911
940444 -
940445 - [On 060129 CALO team that developed Open Iris is still getting
940446 - started using Open Iris. ref SDS 43 7A4F
940448 - ..
940449 - On 010720 work product by experienced engineer and executive does not
940450 - have context, analysis and alignment that is typical in an SDS record.
940451 - ref SDS 26 JG6M
940452 - ..
940453 - Review on 010924 indicates nobody seems to have discovered the
940454 - value of organizational memory, because nobody else produces it.
940455 - ref SDS 35 XT5F Traction may be perfectly capable of providing
940456 - support, but has not been applied to this task, as shown by the record
940457 - Chris submits today, perhaps for reasons Henry van Eykan explained on
940458 - 000926. ref SDS 19 004M
940459 - ..
940460 - Not sure at this point.
940462 - ..
940463 - Traction's overview in the record on 000327 describes providing
940464 - context, focus and accountability that tracks responsibilities showing
940465 - what needs to be done and progress on getting things done. ref SDS 7
940466 - XM4J
940468 - ..
940469 - Traction comments, however, in the examples provided today do not
940470 - indicate how one thing is related to another, nor how anything is
940471 - connected to an objective, requirement or commitment. There are no
940472 - connections from the strong minds of people who enter comments in
940473 - Traction, in this case, Chris, Gregory and Tim.
940475 - ..
940476 - How then does Traction create connections of cause and effect that
940477 - provide context to build and maintain shared meaning called out in the
940478 - Traction product overview shown on 000326? ref SDS 7 XM4J
940479 -
940480 - [On 011105 asked Eric Armstrong about this point; he feels
940481 - hierarchial structures can help Traction. ref SDS 40 0001
940482 - ..
940483 - Are there other examples showing how context, focus/priority and
940484 - accountability are maintained with Traction?
940485 -
940486 -
940487 -
940488 -
940489 -
940490 -
940491 -
9405 -
SUBJECTS
SDS Compliments Traction Marketing Opportunity
Traction Marketing Compliments SDS
9604 -
960501 - ..
960502 - Marketing Opportunity SDS Compliments Traction
960503 -
960504 - The record of Traction capabilities, ref SDS 0 S66F, and indications
960505 - of limitations in work product, ref SDS 0 RL8G, suggests possible
960506 - complementary scope between Traction and SDS.....
960507 -
960508 - 1. Traction might be useful for sales staff to communicate with
960509 - customers, and for engineers, accountants, and executives to
960510 - communicate as a first line of intelligence gathering that is
960511 - fairly fast and easy. This needs to be verified.
960513 - ..
960514 - 2. SDS can use Traction input to develop "intelligence," as in
960515 - this record, ref SDS 0 KV6K, by applying the steps explained on
960516 - 001219. ref SDS 24 FO5M
960517 - ..
960518 - Traction user interface may enable people to develop the first
960519 - step of intelligence collection by gathering information. For many
960520 - people, this may be enough. as Jack Park calls out on 010908.
960521 - ref SDS 28 0001
960523 - ..
960524 - Eric Armstrong has consistently endorsed Traction's user interface,
960525 - most recently on 011031. ref SDS 38 U77O This could help draw an
960526 - audience of customers, who feel frustrated by limitations of email,
960527 - and so are ready to reach for a better result using Traction. Many
960528 - among the OHS/DKR group admit to frustrations about email. Some are
960529 - trying to use greater diligence, reported on 001126. ref SDS 22 BY4K
960530 - Others recognize it takes too much diligence to improve email,
960531 - ref SDS 22 X8PW, so a better technology is needed, very much like
960532 - saying we need a bigger backhoe to move all this mountain of dirt, or
960533 - a bigger pump to handle the flood of information that is washing over
960534 - the landscape of daily business.
960535 - ..
960536 - Some people, among the group who want better results, may see
960537 - value in adding alignment and analysis for reasons on 001207,
960538 - ref SDS 23 V54M, and more recently on 010911, ref SDS 29 UP5K, which
960539 - may be easier to develop using SDS, based on review of the Traction
960540 - record today. ref SDS 0 RL8G For those few, SDS might compliment
960541 - Traction.
960543 - ..
960544 - In other words, Traction does not need SDS, and SDS does not need
960545 - Traction to perform useful work that adds value to existing practice.
960547 - ..
960548 - There may be marketing leverage, however, in exploring ways to present
960549 - on the one hand an easy user interface for folks to gather a little
960550 - higher quality work product using Traction than is possible with
960551 - ordinary email, and for a few customers to further refine what is
960552 - created by Traction into useful knowledge using SDS.
960553 - ..
960554 - The only issue is how to create a customer? Many people
960555 - recognize value in SDS, as reported on 010907, ref SDS 27 KX3L, as is
960556 - surely the case with Traction. But people resist, despite need for
960557 - intelligence under analysis on 010908. ref SDS 28 L39G This requires
960558 - innovative marketing to overcome resistance.
960560 - ..
960561 - This is a possible nexus between SDS and Traction.
960562 -
960563 -
960564 - [On 011104 submitted letter to Chris on following up. ref SDS 39
960565 - 0001
960566 -
960567 - [On 020619 Traction being tried by CIA under contract with
960568 - In-Q-Tel. ref SDS 41 0001
960569 -
960570 -
960571 -
960572 -
960573 -
960574 -
960575 -
960576 -
960577 -
960578 -
960579 -
960580 -
9606 -
Distribution. . . . See "CONTACTS"