From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "moving@dpdk.org" <moving@dpdk.org>
Subject: [dpdk-moving] Weekly Meetings
Date: Fri, 4 Nov 2016 14:23:43 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA6760C9CA@IRSMSX108.ger.corp.intel.com> (raw)
I set up a weekly meeting to continue our discussions on moving to the Linux Foundation. I included the moving@dpdk.org mailing list on the distribution, but the meeting invite never seemed to reach the mailing list (I did get a message saying it needed to be approved by the moderator for some reason). Anyway, to make sure that everybody is aware of the meetings, here are the details:
Tuesdays from November 8th onwards. Currently I set the duration to 4 weeks but we can adjust that as required.
3pm GMT/4pm CET/7am PST/10am EST.
Access numbers:
France: +33 1588 77298
UK: +44 179340 2663
USA: +1 916 356 2663
Bridge Number: 5
Conference ID: 94641018
Join Skype Meeting: https://meet.intel.com/tim.odriscoll/G7H113HY
For next Tuesday's meeting, we'll discuss the following:
1. Budget. We'll review the budget that was proposed earlier this year and see if/how it needs to be changed. This is available at: https://docs.google.com/spreadsheets/d/1-3686Xb_jf4FtxdX8Mus9UwIxUb2vI_ppmJV5GnXcLg/edit#gid=302618256. I'm talking with Raghu and others from the LF team later today to understand their cost model if we want to create a DPDK CI lab, so we should have some input from that for Tuesday's discussion as well.
2. We discussed two possible approaches in Dublin: 1) move to LF with 0 budget as the OVS project did; 2) agree a budget and membership first and then move to LF. In Dublin we decided on option 2 and agreed to target having an updated budget within 4 weeks. I was asked about this again earlier in the week though, so we should touch on it again and make sure that we have a consensus on this.
3. Any other issues that people want to bring up. I know our validation team are working on a CI proposal, so if this is available in time we can discuss that as well.
reply other threads:[~2016-11-04 14:24 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=26FA93C7ED1EAA44AB77D62FBE1D27BA6760C9CA@IRSMSX108.ger.corp.intel.com \
--to=tim.odriscoll@intel.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).