From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"quic_llindhol@quicinc.com" <quic_llindhol@quicinc.com>
Cc: "rebecca@bsdio.com" <rebecca@bsdio.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
"Demeter, Miki" <miki.demeter@intel.com>,
"Kinney, Michael D" <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 16:28:57 +0000 [thread overview]
Message-ID: <CO1PR11MB4929BB420F8024CC4642B46FD2919@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <ZC6VLLmNJZ9zEnuY@qc-i7.hemma.eciton.net>
Hi Leif,
I am not sure. The current contributors agreement has support for code and documentation.
The specific sections on documents are:
* https://github.com/tianocore-docs/edk2-BuildSpecification/blob/db69f5661caec977fac9730e21e5a1132f6ff80b/CONTRIBUTIONS.txt#L29
* https://github.com/tianocore-docs/edk2-BuildSpecification/blob/db69f5661caec977fac9730e21e5a1132f6ff80b/CONTRIBUTIONS.txt#L60
There is an SPDX identifier for Free BSD Docs:
* https://spdx.org/licenses/FreeBSD-DOC.html
What is not clear to me is if a COO indicated by Signed-off-by
Combined with SPDX of FreeBSD-DOC is equivalent to the current
contributors agreement or not.
Can you evaluate?
Mike
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Leif Lindholm
> Sent: Thursday, April 6, 2023 2:47 AM
> To: devel@edk2.groups.io
> Cc: rebecca@bsdio.com; Ard Biesheuvel <ardb+tianocore@kernel.org>; Demeter, Miki <miki.demeter@intel.com>; Kinney, Michael
> D <michael.d.kinney@intel.com>
> Subject: Re: [edk2-devel] [PATCH tianocore-docs v3 2/2] Readme.md: Update the Gitbook documentation section
>
> 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?
>
> /
> Leif
>
> > With that:
> > Reviewed-by: Leif Lindholm <quic_llindhol@quicinc.com>
> >
> > > Signed-off-by: Rebecca Cran <rebecca@bsdio.com>
> > > ---
> > > Readme.md | 7 +++----
> > > 1 file changed, 3 insertions(+), 4 deletions(-)
> > >
> > > diff --git a/Readme.md b/Readme.md
> > > index 1e4a5d25bd6f..494b23af3ac7 100644
> > > --- a/Readme.md
> > > +++ b/Readme.md
> > > @@ -30,12 +30,11 @@ documentation.
> > >
> > > # EDK II GitBook Documents
> > >
> > > -These are the latest draft revisions published using [Gitbook](https://legacy.gitbook.com/).
> > > +These are the latest draft revisions.
> > > The source content for these documents are in GIT repositories in the
> > > [Tianocore-docs](https://github.com/tianocore-docs) organization hosted by [GitHub](https://github.com).
> > > -Feedback on these documents may be provided using the [Gitbook](https://www.gitbook.com) commenting feature
> > > -available when reading the **HTML** versions of the documents. Document issues and feature requests can also
> > > -be entered in [Tianocore Bugzilla](https://bugzilla.tianocore.org).
> > > +Feedback on these documents may be provided via the mailing list.
> > > +Document issues and feature requests can also be entered in [Tianocore Bugzilla](https://bugzilla.tianocore.org).
> > >
> > > * **_EDK II Build Specification_** \[
> > > [HTML ](https://tianocore-docs.github.io/edk2-BuildSpecification/draft/),
> > > --
> > > 2.39.2 (Apple Git-143)
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
>
>
>
next prev parent reply other threads:[~2023-04-06 16:29 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
2023-04-06 16:28 ` Michael D Kinney [this message]
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=CO1PR11MB4929BB420F8024CC4642B46FD2919@CO1PR11MB4929.namprd11.prod.outlook.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