See also: IRC log
<scribe> scribenick: dauwhe
Bill_Kasdorf: Topic: Structural
Issues
... I like having a variety of formats and session
lengths
... we could team up 2 or 3 people in a panel approach for
certain topics
... and that allows us to accommodate more speakers
... I don't want a small number of hour-long sessions
... what are people's thoughts?
tzviya: I think it's a good idea
to have a mix
... most people didn't like the idea of panels, because we get
less content
Bill_Kasdorf: when I talk about a
panel, I'm thinking more of an hour-long session w/ 3 speakers
of 20min each
... I agree that the panels where people just talk is less
interesting
... for me, panel = group of shorter talks
leonard: a moderated panel can be useful, but multiple speakers on the same topic is good too
<pbelfanti> +1 re benefits of moderated panels
Cristina: yes, I agree with
moderation
... so people don't talk generally, but provide specific
information
pbelfanti: I agree, and it comes
down to preparation
... let's avoid the "comfy chair" sessions :)
Bill_Kasdorf: the moderator would need to prep with the speakers
Cristina: we should check slides,
avoid duplication
... there are some people who we could trust, but we'd often
need slides in advance
BillMcCoy: one step further... when you call it a panel some speakers get lazy
<Julian_Calderazi> +q
BillMcCoy: if every speaker
thinks they're giving a 7-minute ted talk and prepares, it will
be great
... don't call them panels, call them topical sessions
<laudrain> +1
BillMcCoy: make sure the people
in charge know that we don't expect "off the cuff" remarks. We
demand preparation.
... we want all the attendees to have a good experience.
... calling it a panel can result in laziness
tzviya: I prepare the best when
I'm given a clear idea what to do
... so we should tell the speakers what we expect from
them
... at BiB they organize around topics, which is a great
idea
Bill_Kasdorf: I agree... make it clear
<mateus-teixeira> +1 (flash talks/pechakucha style)
Julian_Calderazi: maybe 3 people
plus a moderator
... not less than three
Bill_Kasdorf: pithy but
content-rich presentations
... but since we're clustering people with different takes on a
subject, Q and A is important
... more engagement with audience is good
... discussion between speakers, and between speakers and
audience
... that's why you need moderator
Julian_Calderazi: I would be less
nervous if we could have slides in advance
... so we don't have duplicate topics etc
Bill_Kasdorf: slides in advance
are most important to exchange between "panel" speakers
... slide requirements are seldom enforced
tzviya: I prepare in advance, but
I'm polishing up to the end
... and I
... 'm often changing them up to the last minute
... most speakers do this
<laudrain> yes
Bill_Kasdorf: I'm mostly asking
for people to exchange with fellow speakers, but not
necessarily final
... to make sure speakers in a joint session know what others
are doing
... slides submitted in advance don't have to be final
<Julian_Calderazi> We could -only- request 'topics' but not strictly the final slides. So we could check no duplicate topics.
BillMcCoy: what role do we want
as a program committee after july 31?
... I would be thrilled if people volunteer to be "track
captains" to review content
... but we should think about this
... the second option is to give action items to me and w3T
Bill_Kasdorf: another variant
that works at SSP
... people at program committee are assigned to be a "shepard"
for one session
BillMcCoy: I think 'shepherd' is a good word; not sure if we'll have enough volunteers to have one per session
pbelfanti: preliminary slides are
good to promote engagement and collaboration
... which prompts adjustments
... the moderators will have to be involved
Bill_Kasdorf: we need to make clear who is responsible for each session
laudrain: having preso in advance
will help moderator to prepare questions
... even bring questions to speakers beforehand, so speakers
can prepare
Bill_Kasdorf: it's good for
moderators to have questions in reserve
... we have a variety of sessions, so we can talk about this
later in July
... too early to make structure right now.
... I want to talk about marketing
... we could publicize interviews with individual
speakers
... DBW did this
tzviya: first, we should not tie
ourself to one speaker format
... DBW marketed the hell out of it, but it became spam, and
made people mad
Bill_Kasdorf: that's one extreme,
the other extreme is sending an announcement out
... some interviews could be good
tzviya: I'd look at how
ebookcraft is marketed
... they do an announcement well in advance
... they ask speakers to write blog posts about their topics,
like a preview
... most of it is on twitter, so it's opt-in
... you're not bombarded with obnoxious emails
... interviews may be good, but so could be blog posts
Bill_Kasdorf: blog posts are
good, but that's asking for more work
... interviews may be easier
... a combination would be good
... not everyone is on social media
mateus-teixeira: love the blog
post idea, and keeping marketing limited
... the BEA/DBW marketing is so full of hype
... blogs give a truer session of what the talk is about
... and to reach out to their own communities
Bill_Kasdorf: and to have it done
well in advance
... and get feedback
BillMcCoy: w3c has a small
marketing budget
... focus on direct email to people who've been to other idpf
events, or bisg
... focus on reaching people who might be interested
... but it risks that we won't reach people in other spheres of
publishing
... do we expect magazine folks? how do we make that happen?
via IDEAlliance?
<tzviya> here's a blog post by derrick schultz in advance of his ebookcraft talk http://www.booknetcanada.ca/blog/2017/3/13/the-skills-ebook-creators-already-have-for-their-next-job
BillMcCoy: let's avoid
arm-twisting marketing
... we have a blog at w3c for major announcements, and maybe
even a press release
<tzviya> http://www.booknetcanada.ca/blog/2017/3/10/what-if-your-customers-arent-white by Leonicka Valcius before TechForum
BillMcCoy: most powerful message will be speakers to their own communities
tzviya: I posted some links to booknet canada blogs, written by speakers
BillMcCoy: is it required?
tzviya: it's optional, but
strongly encouraged
... and people like to do it
BillMcCoy: we can do stuff on w3c publishing blog
tzviya: I was thinking of five, not 40
<Julian_Calderazi> +q
Bill_Kasdorf: this is another advantage of the "shepherd" strategy; you have an individual relationship with speaker
<Julian_Calderazi> -q
Bill_Kasdorf: BillM, are there logistics thing we need to be addressing in this call?
BillMcCoy: we have a small budget
for speaker expenses
... some speakers can only come if they cover some travel
expenses
... as we get to the next phase, we'll have to be careful in
allocating those limited funds
... advance registration is looking good
... rest of w3m is wondering if anyone will come
... so it's good people are signing up
... we've arranged logistics to we can accommodate up to 300,
although the goal is 200
Bill_Kasdorf: what's the setup?
BillMcCoy: classroom style, with
chairs behind tables
... if we wanted 350, we could do rows of chairs only
Bill_Kasdorf: what about the front? is there a stage/podium?
BillMcCoy: there are two
different rooms
... Thu PM there's an AC meeting that will need one of the
larger rooms
... so we're still sorting out final room allocation
Bill_Kasdorf: what about AV?
BillMcCoy: whatever we can get for free we'll use
Julian_Calderazi: over 150 people we should expect elevated stage and screens
BillMcCoy: we have it
Cristina: on the marketing
part
... we need to contact major publishing magazines, and have an
article
Bill_Kasdorf: Karen has a list of those media contacts
Cristina: having an article will
be helpful--lots of people in the industry look at these
... we should be clear on discounts for organizations as soon
as possible
... like italian publishers association
Bill_Kasdorf: what needs to be done about relationships with other organiztaions
BillMcCoy: I can offer a 10%
discount to anyone; I'll be the point person for that
... I'm already working some discounts
I was holding off until I knew whether we would be limited to 200
scribe: we should go now on
discounts
... if you agree to do an email to your list, and if we can
approve the copy, then we're willing to do the discount and one
free pass
BillMcCoy: magazines might want advertisements
Bill_Kasdorf: we should think
internationally
... and we should think about other sectors... IDEAlliance,
SSP
<BillMcCoy> +1
Bill_Kasdorf: the more logos we get as sponsoring organization, the better messaging we get around being inclusive to subject areas
leonardr: we need to find other
outlets than just traditional publishers
... and speakers who will speak to those needs
BillMcCoy: talk to me about this, so we can start these promotion deals
<BillMcCoy> PDF Association?
Bill_Kasdorf: anyone else want to say something?
BillMcCoy: trying to close
keynote speakers
... one is tim o'reilly
... he wrote a book about everything (500 pages)
... so what would this audience wants tim oreilly to talk
about?
tzviya: machine learning would be the most interesting topic for this group
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/shepard/shepherd/ Succeeded: s/I"m/I'm/ Present: mateus-teixeira tzviya dauwhe bill_kasdorf BillMccoy laudrain pbelfanti Julian_Calderazi Cristina Leonardr Found ScribeNick: dauwhe Inferring Scribes: dauwhe WARNING: No "Topic:" lines found. WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 26 Jun 2017 Guessing minutes URL: http://www.w3.org/2017/06/26-pubsummit-minutes.html People with action items: WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]