From: Bruce Richardson <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: David Young <dave@youngcopy.com>,
Thomas Monjalon <thomas@monjalon.net>, <dev@dpdk.org>
Subject: Re: [PATCH 0/6] docs: Unify Getting Started Guides
Date: Fri, 22 Sep 2023 16:54:26 +0100 [thread overview]
Message-ID: <ZQ24smLGL8Sttbdn@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CAJFAV8zxAAbdpQJupBxELvzmfiBH20wD7=qdwtbXD7pmoNiEAw@mail.gmail.com>
On Fri, Sep 22, 2023 at 04:47:55PM +0200, David Marchand wrote:
> Hello David,
>
> On Wed, Sep 20, 2023 at 5:49 PM David Young <dave@youngcopy.com> wrote:
> >
> > The separate Getting Started Guides for Linux, FreeBSD, and Windows have been
> > consolidated into a single, streamlined guide to simplify the user experience
> > and facilitate easier maintenance.
> >
> > David Young (6):
> > Section 1: Introduction
> > Section 2: Install and Build DPDK
> > Section 3: Setting up a System to Run DPDK Applications
> > Section 4: Running Applications
> > Section 5: Appendix
> > Section 6: Glossary
>
> From my understanding, existing copyright banners should be preserved
> by this reorganisation work.
> Yet I noticed a few Copyright banners dated 2025, please double check
> and fix them.
>
>
> Bruce, Thomas,
> An open question, if new docs are created, who should this work be
> attributed to? the dpdk contributors?
>
For this re-organisation, I expect the copyrights from the existing content
be preserved - merging if so necessary, e.g. a page merged from two
separate ones with differen copyright owners.
For brand new content, the way things look now, it's just likely to come from
existing DPDK experts, so they will apply their usual attributions AFAIK.
/Bruce
next prev parent reply other threads:[~2023-09-22 15:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 15:48 David Young
2023-09-20 15:48 ` [PATCH 1/6] Section 1: Introduction David Young
2023-09-25 11:30 ` Ferruh Yigit
2023-10-11 18:26 ` Dave Young
2023-09-20 15:48 ` [PATCH 2/6] Section 2: Install and Build DPDK David Young
2023-09-25 11:30 ` Ferruh Yigit
2023-09-25 12:20 ` Bruce Richardson
2023-09-25 16:05 ` Tyler Retzlaff
2023-10-12 18:08 ` Dave Young
2023-10-17 13:37 ` Tyler Retzlaff
2023-09-20 15:48 ` [PATCH 3/6] Section 3: Setting up a System to Run DPDK Applications David Young
2023-09-25 11:31 ` Ferruh Yigit
2023-09-25 12:22 ` Bruce Richardson
2023-10-12 17:32 ` Dave Young
2023-09-20 15:48 ` [PATCH 4/6] Section 4: Running Applications David Young
2023-09-25 11:32 ` Ferruh Yigit
2023-09-20 15:48 ` [PATCH 5/6] Section 5: Appendix David Young
2023-09-25 11:33 ` Ferruh Yigit
2023-09-25 11:52 ` Ferruh Yigit
2023-09-25 12:24 ` Bruce Richardson
2023-09-20 15:48 ` [PATCH 6/6] Section 6: Glossary David Young
2023-09-25 11:43 ` Ferruh Yigit
2023-09-22 4:15 ` [PATCH 0/6] docs: Unify Getting Started Guides Tyler Retzlaff
2023-09-22 14:47 ` David Marchand
2023-09-22 15:54 ` Bruce Richardson [this message]
2023-09-25 11:54 ` Ferruh Yigit
2023-10-11 18:34 ` Dave Young
2023-10-13 16:28 ` Bruce Richardson
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-all 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=ZQ24smLGL8Sttbdn@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dave@youngcopy.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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;
as well as URLs for NNTP newsgroup(s).