From: rebecca@bluestop.org
To: Stephano Cetola <stephano.cetola@linux.intel.com>, devel@edk2.groups.io
Cc: "Cetola, Stephano" <stephano.cetola@intel.com>
Subject: Re: [edk2-announce] TianoCore Community Meeting Minutes
Date: Tue, 11 Jun 2019 09:13:31 -0600 [thread overview]
Message-ID: <a594ec54-8aac-e3a4-1472-bd1396bed68d@bluestop.org> (raw)
In-Reply-To: <6e17333f-f7bb-82d0-59ed-437a4c179980@linux.intel.com>
[replying to devel@]
On 2019-06-10 12:47, Stephano Cetola wrote:
>
> Documentation
> -------------
> Rebecca is hosting the Doxygen docs from packages on her server, and
> it is probably better if we use a cloud service to host these, or
> better yet, our current gitbooks system. However, there is a small
> issue with the way Doxygen changes folder structures between builds.
> Since we would be checking this into git (see:
> gitbook/TianoCore-Docs), it would cause a lot of git history
> thrashing. Mike has found ways around this, however we want to be sure
> that searching (particularly across packages) would be possible before
> we go down this road.
I should clarify that I don't mind hosting the doxygen docs: there seems
to be a move to have this sort of thing hosted on well-known cloud
services though, which is why I raised it.
I'm not sure gitbooks is the ideal solution, given that we'd likely lose
the current flexible search capability (e.g. see
https://code.bluestop.org/edk2/docs/doxygensearch.png), and possibly the
ability to cross-link the source code too?
I had a look at the directory structure my doxygen configuration is
generating, and it doesn't have any sub-directories at all: all 27,783
files (229 MB) for the github master docs are in the top-level directory.
--
Rebecca Cran
next parent reply other threads:[~2019-06-11 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6e17333f-f7bb-82d0-59ed-437a4c179980@linux.intel.com>
2019-06-11 15:13 ` rebecca [this message]
2019-06-11 16:40 ` [edk2-announce] TianoCore Community Meeting Minutes Stephano Cetola
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-list 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=a594ec54-8aac-e3a4-1472-bd1396bed68d@bluestop.org \
--to=devel@edk2.groups.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox