Karl, do you have any objections to restoring the link to the
summit.html doc down in the list of links? Though the content should
be merged into the Requirements doc, preserving the linkage to the
original documents for posterity's sake seems reasonable, on the
grounds that someday developers may wonder where even unsurprising
requirements came from (or which user segments they apply to).
Curious,
- Dan
On Fri, 17 Feb 2006, kfogel@tigris.org wrote:
...
> --- trunk/www/merge-tracking/requirements.html (original)
> +++ trunk/www/merge-tracking/requirements.html Fri Feb 17 01:17:53 2006
...
> @@ -28,8 +26,15 @@
>
> <div id="requirements">
>
> -<p style="color: red">TODO: Incorporate CollabNet Summit findings.
> -Remove redundancies.</p>
> +<p style="color: red">*** UNDER CONSTRUCTION ***</p>
> +
> +<p style="color: red">TODO:
> +Incorporate CollabNet Summit findings into
> +the material below. There is a lot of data in those findings not
> +reflected below. For the most part the summit results are not
> +surprising, but they represent the best writeup we have of certain
> +requirements that were formerly only hinted at tangentially on the
> +users@ list and in other forums.</p>
...
> @@ -216,9 +221,6 @@
> functional/design spec pages.</p>
>
> <ul>
> - <li><a href="summit.html">CollabNet Enterprise customer summit on
> - Merge Tracking</a></li>
> -
> <li><a
> href="http://svn.collab.net/repos/svn/trunk/notes/schema-tradeoffs.txt"
> >schema-tradeoffs.txt</a>: Search for the section called "Questions
- application/pgp-signature attachment: stored
Received on Mon Feb 20 06:41:39 2006