public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Stephano Cetola" <stephano.cetola@linux.intel.com>
To: devel@edk2.groups.io
Cc: Rebecca Cran <rebecca@bluestop.org>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-announce] TianoCore Community Meeting Minutes
Date: Tue, 11 Jun 2019 09:40:01 -0700	[thread overview]
Message-ID: <b4e83fd4-d2a2-5967-f7fc-e487e989adc0@linux.intel.com> (raw)
In-Reply-To: <a594ec54-8aac-e3a4-1472-bd1396bed68d@bluestop.org>

On 6/11/2019 8:13 AM, Rebecca Cran wrote:
> 
> 
> 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.

Sure, that makes sense. We appreciate you taking the time to host the 
docs yourself. It's my hope that we can get the docs up on something 
like docs.tianocore.org, but we'll see how feasible that is. :)

> 
> 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 think Mike's hope (and please correct me if I'm wrong here Mike), is 
that we automate this process, and be sure that the doxygen docs work in 
concert with our current documentation setup.

What "in concert" looks like is probably up for debate. We want to be 
sure that people who are searching for documentation find both our 
current docs as well as the doxygen docs.

Cheers,
Stephano

      reply	other threads:[~2019-06-11 16:40 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 ` [edk2-announce] TianoCore Community Meeting Minutes rebecca
2019-06-11 16:40   ` Stephano Cetola [this message]

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=b4e83fd4-d2a2-5967-f7fc-e487e989adc0@linux.intel.com \
    --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