[68] in Tooltime

home help back first fref pref prev next nref lref last post

Tooltime meeting notes 4/9/96

daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Wed Apr 10 09:24:07 1996

Date: Wed, 10 Apr 1996 09:29:30 -0500
To: tooltime@MIT.EDU
From: wade@MIT.EDU (Steven Wade Neiterman)


April 9, 1996
Tooltime/Scopus Implementation Meeting

Summary:

1.  The team reviewed current status
2.  Announcement of project notebook available via the Web
3.  Next meeting Friday April 19 11:00 am 11-124A

--------------------------------------------------------------------
1. CURRENT STATUS:

ACQUIRE ADDITIONAL SERVER HARDWARE
  Ongoing meetings with Peter Kelley and calls into Scopus to help asses
  server needs.  Plan is to keep existing Sparc 20 in E40 for use as a
  development machine.  Acquire new server machine for production,
  located in W91.  Working with Peter on Business Continuity planning
  and risk assessment.

  Issues:  Which Solaris version will be on new production machine?.
  Wade would like to have at least afs support.  This eliminates Solaris
  2.5.  Solaris 2.4 would be ok as we can move to AFS support when
  available.

  Knowledge in Tcl is limited and amount of use is unknown.  The team
  mentioned some options to address this, including resources and
  learning (classes, books, etc.).  Needs further investigation.

  Question on where the Web server resides.  This will be investigated
  further.  Possible use of machine currently used by Lynne.

  Need hostname for new server, any ideas?

SCOPUS PROFESSIONAL SERVICES
  Barbara is working on signed consulting contract, waiting for reply
  from Scopus.  Fax from MIT on counter proposal sent on April 3.  Ten
  day configuration is largest implementation activity and has critical
  resource impact.

  Resource scheduling needs refinement.  For example,
  Lynne will be able available during the critical 10 day configuration
  However,  Sun training schedule may loom as possible conflict
  (if the implementation should be stretched out).

SPACE
  Planning on using Building 16-720 for meetings, testing and
  configuration.  Some flexibility to work in "home" office.

TIMELINE
  Still looking for mid to end of June deployment (1 1/2 months
  implementation plus two weeks help desk lead time).

HELP COORDINATING MEETING
  Help coordinating meeting held April 5, attending Barbara, Kim, Cec,
  Kevin, Harold, Wade.  Purpose is to review status and impact on
  current Help initiatives.  Next meeting is scheduled for April 12.

TECHNOLOGY TRANSFER
  Would like to involve staff who would be able to contribute knowledge
  to next round of business implementations.  Early stages of
  discussion, in addition to names, general ideas involve consulting with
  local experts, NICIT, OLC, CWIS, etc.

Note:  Additional status information can be found in the project
notebook.  Action items are listed in the notebook.

--------------------------------------------------------------------

2. PROJECT NOTEBOOK AVAILABLE VIA THE WEB:

Purpose of the project notebook is to communicate schedules, activities,
milestones and project methodology to team members, stakeholders and
community members.

First draft of project notebook is available via
  http://web.mit.edu/tooltime/www/scopus_notebook.html

  (it's also available from wade's home page:
   http://web.mit.edu/wade/www )

Looking for comments on right amount of information to archive and
communicate (as well as volunteers to help evolve web and communicaton
structure).

Two comments so far:
-  need project summary (any volunteers to write this?)
-  replace words pre-lab, lab, pilot, rollout (especially the word
   "pilot").  Possible alternative words - pre, alpha, beta, deploy.



home help back first fref pref prev next nref lref last post