From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: moving@dpdk.org
Subject: Re: [dpdk-moving] Today's Meeting
Date: Tue, 13 Dec 2016 17:22:29 +0100 [thread overview]
Message-ID: <3536895.ot6KiLdWxE@xps13> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA72279643@IRSMSX108.ger.corp.intel.com>
I give some thoughts here because there is no time during the meeting
to talk between chatty people.
First I agree some progress could be done in managing contributions.
Some progress could be done if people were giving some time.
Unfortunately a lot of people complain but do not give so much time.
There are basically 2 ways to give some time:
- work more on his own contribution (without being disturbed by other projects)
- review, test and give some opinions about other contributions or discussions
About the technical board, there is no point in using it if there is no
online discussion first. If you see a problem, use your mailer and tell it.
There is a real power in bringing some evidence to a public mailing list.
If you do not trust in the power of open discussions, an Open Source project
cannot do much for you.
next prev parent reply other threads:[~2016-12-13 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 11:23 O'Driscoll, Tim
2016-12-13 16:22 ` Thomas Monjalon [this message]
2016-12-13 19:22 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2016-11-29 10:58 O'Driscoll, Tim
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=3536895.ot6KiLdWxE@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=moving@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).