From: Stephen Hemminger <email@example.com> To: Thomas Monjalon <firstname.lastname@example.org> Cc: email@example.com Subject: Re: [dpdk-moving] Today's Meeting Date: Tue, 13 Dec 2016 11:22:41 -0800 Message-ID: <20161213112241.0f59103e@xeon-e3> (raw) In-Reply-To: <3536895.ot6KiLdWxE@xps13> On Tue, 13 Dec 2016 17:22:29 +0100 Thomas Monjalon <firstname.lastname@example.org> wrote: > I give some thoughts here because there is no time during the meeting > to talk between chatty people. I have same issue with phone meetings with > 3 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 Managing is often code word for some other problem: - how can I get my change accepted or - how can we reduce the number of unwanted contributions The most productive open source projects make it clear the state and requirements for getting patches accepted, DPDK is doing well on this. It is just that with there are more contributors than reviewers (could also be a trust issue). As far as more changes, outside original scope. I agree with Linus, who always wanted to make sure that some bluebird patch could be accepted at anytime. I.e no hard and fast roadmap limiting scope. > 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. Agreed.
next prev parent reply index 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 2016-12-13 19:22 ` Stephen Hemminger [this message] -- strict thread matches above, loose matches on Subject: below -- 2016-11-29 10:58 O'Driscoll, Tim
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=20161213112241.0f59103e@xeon-e3 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /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 community structure changes Archives are clonable: git clone --mirror http://inbox.dpdk.org/moving/0 moving/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 moving moving/ http://inbox.dpdk.org/moving \ firstname.lastname@example.org public-inbox-index moving Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.moving AGPL code for this site: git clone https://public-inbox.org/ public-inbox