BCM - Comments inline...
On Oct 16, 2006, at 4:22 PM, Brian Moseley wrote:
On 10/16/06, Priscilla Chung <[EMAIL PROTECTED]> wrote:
When I can I will put the images in the spec to keep everything in
one
place. In the meantime, if there are documents which are 20 pages
long, it
just make sense to link them to download etc. In addition,
proposals and
other technical documents which are written up on the wiki, will
also be
linked from the spec.
i also would prefer to have the images inline even though it makes the
document bigger. i'd really rather not have to download multiple files
and bounce back and forth between windows. page up and page down work
much better ;)
I suspect in this case, Priscilla is probably linking to ppt or pdf
storyboards. I do this as well in the Chandler desktop specs. Sure we
could add all this stuff inline but this is a lot of work for PPD we
would be having to update the same content multiple places. It's
sometimes nicer to keep these as a pdf rather than have them in the
specs directly anyhow since they are often part of other
presentations. On the desktop side, we often link to the same info
from 2-3 different specs. I can also see this happening on the Cosmo
side, we may link to a Chandler spec on the dashboard for instance.
In the Chandler sharing spec, I will also be linking to the
storyboards (the images we are talking about here).
Maintaining all these documents is really time consuming. Right now
we only have 1 single Cosmo spec but in the future we will probably
have several documents. I also see this cross-referencing to other
specs (Chandler) increasing in the future. Regardless of whether or
not these are documents, wiki pages etc, I don't think it's realistic
to have everything in one single page without any links at all. I
people would agree that it's more important that we have a central
document people know is up to date and where they can get to the most
current wiki pages (supporting docs) with accurate information rather
than being able to print out a single 70 page doc that may be
inconsistent.
Yes. Or as it stands now links to the technical specs on the wiki
pages. In
future I can make a link at the top to jump down to the code
design if
needed.
i suggest removing code design and any other tech sections from the
spec template. these will effectively be product requirements specs,
and any tech requirements and development tasks we derive from these
specs will be enumerated on the project wiki.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
