[llvm-dev] Call for Talks, Tutorials, BoFs, Panels, Student Research Competition, and More!

Kristof Beyls via llvm-dev
Sat, 12 Aug 2017 17:20:16 -0000

Hi all,

We are extending the deadline until Monday the 14th, 11:59PM PDT.

Thanks,

Kristof

2017-08-07 14:51 GMT+02:00 Kristof Beyls <kristof.beyls at gmail.com>:

> Just a friendly reminder that you have until the end of this week to get
> in your proposals!
>
> Kristof
>
> 2017-07-12 7:57 GMT+02:00 Tanya Lattner via llvm-dev <
> llvm-dev at lists.llvm.org>:
>
>> Call for Talks, Tutorials, BoFs, Panels, Student Research Competition,
>> and More!
>>
>> All developers and users of LLVM and related sub-projects are invited
to
>> present at the 2017 LLVM Developers’ Meeting.
>>
>> We are looking for the following proposals:
>>
>>    1. Technical Talks (~30 minutes):
>>
>> - On LLVM Infrastructure,Clang and all related sub-projects
>> - On uses of LLVM in academia or industry
>> - On new projects using Clang or LLVM
>>
>>    1. Tutorials (~60 minutes)
>>
>> - In depth talks on LLVM infrastructure or other core libraries
>>
>>    1. NEW: Student Research Competition Technical Talks (~20 minutes)
>>    2. Lightning Talks (5 minutes, no questions, no discussions)
>>    3. Bird of a Feather
>>    <https://en.wikipedia.org/wiki/Birds_of_a_feather_(computing)>
(~30
>>    minutes)
>>    4. Panels (~30-60 minutes)
>>    5. Posters (1 hour)
>>
>>
>>
>> Submission Requirements:
>> The submission deadline is August 11, 2017 at 11:59PM PDT.
>>
>> Please submit your proposal here:
>> https://easychair.org/conferences/?conf=llvmdevmtg2017
>>
>> For each proposal, please submit a title, short abstract (to be used on
>> the website), note who the speakers and moderators are, and provide a
more
>> detailed description of the talk. We highly recommend you consult and
>> follow the guide at the end of this CFP when submitting your proposal.
>>
>> Student Research Competition (SRC):
>> We introduced the Student Research Competition at the most recent
>> EuroLLVM and are bringing it to the US LLVM Developers’ Meeting as
well.
>> The SRC offers students doing LLVM related research a non-academic
>> platform to announce and advertise their work as well as to discuss it
with
>> other researchers, developers and users of LLVM. Students are asked to
>> submit a proposal for a 20 minute technical talk. There will be a prize
for
>> the best SRC talk.
>>
>>
>> FAQ
>>
>> When will I be notified of acceptance?
>>
>> Our goal is to notify all proposal submitters by September 1, 2017.
>>
>> What are panels?
>>
>> Panels may discuss any topic as long as it’s relevant to LLVM or
related
>> sub-projects. Panels can take many forms, but a common format is to
begin
>> with an introduction of the panel members, have short presentations
from
>> each panel member, and follow with an interactive dialogue among the
>> panelists and audience members. Panels should consist of 3-5 people
>> including a moderator.
>>
>> Should I register if I have submitted a proposal?
>>
>> We have 1 complimentary reserved  registration for each accepted
>> technical talk, BoF, or student research competition talk. Accepted
>> tutorials have been reserved 2 complimentary registrations. Panels have
up
>> to 3 reserved registrations. There are no reserved registration spots
for
>> posters or lightning talks. So please register any additional speakers
or
>> if you do not have a reserved registration slot.
>>
>> What if I registered and my talk got accepted?
>>
>> We can refund your registration fee and instructions will be sent
>> following notification.  If you plan to attend even if your proposal is
not
>> accepted and are worried about the event selling out, we suggest
>> registering before notification of acceptance.
>>
>> What if I registered and my talk DID NOT get accepted?
>>
>> We can refund your registration fee if you no longer wish to attend if
>> you contact the organizer by September 15, 2017.
>>
>> What will be recorded?
>>
>> All technical talks, tutorials, SRC talks, panels, and lightning talks
>> will be recorded. By submitting your proposal, you are giving us
permission
>> to record if you present at the meeting. For SRC talks, you have the
option
>> to delay publication of the slides and video for you talk for up to 12
>> months.
>>
>> Who is on the program committee?
>>
>> Our program committee chair is Kristof Beyls. The program committee is
>> composed of active developers of the LLVM, Clang, and related
>> sub-communities. The website will be updated with the list of the
program
>> committee members.
>>
>> I have a question, who do I contact?
>>
>> Please email Tanya Lattner (tanyalattner at llvm.org), Kristof Beyls (
>> Kristof.Beyls at gmail.com), or the LLVM Developers’ Meeting mailing
list.
>> http://lists.llvm.org/mailman/listinfo/llvm-devmeeting
>>
>>
>> Detailed guidance on writing a proposal for the LLVM Developers’
Meeting
>>
>> Writing a proposal for the LLVM Developers’ Meeting
>>
>> This document is a guide to help you submit the best proposal and
>> increase your chances of your proposal being accepted. The LLVM
Developers’
>> Meeting program committee receives more proposals than can be accepted,
so
>> please read this guide careful.
>>
>> If you have never presented at an LLVM Developers’ Meeting, then do not
>> fear this process. We are actively looking for new speakers who are
excited
>> about LLVM and helping grow the community through these educational
talks!
>> You do not need to be a long time developer to submit a proposal.
>>
>> General Guidelines:
>>
>>    - It should be clear from your abstract what your topic is, who your
>>    targeted audience is, and what are the takeaways for attendees. The
program
>>    committee gets a lot of proposals and does not have time to read 10
page
>>    papers for each submission.
>>    - Talks about a use of LLVM (etc) should include details about how
>>    LLVM is used and not only be about the resulting application.
>>    - Tutorials on “how to use X” in LLVM (or other subproject) are
>>    greatly desired and beneficial to many developers. Entry level
topics are
>>    encouraged as well.
>>    - Talks that have been presented at other technical conferences tend
>>    to not get accepted. If you have presented this topic before, make
it clear
>>    what is new and different in your talk.
>>
>>
>>
>> Technical Talk and SRC Talk  Proposal Template:
>>
>> Title:
>>
>>    - This will be displayed on the website, schedule, and signs. Keep
it
>>    short and catchy to attract attendees to your talks. A couple of
examples
>>    are “WebAssembly: Here Be Dragons” or “Beyond Sanitizers: guided
fuzzing
>>    and security hardening”.
>>
>>
>> Speaker Name(s), Company, Email:
>>
>>    - This should be only the people giving the talk. EasyChair only
>>    allows you to select one speaker in its interface and we need to
know if
>>    there is more than one. Additional authors can be listed through
EasyChair.
>>
>>
>> Abstract:
>>
>>    - 1-2 paragraphs. Keep in mind that this is displayed on the
schedule
>>    and website for attendees to consider when selecting talks.
>>    - We suggest you proof read and pay attention to grammar.
>>
>>
>> Details:
>>
>>    - Here you can include more details about your talk. An outline,
demo
>>    description, background of the speaker, etc. 1-2 paragraphs is
sufficient
>>    usually.
>>    - This section will not be published and is intended for the PC to
>>    better understand how interesting your talk will be to the audience.
For
>>    example, if you would prefer not to reveal some conclusions in the
>>    published abstract, explaining them here ensures that the PC can
take them
>>    into account when evaluating your proposal.
>>
>>
>>
>> BoF Talk Proposal Template:
>>
>> Title:
>>
>>    - This will be displayed on the website, schedule, and signs. These
>>    tend to be very straight forward about the area being discussed. An
example
>>    is “Future directions and features for LLDB”.
>>    -
>>
>> Speaker Name(s), Company, Email:
>>
>>    - This should be only the speakers leading the discussion. EasyChair
>>    only allows you to select one speaker in its interface and we need
to know
>>    if there is more than one. Additional authors can be listed through
>>    EasyChair.
>>
>>
>> Abstract:
>>
>>    - 1-2 paragraphs. Keep in mind that this is displayed on the
schedule
>>    and website for attendees to consider when selecting which BoFs to
attend.
>>    - Provide some talking points or potential subtopics.
>>    - We suggest you proof read and pay attention to grammar.
>>
>>
>> Details:
>>
>>    - Provide additional details: goals of the BoF, presentation style.
>>    BoFs are to brainstorm ideas on a specific topic but you will be
more
>>    successful if you have a guided discussion with talking points and
>>    actionable items at the end.
>>
>>
>> Tutorial Proposal Template:
>>
>> Title:
>>
>>    - This will be displayed on the website, schedule, and signs. Keep
it
>>    short and catchy to attract attendees to your talks.
>>
>>
>> Speaker Names(s), Company, Email Address:
>>
>>    - Those giving the tutorial. Typically 1-2 speakers.
>>
>>
>> Abstract:
>>
>>    - 1-2 paragraphs. Keep in mind that this is displayed on the
schedule
>>    and website for attendees to consider when selecting talks.
>>    - We suggest you proof read and pay attention to grammar.
>>
>>
>> Details:
>>
>>    - Include additional details such as tutorial outline, what
materials
>>    you will provide attendees, etc.
>>
>>
>> Panel Proposal Template:
>>
>> Title:
>>
>>    - This will be displayed on the website, schedule, and signs. Keep
it
>>    short and catchy to attract attendees to your talks.
>>
>>
>> Moderator Name(s), Company, Email Address:
>>
>>    - The person keeping speakers on track and asking questions.
>>
>>
>> Speaker Names(s), Company, Email Address:
>>
>>    - The people on the panel. Typically 2-3 speakers. More than 3 tends
>>    to be difficult in the time slot.
>>
>>
>> Abstract:
>>
>>    - This should list one paragraph about the panel topic and what will
>>    be discussed. You should also include detailed 2-3 sentence bios for
each
>>    speaker on the panel.
>>
>>
>> Details:
>>
>>    - Include some sample questions for the panel.
>>
>>
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170812/4195e0b8/attachment-0001.html>