From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
lsf@lists.linux-foundation.org, linux-mm@kvack.org,
Jerome Glisse <jglisse@redhat.com>,
linux-fsdevel@vger.kernel.org, lsf-pc@lists.linux-foundation.org,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [Lsf] [LSF/MM] Preliminary agenda ? Anyone ... anyone ? Bueller ?
Date: Mon, 29 Apr 2019 08:31:52 -0400 [thread overview]
Message-ID: <yq11s1l0z7r.fsf@oracle.com> (raw)
In-Reply-To: <1556540228.3119.10.camel@HansenPartnership.com> (James Bottomley's message of "Mon, 29 Apr 2019 08:17:08 -0400")
James,
> But for this year, I'd just assume the "event partners" checkbox
> covers publication of attendee data to attendees, because if you
> assume the opposite, since you've asked no additional permission of
> your speakers either, that would make publishing the agenda a GDPR
> violation.
Speakers have proposed a topic by posting a message to a public mailing
list. Whereas not all attendees have indicated their desire to attend in
a public forum.
I don't think there's a problem publishing the list of people that sent
an ATTEND. My concern is the ones that didn't. And if the attendee list
is not comprehensive, I am not sure how helpful it is.
From a more practical perspective, I also don't have access to whether
people clicked the "event partners" box or not during registration.
Although I can reach out to LF and see whether I can get access to that
information.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-04-29 12:32 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 [this message]
2019-04-30 16:03 ` Jonathan Adams
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=yq11s1l0z7r.fsf@oracle.com \
--to=martin.petersen@oracle.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=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).