From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-web <web@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-web] Eliminate duplicated information on web page
Date: Wed, 12 Sep 2018 16:58:19 +0100 [thread overview]
Message-ID: <e4ab0f8e-329a-b70a-9608-d0495a197d0c@intel.com> (raw)
Moving discussion to its own thread. Copy-paste from original one as start:
> I recognized while checking for this, we have two contribute pages:
> https://www.dpdk.org/contribute/
> https://core.dpdk.org/contribute/
Yes, information is duplicated.
Given that most of it applies only to the core project, I think we should
remove the duplication and replace the content with some links.
On the page https://www.dpdk.org/contribute/ we can try to do a summary
about what is common to all dpdk.org projects: license, git, emails and bugzilla.
The main interest of this page is to show the mailing lists.
> And two techboard pages:
> https://www.dpdk.org/about/governance/#techboard
> https://core.dpdk.org/techboard/
The first one has already a link to the second one:
"The main DPDK project has a list of maintainers and a Technical Board."
So I think we can remove the "Technical Board" section from this page,
given this board is related only to the DPDK core project.
I would also suggest to rename "The main DPDK project"
to "The DPDK core project".
reply other threads:[~2018-09-12 15:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e4ab0f8e-329a-b70a-9608-d0495a197d0c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
/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).