From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id C83092C55 for ; Wed, 29 Nov 2017 22:30:06 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 772B4209CA; Wed, 29 Nov 2017 16:30:06 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 29 Nov 2017 16:30:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=pKDicZUk81QwtkSYm/bD4AQgh0 XeBrR5RaVkQ/WEs6s=; b=Lhwz0ehBZJgOFtDBDRlA62DWbA58JePVnXqYgFGLOm aciVRNWAj3xsLvgDriWJEb1psGenF6s2N0PkIlFa+TLnNKn762lVJ67VMAKi93P4 P4esrx9uPx6I9FHrAcxxu0Tw0njYGMth0qXQ8q0j0B7B93vZRUNrbwSC6E0D+ZgB s= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=pKDicZ Uk81QwtkSYm/bD4AQgh0XeBrR5RaVkQ/WEs6s=; b=q9Uf5MfPoQte49A6HdBoOd H5kCx5eT/lfDmsPGZdg156HTpnZKJHE03xCOIaEjsF8nHeqF3Gx8WcMl66NFb2B/ 3YS2yI3iP5EAMtDU7o8XzBCJRlzhZpVz9Gp78RTIZGkJ/WCbidQbRS0oAyPCfZZ3 pOtouF/Pk1gmsd7q0YwaGmLEej8VzFYJEjdDtKsEAL6/Oyt8iUAmCwP0nx31Gvvk +telRnlCgCYo/uEl5B5A7xsYXBP5NGsUgIPZWym+nstYL9j/ymq2O3qQ6kmdraFR KGB0BBvnxk1sA6zS50HlM7K2+/f3Rc282+LkcADSRDfO+meny2ZmdBDmqSUVnBcw == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 2D4DD24C57; Wed, 29 Nov 2017 16:30:06 -0500 (EST) From: Thomas Monjalon To: web@dpdk.org Cc: qian.q.xu@intel.com Date: Wed, 29 Nov 2017 22:30:05 +0100 Message-ID: <2301009.brkiL0PioH@xps> In-Reply-To: <20171124210958.21544-1-thomas@monjalon.net> References: <20171124210958.21544-1-thomas@monjalon.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-web] [PATCH] add the bug tracker in the development process X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Nov 2017 21:30:07 -0000 Any comment? 24/11/2017 22:09, Thomas Monjalon: > Add two links to bugzilla in the dev page. > The first link at the top redirects to the open bugs. > The second link is provided in a new section about bug management. > > Signed-off-by: Thomas Monjalon > --- > dev.html | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/dev.html b/dev.html > index 34f24cf..3253fdd 100644 > --- a/dev.html > +++ b/dev.html > @@ -45,6 +45,8 @@ > Coming patches are listed in patchwork. >

Planned features are listed in the roadmap > and integrated during a cycle started by a merge window. > +

Bugs are open in + href="http://dpdk.org/tracker/buglist.cgi?bug_status=__open__&product=DPDK">bugzilla. > >

Licenses

>

Main code is BSD licensed and Linux kernel related parts are naturally licensed under the GPL. > @@ -134,6 +136,12 @@ >

Most of the patchwork actions can be done > with a pwclient command line. > > +

Contribute by finding or fixing bugs

> +

There is a bug tracker where > + anybody can notify a bug to the community, and follow the resolution. > +

A notification is sent to dev@dpdk.org for every new bug. > + The fixes must be sent and discussed on the mailing list. > + >

Technical Board

>

The Technical Board may intermediate in the development process, > as described in the Technical Board operation. >