llvm dev - Sep 2017 - Volunteers for Hackers Lab Needed!

All,

We need volunteers for the Hacker’s Lab at the upcoming 2017 LLVM Developers’
Meeting! The Hacker’s Lab is for small groups to form to discuss topics or work
on problems. Please let me know ASAP if you will able to volunteer so I can add
your topic to the online listing and make appropriate signs.

The Hackers Lab is split into 1.5 hour sessions. During each session, the
Hackers Lab will focus on specific topics. Each table (~15) in the room will
have a sign on it to represent a sub-project or area of LLVM. This will help
newcomers and even active developers congregate together on specific topics.
Many of the tables will have an easel for informal discussions.

In addition to labeling tables, we are asking for volunteers to represent a
sub-project or topic related to the meeting. These volunteers should be
knowledgeable about the sub-project/topic and able to answer some basic
questions or point people to the right developer to talk to. If volunteers want
to go a step further, they could prepare a list of bugs that groups could work
on during the Hackers Lab. This is very open ended in what the leader of the
table can do, but the main goal is to provide a space for developers’ to meet
and find each other who are interested in a specific topic or sub-project.

I’ve gone through many of the Code Owners files to try to find topics, and here
is a list I have started.. but really it depends on who volunteers :)

LLVM
Backends, Code Generation, Register Allocation, Machine Code Layer, ISel
LLDB, Debug Info, DWARF
LTO
Polly
MCJIT
Mid-level optimizations, pass manager, loop optimizations, etc
TableGen
Sanitizers
Windows support
Exception handling
lld

Clang, Libs, & Frontend tools
Clang - parsing, llvm ir generation, etc
Static Analyzer
OpenCL
Clang Tools - clang tidy, clang rename
parallel-libs
Open MP
libC++
llgo

I know this may be a bit confusing.. but it really doesn’t require much work if
you don’t want it to. Ideally, I would love some Code Owners to fill the roles,
but I realize not all will be attending.

Please let me know ASAP if you are interested! In the rare event I have too many
volunteers, we may combine topics at tables.

Thanks,
Tanya
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170924/194142a8/attachment.html>

Hi Tanya,

I volunteer to host a table on Testing and Benchmarking in general, and LNT
and test-suite specifically.

Thanks!

Kristof

2017-09-24 8:24 GMT+00:00 Tanya Lattner via llvm-dev <
llvm-dev at lists.llvm.org>:
> All,
>
> We *need volunteers* for the Hacker’s Lab at the upcoming 2017 LLVM
> Developers’ Meeting! The Hacker’s Lab is for small groups to form to
> discuss topics or work on problems. *Please let me know ASAP if you will
> able to volunteer so I can add your topic to the online listing and make
> appropriate signs.*
>
> The Hackers Lab is split into 1.5 hour sessions. During each session, the
> Hackers Lab will focus on specific topics. Each table (~15) in the room
> will have a sign on it to represent a sub-project or area of LLVM. This
> will help newcomers and even active developers congregate together on
> specific topics. Many of the tables will have an easel for informal
> discussions.
>
> In addition to labeling tables, *we are asking for volunteers to
> represent a sub-project or topic related to the meeting*. These
> volunteers should be knowledgeable about the sub-project/topic and able to
> answer some basic questions or point people to the right developer to talk
> to. If volunteers want to go a step further, they could prepare a list of
> bugs that groups could work on during the Hackers Lab. This is very open
> ended in what the leader of the table can do, but the main goal is to
> provide a space for developers’ to meet and find each other who are
> interested in a specific topic or sub-project.
>
> I’ve gone through many of the Code Owners files to try to find topics, and
> here is a list I have started.. but really it depends on who volunteers :)
>
> LLVM
>
>    1. Backends, Code Generation, Register Allocation, Machine Code Layer,
>    ISel
>    2. LLDB, Debug Info, DWARF
>    3. LTO
>    4. Polly
>    5. MCJIT
>    6. Mid-level optimizations, pass manager, loop optimizations, etc
>    7. TableGen
>    8. Sanitizers
>    9. Windows support
>    10. Exception handling
>    11. lld
>
>
> Clang, Libs, & Frontend tools
>
>    1. Clang - parsing, llvm ir generation, etc
>    2. Static Analyzer
>    3. OpenCL
>    4. Clang Tools - clang tidy, clang rename
>    5. parallel-libs
>    6. Open MP
>    7. libC++
>    8. llgo
>
>
> I know this may be a bit confusing.. but it really doesn’t require much
> work if you don’t want it to. Ideally, I would love some Code Owners to
> fill the roles, but I realize not all will be attending.
>
> *Please let me know ASAP if you are interested! *In the rare event I have
> too many volunteers, we may combine topics at tables.
>
> Thanks,
> Tanya
>
> _______________________________________________
> 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/20171003/c05101aa/attachment.html>