linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Adams <jwadams@google.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	Vlastimil Babka <vbabka@suse.cz>, Jens Axboe <axboe@kernel.dk>,
	lsf@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-block@vger.kernel.org, linux-mm@kvack.org,
	Jerome Glisse <jglisse@redhat.com>,
	linux-fsdevel@vger.kernel.org, lsf-pc@lists.linux-foundation.org
Subject: Re: [Lsf] [LSF/MM] Preliminary agenda ? Anyone ... anyone ? Bueller ?
Date: Tue, 30 Apr 2019 12:03:31 -0400	[thread overview]
Message-ID: <CA+VK+GP2R=6+GQJHX9+d6jnMWgK8i1_H5FiHdeUe3CGZZ5-86g@mail.gmail.com> (raw)
In-Reply-To: <yq1zho911sg.fsf@oracle.com>

On Mon, Apr 29, 2019 at 7:36 AM Martin K. Petersen
<martin.petersen@oracle.com> wrote:
>
>
> James,
>
> > Next year, simply expand the blurb to "sponsors, partners and
> > attendees" to make it more clear ... or better yet separate them so
> > people can opt out of partner spam and still be on the attendee list.
>
> We already made a note that we need an "opt-in to be on the attendee
> list" as part of the registration process next year. That's how other
> conferences go about it...

But there was an explicit checkbox to being on the attendance list in
the registration form, on the second page:

By submitting this registration you consent to The Linux’s
Foundation’s communication with you with respect to the event or
services to which this registration pertains.
* The Linux Foundation Communications ...
* Sponsor Communications    ...
* Attendee Directory
     By checking here, you opt-in to being listed in the event’s
online attendee directory. Some of your registration data will be made
available to other event attendees in the directory (name, title,
company name only)

Why isn't that sufficient?

Cheers,
- jonathan

  parent reply	other threads:[~2019-04-30 16:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 20:00 [LSF/MM] Preliminary agenda ? Anyone ... anyone ? Bueller ? Jerome Glisse
2019-04-25 20:03 ` Jens Axboe
2019-04-25 21:19   ` [LSF/MM TOPIC] Lightning round? Theodore Ts'o
2019-04-26  2:39     ` Jens Axboe
2019-04-26  5:20     ` Michal Hocko
2019-04-27 15:55   ` [LSF/MM] Preliminary agenda ? Anyone ... anyone ? Bueller ? Vlastimil Babka
2019-04-29 10:46     ` Martin K. Petersen
2019-04-29 11:31       ` [Lsf] " James Bottomley
2019-04-29 11:36         ` Martin K. Petersen
2019-04-29 12:17           ` James Bottomley
2019-04-29 12:31             ` Martin K. Petersen
2019-04-30 16:03           ` Jonathan Adams [this message]
2019-04-29 23:54   ` Scheduling conflicts Matthew Wilcox
2019-04-30 10:11     ` Michal Hocko

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='CA+VK+GP2R=6+GQJHX9+d6jnMWgK8i1_H5FiHdeUe3CGZZ5-86g@mail.gmail.com' \
    --to=jwadams@google.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=axboe@kernel.dk \
    --cc=jglisse@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=lsf@lists.linux-foundation.org \
    --cc=martin.petersen@oracle.com \
    --cc=vbabka@suse.cz \
    /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).