<br><font size=2 face="sans-serif">Al is correct; while the initial discussion
re subversion is somewhat interesting, there seems to be a rush to choose
a technology solution before the problem is understood.</font>
<br>
<br><font size=2 face="sans-serif">what's going on here needs to be treated
as a software development project. use cases neeed to be syndicated; the
forces and the dynamics of those forces need to be considered. then and
only then can the right team go off and engineer an initial solution...and
then that solution needs to be grown incrementally and iteratively.</font>
<br>
<br><font size=2 face="sans-serif">you may get a quick solution now, but
the muesum will pay for it big time in the future.</font>
<br>
<br><font size=2 face="sans-serif">Grady Booch<br>
IBM Fellow<br>
Voice: (303) 986-2405 <br>
Mobile: (303) 898-7091<br>
Fax: (303) 987-2141<br>
Video: (303) 795-6587/6626<br>
GPS: 39.620/-105.076<br>
Notes: Grady Booch/Boulder/IBM<br>
E-mail: gbooch@us.ibm.com<br>
Avatar: Alem Theas</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Al Kossow <aek@bitsavers.org></b>
</font>
<br><font size=1 face="sans-serif">Sent by: scc_active-bounces@computerhistory.org</font>
<p><font size=1 face="sans-serif">04/06/07 08:38 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">scc_active@computerhistory.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [SCC_Active_Members] Subversion
as a basis for software archive</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Van Snyder wrote:<br>
<br>
> How about CVS or SCCS? I think these are based on plain files.<br>
><br>
<br>
Would the collective 'we' on this list please refrain from suggesting<br>
solutions to this 'problem' until the museum staff has time to actually<br>
generate a REQUIREMENTS document?<br>
<br>
I'm sorry about being so blunt, but as an engineer I cannot understand<br>
how any sort of rational discussion on this subject can be made until<br>
the actual problem to solve is presented.<br>
<br>
<br>
_______________________________________________<br>
SCC_active mailing list<br>
SCC_active@computerhistory.org<br>
http://mail.computerhistory.org/mailman/listinfo/scc_active<br>
</font></tt>
<br>