DPDK website maintenance
 help / color / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jill Lovato <jlovato@linuxfoundation.org>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
	"tdelanerolle@linuxfoundation.org"
	<tdelanerolle@linuxfoundation.org>, "web@dpdk.org" <web@dpdk.org>
Subject: Re: [dpdk-web] update of "Contribute" page
Date: Sun, 11 Aug 2019 00:29:31 +0200
Message-ID: <2791642.xzzSW0cl1z@xps> (raw)
In-Reply-To: <CANA499GHZ=sQZrjYCcUCZ_GVvHs4drP6rDf_CPr3+Syvk9tYNA@mail.gmail.com>

Hi,

I'm reviewing the web page and see some inconsistencies with what
was written in this email thread, and I think about few improvements.

Please check comments from John below about "Incoming", "opened"
and "information" words, thanks.

About the section listing the services, I was expecting a section title,
like "Online Tools".
I think you can replace "Email archives" with just "Emails".
And instead of writing the URLs, it would be simpler to just keep the
name of the service (Code, Repositories, Patches, Emails, Bugs)
as the link itself. If you think of a better layout for this list,
like buttons on a row, feel free.

Thanks


07/08/2019 18:11, Jill Lovato:
> Yes, we'll get these updates in.
> 
> Thanks so much!
> 
> On Wed, Aug 7, 2019 at 9:07 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> 
> > 07/08/2019 17:50, Mcnamara, John:
> > > > 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.
> > >
> > > Some minor proposed changes to this section as follows:
> > >
> > > The collaboration is based on git and emails. Incoming patches are
> > listed in
> > > patchwork. Bugs are opened in bugzilla. The Technical Board may
> > intermediate
> > > in the development process, as described in the Technical Board
> > operation.
> > >
> > > > The main project has specific informations for contributors.
> > > > Other projects have their own documentation.
> > >
> > > The singular "information" would be better here.
> > >
> > > Otherwise +1.
> >
> > OK, thanks for the review John.
> >
> > Trishan, Jill, I think you can proceed with the above suggestions.
> > Thanks
> >
> >
> > > > -----Original Message-----
> > > > From: web [mailto:web-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> > > > Sent: Wednesday, August 7, 2019 4:05 PM
> > > > To: web@dpdk.org
> > > > Cc: Jill Lovato <jlovato@linuxfoundation.org>;
> > > > tdelanerolle@linuxfoundation.org
> > > > Subject: [dpdk-web] update of "Contribute" page
> > > >
> > > > 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 index

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
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 [this message]
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 publically 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=2791642.xzzSW0cl1z@xps \
    --to=thomas@monjalon.net \
    --cc=jlovato@linuxfoundation.org \
    --cc=john.mcnamara@intel.com \
    --cc=tdelanerolle@linuxfoundation.org \
    --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

DPDK website maintenance

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/web/0 web/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 web web/ http://inbox.dpdk.org/web \
		web@dpdk.org
	public-inbox-index web


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.web


AGPL code for this site: git clone https://public-inbox.org/ public-inbox