Guys, (01)
Here's a recap of our meeting: (02)
//
PhilG-JonC-PPY_20050216a.txt (03)
* met at LeBoulanger 2005.02.16 started 07:00am
** PhilGust, JonathanCheyer & PeterYim (04)
* 1. What it would mean, in the context of this pilot project, to say (05)
we've successfully "preserved" NLS/Augment. (06)
** Task 1 -- Make publicly availabe a cloned version of AUGMENT
-- to get the licensing issues out of the way, and get a workable version (07)
of AUGMENT up on a publicly accessible space (like sourceforge) so that (08)
it can be viewed, installed, played around with and studied by anyone. (09)
** Task 2 -- restore a version of working AUGMENT on a platform that (010)
emulates its original native platform -- to be able to install AUGMENT (011)
image into a clean TOPS20/PDP-10 emulated platform (012)
** Task 3 -- release a version of AUGMENT that is built from its own (013)
source that can run on a platform that emulates its original native (014)
platform (015)
** Task 4 -- get a complete inventory of all the design, operations and (016)
training documentation, ... etc.; put them online, and made accessible (017)
through hyperlinking by anyone. (018)
** as a non-goal in this project - we should not include in the scope (019)
anything newe, we should stayed focussed on preservation (020)
* 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. (021)
** For Task 1: (022)
*** Boeing IPR release - public domain - [action: JohnToole]
*** contact Raylene and bring her into the team - [action: Phil]
*** get Doug's permission to allow Raylene and KenH to capture his (023)
AUGMENT image and expunge personal files - [action: Phil]
*** Have KenH & Raylene go to Doug's office and grab a complete image of (024)
Doug's working system in a single session. Raylene will be the only (025)
person to hold onto the image, until all personal files have been purged.
*** KenH will restore image on a linux box and verify that no personal (026)
files or deleted block are accessible (we'll call this a "clean clone")
*** document the above ....
*** the rest of "Task-1" to follow (027)
* 3. What resources do we need from the CHM to accomplish this. (028)
** a couple of linux workstations (at least one) and a couple of (029)
harddisks
** setup a collaborative work space - Peter & Jonathan volunteered to (030)
setup a collaborative work environment under <chm.cim3.net> [action: Phil (031)
to get CHM to endorse this.]
** people as listed in requirements on this recap
** find out if John Toole needs anything from us (Phil, Jon & Peter) (032)
before talking to Boeing. Suggest forwarding John the thread where we (033)
discussed IPR issues. [action: Phil to find out; we could have a (034)
meeting/conf-call on this too, if necessary]
** also, consider getting HP to release the TOPS20 source and associated (035)
IPR into the public domain; maybe even do this step before approaching (036)
Boeing [action: Phil to talk to JohnT on this.] (037)
* 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). (038)
** Active: PhilGust, JonathanCheyer, PeterYim,
*** try to recruit: KenHarrenstein, RaylenePak, ShinyaYamada, (039)
** Advisory: JohnToole, DougEngelbart, JakeFeinler, HenryLowood, (040)
BillDuvall;
*** try to recruit: ChristinaEngelbart, JeffRulifson, BillEnglish, (041)
CharlesIrby (042)
** we'll send out invitations to all potential advisors (and let them opt (043)
out, if they don't want to get involved, they way, we won't offend (044)
anyone.) (045)
* 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. (046)
** suggest having Doug as the "Distinguished Advisor" to this project, (047)
and let him decide how active he wants to be. He will have complete (048)
access to everything we do. (049)
** we could do periodic meetings at his home, besides the museum (050)
* 6. What tools will we use to collaborate and capture our work. (051)
** candidate <chm.cim3.net> -- a "community only" cwe as discussed above. (052)
Access provided to all members of the team, advisors, and all CHM (053)
personnel. [action: Phil will confirm to Peter & Jon later today] (054)
--
meeting adjourned 9:05am
notes by ppy/2005.02.16
// (055)
Cheers. -ppy
-- (056)
On Fri, 11 Feb 2005 14:22:30 -0800, Philip Gust <gust@nouveausystems.com> wrote:
> Well, then how about at the same place we met a couple of
> weeks ago, around 7am. Will that work for both of you?
>
> I'd like to propose that we try to get through the following things:
>
> 1. What it would mean, in the context of this pilot project, to
> say we've successfully "preserved" NLS/Augment.
>
> 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.
>
> 3. What resources do we need from the CHM to accomplish this.
>
> 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).
>
> 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.
>
> 6. What tools will we use to collaborate and capture our work.
>
> Please feel free to add or suggest changes to this list. Let me
> know if this works for everyone.
>
> Best regards,
>
>
> At 01:21 PM 2/11/2005, Peter Yim wrote:
> >Phil & Jonathan,
> >
> >Wednesday 2/16/05 early morning is fine with me. Mountain View is fine too.
> >
> >Phil, since you call the meeting, you decide where and when.
> >
> >Regards. -ppy
> >--
> >
> >Philip Gust wrote Fri, 11 Feb 2005 06:40:17 -0800:
> >>Jonathan,
> >>Wednesday early morning would be good for me. Peter, I'd prefer an initial
> >>face-to-face meeting as well. Kind of strange for a hard-core collaboration
> >>guy, I know, but there it is... If that's not possible by Wednesday,
> >>better to
> >>get a start on it using phone and other tools.
> >>If we can have an initial face-to-face meeting, which city is most
>convenient
> >>for everyone? Bucks over in is possible, but there's also the place we
> >>met in
> >>Mt. View before. We could even meet at my office (just down the street on
> >>Evelyn just past the 85 overpass) and I bring in breakfast.
> >>Let me know what you're all able to do.
> >>BTW, you can see in another email that I'm talking with Ken about getting
> >>a copy of the emulator up and running. Not sure if he needs to be at this
> >>initial planning meeting, but definitely want to keep him in the loop on
> >>future
> >>ones. Peter, since you have the best rapport with Doug, it would probably
> >>be best for him if you were to lead the discussion with him about how to
> >>"sanitize" a cloned copy of NLS/Augment, if that's something you're willing
> >>to take on. Let me know on this.
> >
> >>At 06:43 PM 2/10/2005, Jonathan Cheyer wrote:
> >>
> >>>Hi Phil,
> >>>
> >>>Since it sounds like Monday is out for Peter, and Tuesday morning is out
> >>>for you, then either Tuesday evening (6 pm or later) or Wednesday
> >>>morning (before 9 am) would be a good time.
> >>>
> >>>I always prefer to meet with people in person whenever possible, since I
> >>>spend enough time on the computer already :-). However, given Peter's
> >>>preference and especially if Ken can be convinced to join the working
> >>>group, it definitely makes sense to do much of the work virtually to
> >>>allow everyone the best opportunity to participate. Ken's email is
> >>>klh@panix.com.
> >>>
> >>>I also got a chance to speak with Raylene at Doug's party, and agree
> >>>with you that she would be a valuable person to include as well.
> >>>
> >>>Jonathan
> >>>
> >>>
> >>>
> >>>Philip Gust wrote:
> >>>
> >>>>Well, any time Tuesday or early Wednesday would work for me.
> >>>>I think that Jonathan needs to have the appointment be pre-work
> >>>>hours.
> >>>
> >>>
> >>>
> >>>Philip Gust
> >>>Nouveau Systems, Inc.
> >>>
> >>>phone: +1 650 961-7992
> >>>fax: +1 508 526-8142
> >>>
> >>>
> >>>mailto: gust@NouveauSystems.com
> >>
> >
> >
> >Philip Gust
> >Nouveau Systems, Inc.
> >
> >phone: +1 650 961-7992
> >fax: +1 508 526-8142
> >
> >
> >mailto: gust@NouveauSystems.com
>
> (057)
|