<div dir="ltr">unsubscribe</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 2, 2020 at 1:15 AM via llvm-devmeeting <<a href="mailto:llvm-devmeeting@lists.llvm.org">llvm-devmeeting@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send llvm-devmeeting mailing list submissions to<br>
<a href="mailto:llvm-devmeeting@lists.llvm.org" target="_blank">llvm-devmeeting@lists.llvm.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-devmeeting" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-devmeeting</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:llvm-devmeeting-request@lists.llvm.org" target="_blank">llvm-devmeeting-request@lists.llvm.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:llvm-devmeeting-owner@lists.llvm.org" target="_blank">llvm-devmeeting-owner@lists.llvm.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of llvm-devmeeting digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Reminder: Deadline 11th of January - EuroLLVM 2020 - Call for<br>
presentations (Kristof Beyls via llvm-devmeeting)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 2 Jan 2020 10:14:02 +0100<br>
From: Kristof Beyls via llvm-devmeeting<br>
<<a href="mailto:llvm-devmeeting@lists.llvm.org" target="_blank">llvm-devmeeting@lists.llvm.org</a>><br>
To: llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>>, Clang Dev<br>
<<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>>, <a href="mailto:clangd-dev@lists.llvm.org" target="_blank">clangd-dev@lists.llvm.org</a>,<br>
<a href="mailto:flang-dev@lists.llvm.org" target="_blank">flang-dev@lists.llvm.org</a>, <a href="mailto:libc-dev@lists.llvm.org" target="_blank">libc-dev@lists.llvm.org</a>,<br>
<a href="mailto:libclc-dev@lists.llvm.org" target="_blank">libclc-dev@lists.llvm.org</a>, <a href="mailto:libcxx-dev@lists.llvm.org" target="_blank">libcxx-dev@lists.llvm.org</a>,<br>
<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a>, <a href="mailto:llvm-devmeeting@lists.llvm.org" target="_blank">llvm-devmeeting@lists.llvm.org</a>,<br>
<a href="mailto:openmp-dev@lists.llvm.org" target="_blank">openmp-dev@lists.llvm.org</a>, <a href="mailto:parallel_libs-dev@lists.llvm.org" target="_blank">parallel_libs-dev@lists.llvm.org</a><br>
Subject: [llvm-devmeeting] Reminder: Deadline 11th of January -<br>
EuroLLVM 2020 - Call for presentations<br>
Message-ID:<br>
<CAEVefYXer=RZ5Dr9O4Ch6F=<a href="mailto:MbWy-Vyv4u44baj--rxRE085iOA@mail.gmail.com" target="_blank">MbWy-Vyv4u44baj--rxRE085iOA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
This is just a gentle reminder that the deadline for submitting proposals<br>
is Saturday 11th of January, in about 9 days.<br>
<br>
Op vr 22 nov. 2019 om 15:52 schreef Kristof Beyls <<a href="mailto:kristof.beyls@gmail.com" target="_blank">kristof.beyls@gmail.com</a>>:<br>
<br>
> All developers and users of LLVM and related sub-projects are invited to<br>
> present and discuss at the EuroLLVM'20 <<a href="http://llvm.org/devmtg/2020-04/" rel="noreferrer" target="_blank">http://llvm.org/devmtg/2020-04/</a>><br>
> developers’ meeting in Paris, France.<br>
><br>
> We are looking for the following proposals:<br>
><br>
> 1.<br>
><br>
> Technical Talks (25 minutes + 5 minutes Q&A):<br>
> -<br>
><br>
> On any llvm project such as the core libraries, clang, mlir, flang,<br>
> etc.<br>
> -<br>
><br>
> On uses of LLVM in academia or industry<br>
> -<br>
><br>
> On new projects using Clang or LLVM<br>
> -<br>
><br>
> On any other LLVM-related topic of interest to participants.<br>
> 2.<br>
><br>
> Tutorials (60 minutes): in depth talks focussed on helping less<br>
> experienced people get up to speed on an aspect of the LLVM project, with<br>
> in depth examples and explanations.<br>
> 3.<br>
><br>
> Student Research Competition Technical Talks & Poster (25 minutes + 5<br>
> minutes Q&A) : The SRC offers students doing LLVM related research a<br>
> non-academic platform to announce and advertise their work as well as to<br>
> discuss it with other researchers, developers and users of LLVM. Students<br>
> are strongly encouraged to present a poster as well, as this will enable<br>
> wider discussions with the audience. An embargo period to delay the<br>
> publication of the abstract/talk/poster is possible. There will be a prize<br>
> for the best SRC entry.<br>
> 4.<br>
><br>
> Lightning Talks (5 minutes, no questions, no discussions)<br>
> 5.<br>
><br>
> Panels / round tables (30-60 minutes) / Birds of a Feather<br>
> <<a href="https://en.wikipedia.org/wiki/Birds_of_a_feather_(computing)" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/Birds_of_a_feather_(computing)</a>> (BoF)<br>
> (30 minutes)<br>
><br>
> These are all discussion formats. The best format is probably mostly<br>
> dependent on the number of expected participants. For small group<br>
> highly-engaged discussion, round tables are expected to work best. Round<br>
> table topics can be proposed closer to the EuroLLVM meeting.<br>
> For discussions that are expected to attract larger groups, either a BoF<br>
> or Panel format is expected to work better. A BoF session is run in a<br>
> presentation-like setup, and therefore is expected to have somewhat less<br>
> free-flowing discussion than a round table.<br>
><br>
> We encourage proposals for a panel format where several experts (and a<br>
> moderator) on a topic get together and have an open discussion in front of<br>
> an audience with prepared questions and also questions from the audience.<br>
> The program committee will be looking for panel proposals and giving favor<br>
> to them over more traditional BoF proposals.<br>
><br>
> 1.<br>
><br>
> Posters (1 hour)<br>
><br>
><br>
><br>
> Submission Requirements:<br>
><br>
> The submission deadline is January 11, 2020 at 11:59PM AoE (Anywhere on<br>
> Earth).<br>
><br>
> Please submit your proposal to the EuroLLVM'20 submission site<br>
> <<a href="https://hotcrp.llvm.org/eurollvm2020/" rel="noreferrer" target="_blank">https://hotcrp.llvm.org/eurollvm2020/</a>><br>
><br>
> For each proposal, please submit a title, short abstract, submission type,<br>
> abstract for the website, and include who the speakers or panel<br>
> member/moderators are. If you wish, you can provide a more detailed<br>
> description of the talk through an extended PDF abstract. We highly<br>
> recommend you consult and follow the guide at the end of this CFP when<br>
> submitting your proposal.<br>
><br>
> FAQ<br>
><br>
> When will I be notified of acceptance?<br>
><br>
> Our goal is to notify all submissions by January 24th, 2020.<br>
><br>
> What are panels?<br>
><br>
> Panels may discuss any topic as long as it’s relevant to LLVM or related<br>
> sub-projects. Panels can take many forms, but a common format is to begin<br>
> with short introductions from each panel member, and follow with an<br>
> interactive dialogue among the panelists and audience members. Panels<br>
> should consist of 3 to 6 people including a moderator.<br>
><br>
> Should I register if I have submitted a proposal?<br>
><br>
> We have 1 complimentary reserved registration for each accepted technical<br>
> talk, BoF, or student research competition talk. Accepted tutorials have<br>
> been reserved 2 complimentary registrations. Panels have up to 3 reserved<br>
> registrations. There are no reserved registration spots for posters or<br>
> lightning talks. So please register any additional speakers or if you do<br>
> not have a reserved registration slot.<br>
><br>
> What if I registered and my talk got accepted?<br>
><br>
> We can refund your registration fee and instructions will be sent<br>
> following notification. If you plan to attend even if your proposal is not<br>
> accepted and are worried about the event selling out, we suggest<br>
> registering before notification of acceptance.<br>
><br>
> What if I registered and my talk DID NOT get accepted?<br>
><br>
> We can refund your registration fee if you no longer wish to attend if you<br>
> contact the organizers by March 6th, 2020.<br>
><br>
> What will be recorded?<br>
><br>
> All technical talks, tutorials, SRC talks, panels, and lightning talks<br>
> will be recorded and published. By submitting your proposal, you are giving<br>
> us permission to record and publish if you present at the meeting. For SRC<br>
> talks, you have the option to delay publication of the slides and video for<br>
> you talk for up to 12 months.<br>
><br>
> Who is on the program committee?<br>
><br>
> Our program committee chair is Kristof Beyls. The program committee is<br>
> composed of active developers of the LLVM, Clang, and related<br>
> sub-communities. The website will be updated with the list of the program<br>
> committee members.<br>
><br>
> I have a question, who do I contact?<br>
><br>
> Please email the LLVM Dev Mtg Organizers (<br>
> <a href="mailto:eurollvm-organizers@lists.llvm.org" target="_blank">eurollvm-organizers@lists.llvm.org</a>), or the LLVM Developers’ Meeting<br>
> mailing list. <a href="http://lists.llvm.org/mailman/listinfo/llvm-devmeeting" rel="noreferrer" target="_blank">http://lists.llvm.org/mailman/listinfo/llvm-devmeeting</a><br>
><br>
><br>
> Detailed guidance on writing a proposal for the LLVM Developers’ Meeting<br>
><br>
> Writing a proposal for the LLVM Developers’ Meeting<br>
><br>
> This document is a guide to help you submit the best proposal and increase<br>
> your chances of your proposal being accepted. The LLVM Developers’ Meeting<br>
> program committee receives more proposals than can be accepted, so please<br>
> read this guide carefully.<br>
><br>
> If you have never presented at an LLVM Developers’ Meeting, then do not<br>
> fear this process. We are actively looking for new speakers who are excited<br>
> about LLVM and helping grow the community through these educational talks!<br>
> You do not need to be a long time developer to submit a proposal.<br>
><br>
> General Guidelines:<br>
><br>
> -<br>
><br>
> It should be clear from your abstract what your topic is, who your<br>
> targeted audience is, and what are the takeaways for attendees. The program<br>
> committee gets a lot of proposals and does not have time to read 10 page<br>
> papers for each submission (excluding SRC submissions).<br>
> -<br>
><br>
> Talks about a use of LLVM (etc) should include details about how LLVM<br>
> is used and not only be about the resulting application.<br>
> -<br>
><br>
> Tutorials on “how to use X” in LLVM (or other subproject) are greatly<br>
> desired and beneficial to many developers. Entry level topics are<br>
> encouraged as well.<br>
> -<br>
><br>
> Talks that have been presented at other technical conferences are less<br>
> likely to get accepted. If you have presented this topic before, make it<br>
> clear what is new and different in your talk.<br>
><br>
><br>
><br>
> Technical Talk and SRC Talk Proposal Template:<br>
><br>
> Title:<br>
><br>
> -<br>
><br>
> This will be displayed on the website, schedule, and signs. Keep it<br>
> short and catchy to attract attendees to your talks. A couple of examples<br>
> are “WebAssembly: Here Be Dragons” or “Beyond Sanitizers: guided fuzzing<br>
> and security hardening”. There is also a field in the submission form for<br>
> this same title.<br>
><br>
><br>
> Description:<br>
><br>
> -<br>
><br>
> 1-2 paragraphs. You can also use this for the Website Abstract field<br>
> in the submission form.<br>
> -<br>
><br>
> We suggest you proofread and pay attention to grammar.<br>
><br>
><br>
> Details:<br>
><br>
> -<br>
><br>
> Here you can include more details about your talk. An outline, demo<br>
> description, background of the speaker, etc. 1-2 paragraphs are usually<br>
> sufficient.<br>
> -<br>
><br>
> This section will not be published and is intended for the PC to<br>
> better understand how interesting your talk will be to the audience. For<br>
> example, if you would prefer not to reveal some conclusions in the<br>
> published abstract, explaining them here ensures that the PC can take them<br>
> into account when evaluating your proposal.<br>
><br>
><br>
> SRC Paper:<br>
><br>
> -<br>
><br>
> If this is an SRC talk, please attach your paper as well.<br>
><br>
><br>
> Panel Talk Proposal Template:<br>
><br>
> Title:<br>
><br>
> -<br>
><br>
> This will be displayed on the website, schedule, and signs. These tend<br>
> to be very straight forward about the area being discussed. An example is<br>
> “Future directions and features for LLDB”. There is also a field in the<br>
> submission form for this same title.<br>
><br>
><br>
> Description:<br>
><br>
> -<br>
><br>
> 1-2 paragraphs. May also be used for the website abstract field in the<br>
> submission form.<br>
> -<br>
><br>
> Provide some talking points or potential subtopics.<br>
> -<br>
><br>
> We suggest you proofread and pay attention to grammar.<br>
><br>
><br>
> Details:<br>
><br>
> -<br>
><br>
> Provide additional details: goals of the panel, and example questions.<br>
> Panels are to brainstorm and discuss ideas on a specific topic between the<br>
> experts on the panel and the audience. You should also include detailed 2-3<br>
> sentence bios for each speaker on the panel. You may or may not include<br>
> speaker names as the submissions are blind.<br>
><br>
><br>
> BoF Proposal Template:<br>
><br>
> Title:<br>
><br>
> -<br>
><br>
> This will be displayed on the website, schedule, and signs. These tend<br>
> to be very straight forward about the area being discussed. An example is<br>
> “LLVM Numerics improvements”. There is also a field in the submission form<br>
> for this same title.<br>
><br>
><br>
> Description:<br>
><br>
> -<br>
><br>
> 1-2 paragraphs. May also be used for the website abstract field in the<br>
> submission form.<br>
> -<br>
><br>
> Provide some talking points or potential subtopics.<br>
> -<br>
><br>
> We suggest you proofread and pay attention to grammar.<br>
><br>
><br>
> Details:<br>
><br>
> -<br>
><br>
> Provide additional details: goals of the BoF. An outline of sub-topics<br>
> you wish to present and questions you’d like to raise for debate.<br>
><br>
><br>
><br>
> Tutorial Proposal Template:<br>
><br>
> Title:<br>
><br>
> -<br>
><br>
> This will be displayed on the website, schedule, and signs. Keep it<br>
> short and catchy to attract attendees to your talks. There is also a field<br>
> in the submission form for this same title.<br>
><br>
><br>
> Description:<br>
><br>
> -<br>
><br>
> 1-2 paragraphs. May also be used for the website abstract field in the<br>
> submission form.<br>
> -<br>
><br>
> We suggest you proofread and pay attention to grammar.<br>
><br>
><br>
> Details:<br>
><br>
> -<br>
><br>
> Include additional details such as tutorial outline, what materials<br>
> you will provide attendees, etc.<br>
> -<br>
><br>
> Please consider the advice at<br>
> <a href="https://www.youtube.com/watch?v=F_q50Th1t3A" rel="noreferrer" target="_blank">https://www.youtube.com/watch?v=F_q50Th1t3A</a> when proposing and/or<br>
> designing your tutorial.<br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.llvm.org/pipermail/llvm-devmeeting/attachments/20200102/8d960427/attachment.html" rel="noreferrer" target="_blank">http://lists.llvm.org/pipermail/llvm-devmeeting/attachments/20200102/8d960427/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
llvm-devmeeting mailing list<br>
<a href="mailto:llvm-devmeeting@lists.llvm.org" target="_blank">llvm-devmeeting@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-devmeeting" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-devmeeting</a><br>
<br>
<br>
------------------------------<br>
<br>
End of llvm-devmeeting Digest, Vol 65, Issue 1<br>
**********************************************<br>
</blockquote></div>