From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=none, err=permanent DNS error (domain: linux.intel.com, ip: 192.55.52.88, mailfrom: stephano.cetola@linux.intel.com) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by groups.io with SMTP; Tue, 11 Jun 2019 09:40:03 -0700 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Jun 2019 09:40:02 -0700 X-ExtLoop1: 1 Received: from scetola-mobl1.amr.corp.intel.com (HELO [10.254.29.161]) ([10.254.29.161]) by orsmga007.jf.intel.com with ESMTP; 11 Jun 2019 09:40:01 -0700 Subject: Re: [edk2-announce] TianoCore Community Meeting Minutes To: devel@edk2.groups.io Cc: Rebecca Cran , "Kinney, Michael D" References: <6e17333f-f7bb-82d0-59ed-437a4c179980@linux.intel.com> From: "Stephano Cetola" Message-ID: Date: Tue, 11 Jun 2019 09:40:01 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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