Hello! This is an update to let you know that the deadline has been extended to 
September 27th at 5pm PDT.

A couple of additional notes:
- Notification will be on Oct 8th
- Recordings will be happening as early as the first week of November (Nov 
1-5). We are finalizing the details in the next couple weeks on how this will 
work. 

Thanks,
Tanya 

> On Sep 7, 2021, at 10:13 PM, Tanya Lattner <tanyalatt...@llvm.org> wrote:
> 
> All developers and users of LLVM and related sub-projects are invited to 
> present at the 2021 LLVM Developers’ Meeting 
> <https://llvm.org/devmtg/2021-11/>! The conference will be held November 
> 17-19. Due to the uncertainty of COVID-19, the conference will again be 
> online only. Full conference details coming in the next couple weeks. There 
> will be a Q&A session for proposal submission on September 9 at 10am and 10pm 
> PDT. See the website <https://llvm.org/devmtg/2021-11/> for details.
> 
> Submit your talk proposals here (but read on as some things have changed):
> LLVM2021 Submissions <https://hotcrp.llvm.org/usllvm2021/>
> This year, we will have a few changes to the program. First, we are 
> introducing a new technical talk category called “Quick Technical Talks”. 
> These talks are similar to full length technical talks or lightning talks 
> except that the speakers are given only 10 minutes. Additionally, we will no 
> longer have a poster session and encourage those interested to submit a 
> lightning talk instead. The Student Research Competition has been modified to 
> no longer be a competition, but a specific category for student presentations 
> and full length papers are not required. Lastly, you will notice that Birds 
> of a Feather (BoF) sessions have been removed as a category and we will share 
> plans for these types of sessions at a later date. 
> 
> We are looking for the following proposals:
> Technical Talks (20-25 minutes*):
> Talks 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, tools, etc. 
> Demos encouraged.
> Student Technical Talks (15-20 minutes*)
> Talks from students using LLVM, Clang, and all sub-projects in research.
> The audience usually votes on a winner.
> Quick Technical Talks (10 minutes)
>       Quick talks about a use or improvement of LLVM and other sub-projects.
> Lightning Talks (5 minutes)
> Lightning fast talks about a use or improvement of LLVM and other 
> sub-projects.
> Panels (45 minutes)
> 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 at least 3 people and have a moderator.
> 
> * Exact times TBD after talks selected
> 
> Submission Requirements:
> The submission deadline is September 20, 2021 at 5:00PM PDT.
> 
> Please submit your proposal here:
> LLVM2021 Submissions <https://hotcrp.llvm.org/usllvm2021/>
> For each proposal you must submit the following:
> Talk title
> Abstract
> Submission type (Different than last year)
> For technical talk submissions, you can indicate if you would give a shorter 
> talk (ie. Lightning or Quick instead of full length Technical Talk)
> Photo and bios for all speakers (NEW!)
> Short abstract for the website
> Extended PDF abstract (optional)
> 
> We highly recommend you consult and follow the guide below when submitting 
> your proposal.
> 
> Additional details regarding notification and recording timeline will be 
> communicated soon. If you have questions, please contact Tanya Lattner 
> through Discourse, Discord, or email.
> 
> 
> Thanks,
> Tanya Lattner 
> 
> 
> 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.
> 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 Student 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.
> 
> 
> 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.
> 

_______________________________________________
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Reply via email to