From: Ed Warnicke <hagbard@gmail.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: Francois Ozog <francois.ozog@linaro.org>,
"moving@dpdk.org" <moving@dpdk.org>,
Dave Neary <dneary@redhat.com>
Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, January 10th
Date: Thu, 12 Jan 2017 05:14:55 -0700 [thread overview]
Message-ID: <CAFVSqg39OqwaTkbNtxT=BLYEn0chY0QAWp5TyOm2e=sUJcy7XQ@mail.gmail.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA722A6EC0@IRSMSX108.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
Has the question of moving the infra (the actual servers/services behind
dpdk.org) over to LF come up?
Ed
On Thu, Jan 12, 2017 at 5:07 AM, O'Driscoll, Tim <tim.odriscoll@intel.com>
wrote:
>
>
> > From: Francois Ozog [mailto:francois.ozog@linaro.org]
> > Sent: Thursday, January 12, 2017 9:09 AM
> > To: O'Driscoll, Tim <tim.odriscoll@intel.com>
> > Cc: moving@dpdk.org; Dave Neary <dneary@redhat.com>
> > Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux
> Foundation" call, January 10th
> >
> > Hi,
> >
> > Thanks for the update.
> >
> > I have missed a couple of calls and did not found notes on the following
> topic: dpdk.org domain ownership.
> >
> > I think i has been a discussion topic during Dublin and thought that
> Dave Neary may have said (unsure) that it was assumed that the dpdk.org
> domain ownership should be transferred to LF.
> >
> > Was there a discussion/conclusion on this ?
>
> Yes, the question was asked during the discussion in Dublin (by Dave I
> think). This is what Dave captured in his minutes of that discussion:
>
> "When asked about transferring the ownership of the domain name to Linux
> Foundation, Vincent reiterated that his main concern was keeping the
> project open, and that he did not anticipate that transferring the
> domain ownership would be an issue."
>
> Vincent can confirm, but hopefully this means that there's no issue with
> this.
>
> >
> > Cordially,
> >
> > FF
>
>
[-- Attachment #2: Type: text/html, Size: 2302 bytes --]
next prev parent reply other threads:[~2017-01-12 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 22:16 O'Driscoll, Tim
2017-01-12 9:09 ` Francois Ozog
2017-01-12 12:07 ` O'Driscoll, Tim
2017-01-12 12:14 ` Ed Warnicke [this message]
2017-01-12 15:53 ` O'Driscoll, Tim
2017-01-12 12:47 ` Vincent JARDIN
2017-01-12 12:55 ` Vincent JARDIN
2017-01-13 5:12 ` Vincent Jardin
2017-01-17 14:19 ` Vincent JARDIN
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='CAFVSqg39OqwaTkbNtxT=BLYEn0chY0QAWp5TyOm2e=sUJcy7XQ@mail.gmail.com' \
--to=hagbard@gmail.com \
--cc=dneary@redhat.com \
--cc=francois.ozog@linaro.org \
--cc=moving@dpdk.org \
--cc=tim.odriscoll@intel.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
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).