NLS_Restoration Preliminary Discussion (8T)
Suggestion of meeting & agenda from Phil: (8U)
ref: http://chm.cim3.net/forum//nls-restore/2005-02/msg00007.html (8V)
From: Philip Gust <gust@nouveausystems.com> To: Peter Yim <peter.yim@cim3.com>, Jonathan Cheyer <jonathan@cheyer.biz> Date: Fri, 11 Feb 2005 14:22:30 -0800 Subject: Re: Initial NLS / Augment CHM meeting (8W)
... about at the same place we met a couple of weeks ago, around 7am. Will that work for both of you? (8X)
I'd like to propose that we try to get through the following things: (8Y)
1. What it would mean, in the context of this pilot project, to say we've successfully "preserved" NLS / Augment. (8Z)
2. What steps should we take and in what order to accomplish this between now and, say August, how to partition tasks, and in more detail what should be our initial set of milestones. (90)
3. What resources do we need from the CHM to accomplish this. (91)
4. Who should be part of the "active" group, and who we need to have as part of the "advisory" group (including ex-Augment members who don't want to actively participate by have critical knowledge, or people like Jake Feinler from CHM or Henry Lowood from Stanford). (92)
5. We need to consider Doug's role, since his participation is critical, yet his participation may fall somewhere between "active" and "advisory". He should feel as included as he wants and is able to Let's discuss how to create that space for him. (93)
6. What tools will we use to collaborate and capture our work. (94)
Please feel free to add or suggest changes to this list. Let me know if this works for everyone. (95)
Best regards, Phil (96)
Breakfast Meeting Wed Feb. 16, 2005 (97)
ppy/PhilG-JonC-PPY_20050216a.txt ref: http://chm.cim3.net/forum//nls-restore/2005-02/msg00039.html (98)
- Meeting at LeBoulanger Cafe (Mountain View, CA), Wed 2005.02.16 - 07:00~9:00am (99)
- Attendees: PhilGust, JonathanCheyer & PeterYim (9A)
- 1. What it would mean, in the context of this pilot project, to say we've successfully "preserved" NLS / Augment. (9B)
- Task 1 -- Make publicly availabe a cloned version of AUGMENT -- to get the licensing issues out of the way, and get a workable version of AUGMENT up on a publicly accessible space (like sourceforge) so that it can be viewed, installed, played around with and studied by anyone. (9C)
- Task 2 -- restore a version of working AUGMENT on a platform that emulates its original native platform -- to be able to install AUGMENT image into a clean TOPS20/PDP-10 emulated platform (9D)
- Task 3 -- release a version of AUGMENT that is built from its own source that can run on a platform that emulates its original native platform (9E)
- Task 4 -- get a complete inventory of all the design, operations and training documentation, ... etc.; put them online, and made accessible through hyperlinking by anyone. (9F)
- as a non-goal in this project - we should not include in the scope anything newe, we should stayed focussed on preservation (9G)
- 2. What steps should we take and in what order to accomplish
this between now and, say August, how to partition tasks, and
in more detail what should be our initial set of milestones. (9H)
- For Task 1: (9J)
- Boeing IPR release - public domain - [action: JohnToole] (9K)
- contact Raylene (RaylenePak) and bring her into the team - [action: Phil] (9L)
- get Doug's permission to allow Raylene and Ken (KenHarrenstein) to capture his AUGMENT image and expunge personal files - [action: Phil] (9M)
- Have Ken & Raylene go to Doug's office and grab a complete image of Doug's working system in a single session. Raylene will be the only person to hold onto the image, until all personal files have been purged. (9N)
- Ken will restore image on a linux box and verify that no personal files or deleted block are accessible (we'll call this a "clean clone") (9O)
- document the above .... (9P)
- the rest of "Task-1" to follow (9Q)
- For Task 1: (9J)
- 3. What resources do we need from the CHM to accomplish this. (9R)
- a couple of linux workstations (at least one) and a couple of harddisks (9S)
- setup a collaborative work space - Peter & Jonathan volunteered to setup a collaborative work environment under <chm.cim3.net> [action: Phil to get CHM to endorse this.] (9T)
- people as listed in requirements on this recap (9U)
- find out if John Toole needs anything from us (Phil, Jon & Peter) before talking to Boeing. Suggest forwarding John the thread where we discussed IPR issues. [action: Phil to find out; we could have a meeting/conf-call on this too, if necessary] (9V)
- also, consider getting HP to release the TOPS20 source and associated IPR into the public domain; maybe even do this step before approaching Boeing [action: Phil to talk to JohnToole on this.] (9W)
- 4. Who should be part of the "active" group, and who we need to
have as part of the "advisory" group (including ex-Augment members
who don't want to actively participate by have critical knowledge, or
people like Jake Feinler from CHM or Henry Lowood from Stanford). (9X)
- Active: PhilGust, JonathanCheyer, PeterYim, (9Y)
- try to recruit: KenHarrenstein, RaylenePak, ShinyaYamada, (9Z)
- Advisory: JohnToole, DougEngelbart, JakeFeinler, HenryLowood, BillDuvall; (A0)
- try to recruit: ChristinaEngelbart, JeffRulifson, BillEnglish, CharlesIrby (A1)
- we'll send out invitations to all potential advisors (and let them opt out, if they don't want to get involved, they way, we won't offend anyone.) (A2)
- Active: PhilGust, JonathanCheyer, PeterYim, (9Y)
- 5. We need to consider Doug's role, since his participation is critical, yet his participation may fall somewhere between "active" and "advisory". He should feel as included as he wants and is able to Let's discuss how to create that space for him. (A3)
- 6. What tools will we use to collaborate and capture our work. (A6)
- candidate <chm.cim3.net> -- a "community only" cwe as discussed above. Access provided to all members of the team, advisors, and all CHM personnel. [action: Phil will confirm to Peter & Jon later today] (A7)
-- meeting adjourned 9:05am notes by ppy/2005.02.16 (A8)