DPDK website maintenance
 help / color / mirror / Atom feed
From: Rashid Khan <rkhan@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Jill Lovato <jlovato@linuxfoundation.org>,
	web@dpdk.org,  "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
	dpdk-techboard <techboard@dpdk.org>,
Subject: Re: [dpdk-web] [dpdk-govboard] pages "about" DPDK
Date: Tue, 1 Jun 2021 11:15:36 -0400	[thread overview]
Message-ID: <CAH__z=ZLWm7RtOgTo23dcOa4Ku+1EZ27g_nPbTLgXbi=FaS0kQ@mail.gmail.com> (raw)
In-Reply-To: <1993016.W4zrS009Xr@thomas>

Thomas I agree both those sections need to be updated and refreshed.
It might help to have links on different pages so that information is easy
to find.

I am not sure who or how we can update those pages
I mean who has the passwords / permissions / framework to make changes to
the project's website.

Jill or Thomas do you know the mechanical aspects of this?
Who how etc

On Mon, May 31, 2021 at 10:56 AM Thomas Monjalon <thomas@monjalon.net>

> Hi,
> I would like to discuss how to refresh the website pages
> "about" and "governance":
> https://www.dpdk.org/about/
> https://www.dpdk.org/about/governance/
> I think we can update the story telling and the timeline.
> About the "Technical Board", it is not updated and makes me think
> we should have just a link to https://core.dpdk.org/techboard/
> Actually the section could be completely removed because referenced
> below in the same page.
> About the "Governing Board", it should be updated or replaced
> by a link to https://www.dpdk.org/ecosystem/#members
> if company names are enough.

  reply	other threads:[~2021-06-01 15:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31 14:56 [dpdk-web] " Thomas Monjalon
2021-06-01 15:15 ` Rashid Khan [this message]
2021-06-01 15:25   ` [dpdk-web] [dpdk-govboard] " Jill Lovato

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='CAH__z=ZLWm7RtOgTo23dcOa4Ku+1EZ27g_nPbTLgXbi=FaS0kQ@mail.gmail.com' \
    --to=rkhan@redhat.com \
    --cc=govboard@dpdk.org \
    --cc=jlovato@linuxfoundation.org \
    --cc=techboard@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=tim.odriscoll@intel.com \
    --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).