llvm dev - Jul 2019 - 2019 LLVM Dev Mtg (Bay Area) - Call for presentations

All developers and users of LLVM and related sub-projects are invited to present
at the 2019 LLVM Developers’ Meeting - Bay Area
<http://llvm.org/devmtg/2019-10/>.

We are looking for the following proposals:
Technical Talks (25-30 minutes including Q&A):
- On LLVM Infrastructure,Clang and all related sub-projects
- On uses of LLVM in academia or industry
- On new projects using Clang or LLVM
Tutorials (60 minutes)
- In depth talks on LLVM infrastructure or other core libraries
Student Research Competition Technical Talks & Poster (20-25 minutes
including Q&A)
Lightning Talks (5 minutes, no questions, no discussions)
Birds of a Feather
<https://en.wikipedia.org/wiki/Birds_of_a_feather_(computing)> (30
minutes)**
Panels (30-60 minutes)**
Posters (1 hour)


** As the LLVM Developers’ Meeting as grown in size, we are moving away from
formal Birds of a Feather sessions in favor of smaller informal round table
discussions. These round table topics can be proposed closer to the LLVM
Developers’ Meeting and are designed for a smaller and more engaged group of
developers. Therefore, we are encouraging and recommending that instead of a
birds of a feather sessions, that developers consider proposing a panel
discussion. This would mean that several experts on a topic (and a moderator)
would get together and have an open discussion in front of an audience with
prepared questions and also questions from the audience. The program committee
will be looking for these proposals and giving favor to them over more
traditional birds of a feather proposals that we have had in the past.

Submission Requirements:
The submission deadline is August 12, 2019 at 11:59PM PDT.

Please submit your proposal here:
LLVM2019 Home <https://hotcrp.llvm.org/usllvm2019/>
For each proposal, please submit a title, short abstract, submission type,
abstract for the website, include who the speakers or panel member/moderators
are, and provide a more detailed description of the talk through an extended PDF
abstract. We highly recommend you consult and follow the guide at the end of
this CFP when submitting your proposal.

Student Research Competition (SRC):
We will again have a Student Research Competition (SRC). 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-25 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 submissions by August 27, 2019.

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
short introductions from each panel member, and follow with an interactive
dialogue among the panelists and audience members. Panels should consist of 3
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 22, 2019.

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 David Blaikie. 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 the LLVM Dev Mtg Organizers (devmtg-organizers at lists.llvm.org),
or the LLVM Developers’ Meeting mailing list.
http://lists.llvm.org/mailman/listinfo/llvm-devmeeting
<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 carefully.

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 (excluding SRC submissions).
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:
** Include in the extended abstract PDF attachment **

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”. There is also a field in the submission form for this same
title.

Description:
1-2 paragraphs. You can also use this for the Website Abstract field in the
submission form.
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 usually sufficient.
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.

SRC Paper:
If this is an SRC talk, please attach your paper as well.

Panel Talk Proposal Template:
** Include in the extended abstract PDF attachment **

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”. There is also a field in the submission form
for this same title.

Description:
1-2 paragraphs. May also be used for the website abstract field in the
submission form.
Provide some talking points or potential subtopics.
We suggest you proof read and pay attention to grammar.

Details:
Provide additional details: goals of the panel, and example questions. Panels
are to brainstorm and discuss ideas on a specific topic between the experts on
the panel and the audience. You should also include detailed 2-3 sentence bios
for each speaker on the panel. You may or may not include speaker names as the
submissions are blind.

Tutorial Proposal Template:
** Include in the extended abstract PDF attachment **

Title:
This will be displayed on the website, schedule, and signs. Keep it short and
catchy to attract attendees to your talks. There is also a field in the
submission form for this same title.

Description:
1-2 paragraphs. May also be used for the website abstract field in the
submission form.
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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190702/a5ab5fb8/attachment.html>

Just a friendly reminder that the deadline is this coming Monday! Please let me
know if you have questions.

