All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev01@lists.netfilter.org, Brenda Butler <bjb@mojatatu.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Richard Guy Briggs <rgb@tricolour.net>
Subject: Re: [netdev01] registration inconsistency
Date: Fri, 12 Dec 2014 08:12:15 -0500	[thread overview]
Message-ID: <548AE9AF.90902@mojatatu.com> (raw)
In-Reply-To: <1418387022.2470.26.camel@sipsolutions.net>

On 12/12/14 07:23, Johannes Berg wrote:
> On Fri, 2014-12-12 at 06:42 -0500, Jamal Hadi Salim wrote:
>
>> For workshops, you should go ahead and invite people you want.
>> If you want us to give codes to some people (means either they dont
>> have  to pay or get discounts) then ping bjb and/or myself.
>
> No no, I don't think any (many) people will need a discount.
>
>> I am not sure how we distinguish invited people vs not-invited. It
>> would be nice to be able to do so.
>> One way is to do what the IETF does; provide color coded badges?
>> Also:
>> Do you think we need to change the language on the web site
>> to avoid any confusion?
>
> I think the confusion is that the CFP and the website say the conference
> is going to be be 50% speakers and 50% invitation: "The netdev
> conference this year is structured to be 50/50 by-invitation and talk
> submission"
>
> Looking back at this, I think you meant that the *talks* were going to
> be 50/50 like that, but some people have contacted me about that they
> thought *attendance* was going to be like that. In fact I just glossed
> over it and until now thought the same!
>
> If I'm right that you meant *talks* then I think you should clarify that
> language and even send out a clarification as a reply to the CFP email.
>

I think i got it.
Either a reply or we fix the CFP on the website.
Ccing Richard.

cheers,
jamal

       reply	other threads:[~2014-12-12 13:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1418326801.15709.1.camel@sipsolutions.net>
     [not found] ` <5489F9B2.60306@mojatatu.com>
     [not found]   ` <1418375818.2470.0.camel@sipsolutions.net>
     [not found]     ` <548AD48A.9080009@mojatatu.com>
     [not found]       ` <1418387022.2470.26.camel@sipsolutions.net>
2014-12-12 13:12         ` Jamal Hadi Salim [this message]
2014-12-12 13:19           ` [netdev01] registration inconsistency Johannes Berg
2014-12-12 14:01             ` Richard Guy Briggs
2014-12-12 14:45               ` Jamal Hadi Salim

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=548AE9AF.90902@mojatatu.com \
    --to=jhs@mojatatu.com \
    --cc=bjb@mojatatu.com \
    --cc=johannes@sipsolutions.net \
    --cc=netdev01@lists.netfilter.org \
    --cc=netdev@vger.kernel.org \
    --cc=rgb@tricolour.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.