DPDK patches and discussions
 help / color / mirror / Atom feed
From: Marc <marcdevel@gmail.com>
To: Dave Neary <dneary@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC] location for DPDK related white papers
Date: Fri, 23 Oct 2015 18:19:22 +0200	[thread overview]
Message-ID: <CAExC=0TDRUCb61CPA-GfxVtzRoV0ucMiJ_qhw-i2jk7tFxBD5Q@mail.gmail.com> (raw)
In-Reply-To: <562A4D49.1080108@redhat.com>

On 23 October 2015 at 17:07, Dave Neary <dneary@redhat.com> wrote:

> Hi,
>
> On 10/23/2015 06:28 AM, Mcnamara, John wrote:
> > We have had a few people wishing to submit DPDK related white papers.
> > These tend to focus on particular aspects of DPDK and don't fit into
> > any of the existing documents.
> >
> > Where should these be stored/made available? Some options:
> >
> > * In the repo, in RST format in a doc/guides/white_paper directory.
>
> This would be my preference. We could create PDF versions alongside
> them, but the sources should be editable (enables updates over time).
>

My two cents,

I would not pollute the code repository with the history of
whitepapers/papers. In addition and as said, there will be the need to
inevitably version binary files like images, which will increase the size
of the (code) repo quite rapidly.

I would, at most, use a separate git submodule in that location, only
populated at wish.

Having completely separate repository under dpdk.org or simply the PDFs/raw
RST in the website seem better options.

Marc


>
> > * On dpdk.org in PDF format.
> > * Elsewhere.
> >
> > Any comments, suggestions?
> Thanks,
> Dave.
>
>
> --
> Dave Neary - NFV/SDN Community Strategy
> Open Source and Standards, Red Hat - http://community.redhat.com
> Ph: +1-978-399-2182 / Cell: +1-978-799-3338
>

      reply	other threads:[~2015-10-23 16:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 10:28 Mcnamara, John
2015-10-23 13:41 ` Thomas Monjalon
2015-10-23 14:48   ` Mcnamara, John
2015-10-23 14:52     ` Thomas Monjalon
2015-10-23 13:48 ` Jay Rolette
2015-10-23 15:07 ` Dave Neary
2015-10-23 16:19   ` Marc [this message]

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='CAExC=0TDRUCb61CPA-GfxVtzRoV0ucMiJ_qhw-i2jk7tFxBD5Q@mail.gmail.com' \
    --to=marcdevel@gmail.com \
    --cc=dev@dpdk.org \
    --cc=dneary@redhat.com \
    /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).