TEAMSHARE SCHEDULING MEETING, 2000-08-24

Richard Brooksby, Ravenbrook Limited, 2000-08-24


1. INTRODUCTION

Richard Brooksby (Senior Consultant, Ravenbrook Limited) met Kelly Shaw
(Director of Strategic Alliances, TeamShare, Inc.) to discuss
TeamShare's commitments and schedules for implementing changes in
TeamTrack required by the Perforce Defect Tracking Integration project.

The purpose of this document is to record the decisions and commitments
made at the meeting.

The readership of this document is anyone interested in the project.

This document is not confidential.


2. MEETING SUMMARY

Larry Fish <larry.fish@teamshare.com> is the developer who will be
making the changes to TeamTrack.

TeamShare agrees to make the changes discussed to implement the
"replication" part of the integration [GDR 2000-08-18, sections 3.1 and
3.3] by the end of September, provided that Ravenbrook give them sample
data soon.

TeamShare is not willing to commit to a schedule for the
"tracker-client" part of the integration at this stage [GDR 2000-08-18,
section 3.2].  They would like to re-evaluate the situation once the
replication part is done.

TeamShare believe that, except for a use case for documentors, the 
tracker-client isn't significant, and that a link from the defect
tracking interface to Perforce's interface might be enough to solve 90%
of issues.

TeamShare won't add new permissions to limit source control operations
[GDR 2000-08-18, section 3.2.5] because that is hard to do in TeamTrack
version 4.  Instead, anyone with "VC" permission will be able to see
associated filespecs and changelists, and anyone in the "VC" group will
be able to edit them.  It's a bit of a kludge, but it will help to
prevent reworking of version 4.  New permissions will be possible in
TeamShare version 5.

TeamShare will send a couple of people to the Perforce User Conference.


A. REFERENCES

[GDR 2000-08-18] "TeamShare design meetings, 2000-08-14/2000-08-16";
Gareth Rees; Ravenbrook Limited; 2000-08-18.


Copyright (C) 2000 Ravenbrook Limited.  This document is provided "as
is", without any express or implied warranty.  In no event will the
authors be held liable for any damages arising from the use of this
document.  You may make and distribute verbatim copies of this document
provided that you do not charge a fee for this document or for its
distribution.

$Id: //info.ravenbrook.com/project/p4dti/doc/2000-08-24/teamshare-meeting/index.txt#1 $