From: "Rebecca Cran" <rebecca@bsdio.com>
To: discuss@edk2.groups.io, michael.d.kinney@intel.com,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-discuss] [edk2-devel] EDK2 doxygen documentation - adding docs for stable tags?
Date: Wed, 10 Nov 2021 06:40:05 -0700 [thread overview]
Message-ID: <31e7130e-958a-a026-0b17-43ee57ea6773@bsdio.com> (raw)
In-Reply-To: <CO1PR11MB49290AB9E3FC3B4D7868B21FD2939@CO1PR11MB4929.namprd11.prod.outlook.com>
How easy it is to push changes to https://www.tianocore.org/ ? I had
thought that given how infrequently it's updated it's rather difficult,
but I agree that's the ideal location for the Doxygen pages. If it's
easier than I think, I have other changes I'd like to make such as
updating https://www.tianocore.org/news/ which hasn't been changed since
2018.
I agree it would be great if it could be a CI job somewhere: do we have
any existing scheduled jobs in EDK2 already, or is it something that
would need to be added?
Given that it was Stephano who originally said years ago that Doxygen
generation should be in the cloud, and how nothing has changed since I'm
skeptical about it, so for now I'll plan on setting up a scheduled job
on my Gitlab instance (https://gitlab.bsdio.com) instead and continue
publishing the pages on my site. But I'd be happy to help work towards
putting it on tianocore.org as long as we don't lose any functionality
in the process.
--
Rebecca Cran
On 11/9/21 7:27 PM, Michael D Kinney wrote:
> Hi Rebecca,
>
> Yes. They are useful. I would be better if it could be a CI job on either Azure pipelines
> or GitHub Actions could run the tool and publish the documents in TianoCore. Perhaps an on
> demand job against a specific tag.
>
> Mike
>
>> -----Original Message-----
>> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Rebecca Cran
>> Sent: Tuesday, November 9, 2021 3:20 PM
>> To: devel@edk2.groups.io; discuss@edk2.groups.io
>> Subject: [edk2-devel] EDK2 doxygen documentation - adding docs for stable tags?
>>
>> I've been hosting the Doxygen documentation for EDK2 at
>> https://bsdio.com/edk2/docs for a few years now. I previously had
>> versions for master, UDK2015, UDK2017, UDK2018 etc. but since migrating
>> my web server dropped everything except master.
>>
>>
>> I was wondering if people are finding it useful, and if so whether
>> they'd like me to generate documentation for each stable tag too?
>>
>>
>> Personally, _I_ find the web-based version (as opposed to a
>> locally-generated version) useful for the search feature -- being able
>> to quickly find the documentation for a certain function.
>>
>>
>> --
>>
>> Rebecca Cran
>>
>>
>>
>>
>>
>>
>
>
>
>
>
next prev parent reply other threads:[~2021-11-10 13:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 23:19 EDK2 doxygen documentation - adding docs for stable tags? Rebecca Cran
2021-11-10 2:27 ` [edk2-devel] " Michael D Kinney
2021-11-10 13:40 ` Rebecca Cran [this message]
2021-12-01 3:21 ` Michael D Kinney
2021-12-01 16:51 ` Rebecca Cran
2021-12-01 17:02 ` Michael D Kinney
2021-12-05 4:01 ` Michael D Kinney
2021-12-05 4:30 ` Rebecca Cran
2021-12-05 7:09 ` Michael D Kinney
2021-12-08 2:56 ` Rebecca Cran
2021-12-08 2:56 ` Rebecca Cran
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=31e7130e-958a-a026-0b17-43ee57ea6773@bsdio.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