DPDK website maintenance
 help / color / mirror / Atom feed
From: Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dpdk-web <web@dpdk.org>, Jill Lovato <jlovato@linuxfoundation.org>
Subject: Re: [dpdk-web] update of "Contribute" page
Date: Wed, 7 Aug 2019 11:09:42 -0400	[thread overview]
Message-ID: <CAFXL6f_X5+21qfg2rPXzKJzLs9aqz-rM+6YXcsWvoyq18QQPsA@mail.gmail.com> (raw)
In-Reply-To: <23028549.JrK2mSDJaO@xps>

Looks reasonable set of changes.

On Wed, Aug 7, 2019, 11:04 AM Thomas Monjalon <thomas@monjalon.net> wrote:

> Hi,
> I would like to propose an update of this page:
>         https://www.dpdk.org/contribute/
> It is supposed to be a welcome page for contributors of any DPDK project,
> not only the core one. So we can remove some redundancy with the page
> about contributing to DPDK Core.
> One more change: we have a new code.dpdk.org service to advertise.
> We can keep this introduction:
> "
> DPDK is an open source project, with the main code BSD licensed and Linux
> kernel related parts are naturally licensed under the GPL. We welcome and
> encourage anyone who is interested to contribute and participate in the
> project.
> "
> The second part of the introduction requires some changes:
> "
> The collaboration is based on git and emails. Coming patches are listed in
> patchwork. Bugs are open in bugzilla. The Technical Board may intermediate
> in the development process, as described in the Technical Board operation.
> "
> The link on "git" must be changed to http://git.dpdk.org so that it
> covers all repositories.
> The link on "emails" must be to the following section listing all
> mailing-lists.
> The link on "patchwork" must cover any possible new project:
> https://patches.dpdk.org
> The sentence about the roadmap is removed because specific to Core.
> The link on "bugzilla" must cover all projects: https://bugs.dpdk.org
> We should add a sentence to link to the "Contribute" page of the Core
> project:
> "
> The main project has specific informations for contributors.
> Other projects have their own documentation.
> "
> with "informations for contributors" being a link to
> https://core.dpdk.org/contribute
> and "documentation" being a link to https://www.dpdk.org/hosted-projects/
> The next section "Get the Code" can be replaced by a list of links to
> services
> available to the contributors:
>         - Code - code.dpdk.org
>         - Repositories - git.dpdk.org
>         - Patches - patches.dpdk.org
>         - Email archives - inbox.dpdk.org
>         - Bugs - bugs.dpdk.org
> The section "Mailing Lists" should stay as is.
> The section "Ways to Contribute" is an old copy of the Core project,
> so it should be completely removed from this general page.
> Any comment?

  reply	other threads:[~2019-08-07 15:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07 15:04 Thomas Monjalon
2019-08-07 15:09 ` Trishan de Lanerolle [this message]
2019-08-07 15:34   ` Jill Lovato
2019-08-07 15:50 ` Mcnamara, John
2019-08-07 16:07   ` Thomas Monjalon
2019-08-07 16:11     ` Jill Lovato
2019-08-10 22:29       ` Thomas Monjalon
2019-09-03 20:21         ` Thomas Monjalon
2019-09-03 20:46           ` Jill Lovato
2019-09-03 20:50             ` Thomas Monjalon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFXL6f_X5+21qfg2rPXzKJzLs9aqz-rM+6YXcsWvoyq18QQPsA@mail.gmail.com \
    --to=tdelanerolle@linuxfoundation.org \
    --cc=jlovato@linuxfoundation.org \
    --cc=thomas@monjalon.net \
    --cc=web@dpdk.org \


* 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).