[llvm-devmeeting] llvm-devmeeting Digest, Vol 65, Issue 1
Sreekumar Kodakara via llvm-devmeeting
llvm-devmeeting at lists.llvm.org
Thu Jan 2 09:14:32 PST 2020
unsubscribe
On Thu, Jan 2, 2020 at 1:15 AM via llvm-devmeeting <
llvm-devmeeting at lists.llvm.org> wrote:
> Send llvm-devmeeting mailing list submissions to
> llvm-devmeeting at lists.llvm.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-devmeeting
> or, via email, send a message with subject or body 'help' to
> llvm-devmeeting-request at lists.llvm.org
>
> You can reach the person managing the list at
> llvm-devmeeting-owner at lists.llvm.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of llvm-devmeeting digest..."
>
>
> Today's Topics:
>
> 1. Reminder: Deadline 11th of January - EuroLLVM 2020 - Call for
> presentations (Kristof Beyls via llvm-devmeeting)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 2 Jan 2020 10:14:02 +0100
> From: Kristof Beyls via llvm-devmeeting
> <llvm-devmeeting at lists.llvm.org>
> To: llvm-dev <llvm-dev at lists.llvm.org>, Clang Dev
> <cfe-dev at lists.llvm.org>, clangd-dev at lists.llvm.org,
> flang-dev at lists.llvm.org, libc-dev at lists.llvm.org,
> libclc-dev at lists.llvm.org, libcxx-dev at lists.llvm.org,
> lldb-dev at lists.llvm.org, llvm-devmeeting at lists.llvm.org,
> openmp-dev at lists.llvm.org, parallel_libs-dev at lists.llvm.org
> Subject: [llvm-devmeeting] Reminder: Deadline 11th of January -
> EuroLLVM 2020 - Call for presentations
> Message-ID:
> <CAEVefYXer=RZ5Dr9O4Ch6F=
> MbWy-Vyv4u44baj--rxRE085iOA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> This is just a gentle reminder that the deadline for submitting proposals
> is Saturday 11th of January, in about 9 days.
>
> Op vr 22 nov. 2019 om 15:52 schreef Kristof Beyls <kristof.beyls at gmail.com
> >:
>
> > All developers and users of LLVM and related sub-projects are invited to
> > present and discuss at the EuroLLVM'20 <http://llvm.org/devmtg/2020-04/>
> > developers’ meeting in Paris, France.
> >
> > We are looking for the following proposals:
> >
> > 1.
> >
> > Technical Talks (25 minutes + 5 minutes Q&A):
> > -
> >
> > On any llvm project such as the core libraries, clang, mlir, flang,
> > etc.
> > -
> >
> > On uses of LLVM in academia or industry
> > -
> >
> > On new projects using Clang or LLVM
> > -
> >
> > On any other LLVM-related topic of interest to participants.
> > 2.
> >
> > Tutorials (60 minutes): in depth talks focussed on helping less
> > experienced people get up to speed on an aspect of the LLVM project,
> with
> > in depth examples and explanations.
> > 3.
> >
> > Student Research Competition Technical Talks & Poster (25 minutes + 5
> > minutes Q&A) : 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 strongly encouraged to present a poster as well, as this will
> enable
> > wider discussions with the audience. An embargo period to delay the
> > publication of the abstract/talk/poster is possible. There will be a
> prize
> > for the best SRC entry.
> > 4.
> >
> > Lightning Talks (5 minutes, no questions, no discussions)
> > 5.
> >
> > Panels / round tables (30-60 minutes) / Birds of a Feather
> > <https://en.wikipedia.org/wiki/Birds_of_a_feather_(computing)> (BoF)
> > (30 minutes)
> >
> > These are all discussion formats. The best format is probably mostly
> > dependent on the number of expected participants. For small group
> > highly-engaged discussion, round tables are expected to work best. Round
> > table topics can be proposed closer to the EuroLLVM meeting.
> > For discussions that are expected to attract larger groups, either a BoF
> > or Panel format is expected to work better. A BoF session is run in a
> > presentation-like setup, and therefore is expected to have somewhat less
> > free-flowing discussion than a round table.
> >
> > We encourage proposals for a panel format where several experts (and a
> > moderator) on a topic 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 panel proposals and giving
> favor
> > to them over more traditional BoF proposals.
> >
> > 1.
> >
> > Posters (1 hour)
> >
> >
> >
> > Submission Requirements:
> >
> > The submission deadline is January 11, 2020 at 11:59PM AoE (Anywhere on
> > Earth).
> >
> > Please submit your proposal to the EuroLLVM'20 submission site
> > <https://hotcrp.llvm.org/eurollvm2020/>
> >
> > For each proposal, please submit a title, short abstract, submission
> type,
> > abstract for the website, and include who the speakers or panel
> > member/moderators are. If you wish, you can 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.
> >
> > FAQ
> >
> > When will I be notified of acceptance?
> >
> > Our goal is to notify all submissions by January 24th, 2020.
> >
> > 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 to 6 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 organizers by March 6th, 2020.
> >
> > What will be recorded?
> >
> > All technical talks, tutorials, SRC talks, panels, and lightning talks
> > will be recorded and published. By submitting your proposal, you are
> giving
> > us permission to record and publish 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 the LLVM Dev Mtg Organizers (
> > eurollvm-organizers at lists.llvm.org), 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 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 are less
> > likely to 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”. 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 proofread 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 are
> 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:
> >
> > 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 proofread 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.
> >
> >
> > BoF 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
> > “LLVM Numerics improvements”. 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 proofread and pay attention to grammar.
> >
> >
> > Details:
> >
> > -
> >
> > Provide additional details: goals of the BoF. An outline of sub-topics
> > you wish to present and questions you’d like to raise for debate.
> >
> >
> >
> > 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. 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 proofread and pay attention to grammar.
> >
> >
> > Details:
> >
> > -
> >
> > Include additional details such as tutorial outline, what materials
> > you will provide attendees, etc.
> > -
> >
> > Please consider the advice at
> > https://www.youtube.com/watch?v=F_q50Th1t3A when proposing and/or
> > designing your tutorial.
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.llvm.org/pipermail/llvm-devmeeting/attachments/20200102/8d960427/attachment.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> llvm-devmeeting mailing list
> llvm-devmeeting at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-devmeeting
>
>
> ------------------------------
>
> End of llvm-devmeeting Digest, Vol 65, Issue 1
> **********************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-devmeeting/attachments/20200102/0f1ff647/attachment-0001.html>
More information about the llvm-devmeeting
mailing list