From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: Diagrams
Date: Fri, 13 May 2011 14:45:24 -0700 [thread overview]
Message-ID: <1305323124.2023.26.camel@scimitar> (raw)
In-Reply-To: <DE8BA75F34A0404282AC5E15F691BC76D6B78F9B@orsmsx504.amr.corp.intel.com>
On Fri, 2011-05-13 at 14:07 -0700, Rifenbark, Scott M wrote:
> Currently I have been consistently using a ‘figures’ directory within
> each manual directory to house any PNG files used in a given manual.
> However, the Yocto-docs repository has a ‘diagrams’ folder at the same
> level as ‘documentation’. I think we should continue to keep figures
> with their respective books and not in some higher-level folder at the
> same level of documentation.
>
The benefit of the "store them all in the same folder" approach is that
I can easily find and view the diagrams which might be useful without
having to dig through several folders. I can of course understand the
alternative argument you make.
>
>
> This brings up some questions. Let’s say you have a figure that is
> somewhat universal and is used often by the community, such as this
> ‘oearch.png’ figure. But, the figure is also part of a manual. Do we
> keep the figure in the manual’s ‘figures’ folder exclusively? Or,
> duplicate the figure and keep it in the higher-level ‘diagrams’ folder
> as well?
>
>
>
> It goes against good practice to duplicate things so I would lean
> toward keeping the figures with the documents. And, if we have
> figures that are not used in any documentation we could keep them in
> the higher-level ‘diagrams’ folder.
>
>
>
> Thoughts?
>
I completely agree with the duplication point. I think git should handle
symlinks pretty well so we could store them all in the central directory
and link to the documentation sub-folders, or vice-versa?
Cheers,
Joshua
--
Joshua Lock
Yocto Build System Monkey
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-05-13 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 21:07 Diagrams Rifenbark, Scott M
2011-05-13 21:45 ` Joshua Lock [this message]
2011-05-13 21:59 ` Diagrams Rifenbark, Scott M
2011-05-16 9:06 ` Diagrams Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1305323124.2023.26.camel@scimitar \
--to=josh@linux.intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.