From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by dpdk.org (Postfix) with ESMTP id 3E7F15A0C for ; Fri, 23 Oct 2015 18:19:42 +0200 (CEST) Received: by wicfv8 with SMTP id fv8so39070922wic.0 for ; Fri, 23 Oct 2015 09:19:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=c2asXkDBAyUhSxAp8MgJZ/4XeVJ1G9/LBqYIF0CLx3M=; b=S1irZAnD0YfMtw1BN6cR6d0DCrDiki0YxGNIIy4C7K65JwebVXWonWUO+wz3WwWmj0 KPh5AJojEH4AH5CqqZGxz9VNMNwfjfDUFASW52iOi0oisoWAZ3hfLDnRRkiuPiMY5r1/ sACAUiBT5x9fuy88PQkdXZmGIz9mzg3nGCsijowYyyPj379XGyIE14dvLfygisovAv7i WtIlaW40m2yvWRA7wIHdTNWljhO5QhlxcuDKuPDvyH7f4xST9mO7PO7XmNH6mZ6nAKPG T774vShmYCTnXjTx4fphqkuxpNKDnuXGtUMIUfb554r8BUBBdN1B/4JvzhbvMTOjHikP XNvw== X-Received: by 10.180.198.43 with SMTP id iz11mr5598424wic.17.1445617181928; Fri, 23 Oct 2015 09:19:41 -0700 (PDT) MIME-Version: 1.0 Sender: marc.sune@gmail.com Received: by 10.27.136.85 with HTTP; Fri, 23 Oct 2015 09:19:22 -0700 (PDT) In-Reply-To: <562A4D49.1080108@redhat.com> References: <562A4D49.1080108@redhat.com> From: Marc Date: Fri, 23 Oct 2015 18:19:22 +0200 X-Google-Sender-Auth: NivbcZo3oGJ2o5o3u-e6Ksz_60g Message-ID: To: Dave Neary Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [RFC] location for DPDK related white papers X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Oct 2015 16:19:42 -0000 On 23 October 2015 at 17:07, Dave Neary 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 >