From: "Rebecca Cran" <rebecca@bsdio.com>
To: Leif Lindholm <quic_llindhol@quicinc.com>, devel@edk2.groups.io
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
Miki Demeter <miki.demeter@intel.com>,
michael.d.kinney@intel.com
Subject: Re: [edk2-devel] [PATCH tianocore-docs v3 2/2] Readme.md: Update the Gitbook documentation section
Date: Thu, 6 Apr 2023 09:32:29 -0600 [thread overview]
Message-ID: <2288c2f9-abce-5d95-73a8-8ae3a91fa962@bsdio.com> (raw)
In-Reply-To: <ZC6VLLmNJZ9zEnuY@qc-i7.hemma.eciton.net>
On 4/6/23 3:47 AM, Leif Lindholm wrote:
> On Thu, Apr 06, 2023 at 10:42:34 +0100, Leif Lindholm wrote:
>> On Wed, Apr 05, 2023 at 19:06:18 -0600, Rebecca Cran wrote:
>>> We no longer use Gitbook for publishing the documentation.
>>> Update the section to direct users to use the mailing list to
>>> send feedback, and since we use GitHub Flavored Markdown, remove the
>>> link to Gitbook.
>>>
>>> Contributed-under: TianoCore Contribution Agreement 1.1
>> We don't use that any more, please drop (old template?).
> Or, err, have we not fixed that for tianocore-docs?
> This feels suboptimal.
>
> Mike: is this something we can address?
I talked to Mike about this at the TianoCore Community Meeting a few
minutes ago, and our understanding is that the TianoCore Contribution
Agreement is still required for documentation.
If we want to drop it, it sounds like we'd need to figure out how to do
so for the docs.
--
Rebecca Cran
next prev parent reply other threads:[~2023-04-06 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 1:06 [PATCH tianocore-docs v3 0/2] Fix links to specifications, guides etc Rebecca Cran
2023-04-06 1:06 ` [PATCH tianocore-docs v3 1/2] Readme.md: convert links from Gitbook to Github Pages Rebecca Cran
2023-04-06 1:06 ` [PATCH tianocore-docs v3 2/2] Readme.md: Update the Gitbook documentation section Rebecca Cran
2023-04-06 1:40 ` [edk2-devel] " Michael D Kinney
2023-04-06 9:42 ` Leif Lindholm
[not found] ` <17534F32771376CE.3578@groups.io>
2023-04-06 9:47 ` Leif Lindholm
2023-04-06 15:32 ` Rebecca Cran [this message]
2023-04-06 16:28 ` Michael D Kinney
2023-04-17 12:18 ` Leif Lindholm
2023-04-24 0:03 ` Michael D Kinney
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=2288c2f9-abce-5d95-73a8-8ae3a91fa962@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