Thanks,
Tanya
> On Jul 2, 2019, at 8:49 AM, Tanya Lattner <tanyalattner at llvm.org>
wrote:
> 
> All developers and users of LLVM and related sub-projects are invited to
present at the 2019 LLVM Developers’ Meeting - Bay Area
<http://llvm.org/devmtg/2019-10/>.
> 
> We are looking for the following proposals:
> Technical Talks (25-30 minutes including Q&A):
> - On LLVM Infrastructure,Clang and all related sub-projects
> - On uses of LLVM in academia or industry
> - On new projects using Clang or LLVM
> Tutorials (60 minutes)
> - In depth talks on LLVM infrastructure or other core libraries
> Student Research Competition Technical Talks & Poster (20-25 minutes
including Q&A)
> Lightning Talks (5 minutes, no questions, no discussions)
> Birds of a Feather
<https://en.wikipedia.org/wiki/Birds_of_a_feather_(computing)> (30
minutes)**
> Panels (30-60 minutes)**
> Posters (1 hour)
> 
> 
> ** As the LLVM Developers’ Meeting as grown in size, we are moving away
from formal Birds of a Feather sessions in favor of smaller informal round table
discussions. These round table topics can be proposed closer to the LLVM
Developers’ Meeting and are designed for a smaller and more engaged group of
developers. Therefore, we are encouraging and recommending that instead of a
birds of a feather sessions, that developers consider proposing a panel
discussion. This would mean that several experts on a topic (and a moderator)
would get together and have an open discussion in front of an audience with
prepared questions and also questions from the audience. The program committee
will be looking for these proposals and giving favor to them over more
traditional birds of a feather proposals that we have had in the past.
> 
> Submission Requirements:
> The submission deadline is August 12, 2019 at 11:59PM PDT.
> 
> Please submit your proposal here:
> LLVM2019 Home <https://hotcrp.llvm.org/usllvm2019/>
> For each proposal, please submit a title, short abstract, submission type,
abstract for the website, include who the speakers or panel member/moderators
are, and provide a more detailed description of the talk through an extended PDF
abstract. We highly recommend you consult and follow the guide at the end of
this CFP when submitting your proposal.
> 
> Student Research Competition (SRC):
> We will again have a Student Research Competition (SRC). 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-25 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 submissions by August 27, 2019.
> 
> 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
short introductions from each panel member, and follow with an interactive
dialogue among the panelists and audience members. Panels should consist of 3
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 22, 2019.
> 
> 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 David Blaikie. 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 the LLVM Dev Mtg Organizers (devmtg-organizers at
lists.llvm.org <mailto:devmtg-organizers at lists.llvm.org>), or the LLVM
Developers’ Meeting mailing list.
http://lists.llvm.org/mailman/listinfo/llvm-devmeeting
<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 carefully.
> 
> 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 (excluding SRC submissions).
> 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:
> ** Include in the extended abstract PDF attachment **
> 
> 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”. There is also a field in the submission form for this same
title.
> 
> Description:
> 1-2 paragraphs. You can also use this for the Website Abstract field in the
submission form.
> 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 usually
sufficient.
> 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.
> 
> SRC Paper:
> If this is an SRC talk, please attach your paper as well.
> 
> Panel Talk Proposal Template:
> ** Include in the extended abstract PDF attachment **
> 
> 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”. There is also a field in the submission form
for this same title.
> 
> Description:
> 1-2 paragraphs. May also be used for the website abstract field in the
submission form.
> Provide some talking points or potential subtopics.
> We suggest you proof read and pay attention to grammar.
> 
> Details:
> Provide additional details: goals of the panel, and example questions.
Panels are to brainstorm and discuss ideas on a specific topic between the
experts on the panel and the audience. You should also include detailed 2-3
sentence bios for each speaker on the panel. You may or may not include speaker
names as the submissions are blind.
> 
> Tutorial Proposal Template:
> ** Include in the extended abstract PDF attachment **
> 
> Title:
> This will be displayed on the website, schedule, and signs. Keep it short
and catchy to attract attendees to your talks. There is also a field in the
submission form for this same title.
> 
> Description:
> 1-2 paragraphs. May also be used for the website abstract field in the
submission form.
> 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.
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190809/8b5c435d/attachment-0001.html>