[llvm-dev] [GSoC] General Information
Tobias Grosser via llvm-dev
llvm-dev at lists.llvm.org
Tue Apr 26 11:58:15 PDT 2016
On 04/26/2016 08:48 PM, vivek pandya wrote:
> /*Vivek Pandya*/
> On Tue, Apr 26, 2016 at 11:00 AM, Tobias Grosser <tobias at grosser.es
> <mailto:tobias at grosser.es>> wrote:
> Dear LLVM summer of code students,
> let me congratulate you to your successful application!
> After your participation has been announced, its now time to start
> with community bounding as preparation of the actual project start
> on 23 May. To ensure your GSoC becomes a large success, I wrote down
> some general information that has proven important in previous years.
> # GSoC and the LLVM community
> Besides your individual project goals, the primary objective of your
> GSoC project is to establish yourself as a full and active member of
> the LLVM community. It is your job to get in touch with the LLVM
> community and to develop your project as part of the LLVM community.
> This means you are invited to discuss your ideas with the LLVM
> community, to submit your patches for public code review, and also
> to participate as code-reviewer for patches that fall in your area
> of expertise and match your level of knowledge. To ensure maximal
> community involvement, LLVM has a well established tradition of
> incremental development and you should follow this practice in your
> GSoC project.
> # The role of the mentor
> You have been paired with one (or two) personal mentors, who will
> support you throughout your summer of code project. Your mentor is
> your first point of contact in case of any questions regarding your
> GSoC project. His primary role is to ensure you are successfully
> integrated with the LLVM community by ensuring you understand how to
> discuss project ideas, how to obtain code reviews, and generally to
> help you to understand the informal best practices in the LLVM
> community. In many cases he will also provide reviews for your
> patches, but please keep in mind that he is not your proxy to the
> LLVM community, but you are expected to directly interact with the
> whole community. In the optimal case, you learn quickly how to
> obtain patch reviews yourself and how to discuss your ideas with the
> full LLVM community. Your mentor will likely also give feedback, but
> he is just one out of the many people in the community you will be
> working with.
> Your mentor also evaluates your project and can change project
> milestone if this should become necessary. However, we again suggest
> to discuss changes to your agenda in public.
> # Media of communication
> This email is on-purpose sent to you through the
> LLVM/cfe/safecode/Polly mailing lists. Mailing lists are the primary
> medium of communication for LLVM. Other means such as IRC, phone or
> personal meetings can complement email, but please ensure that all
> important discussions either take part via the mailing lists or are
> mirrored to the mailing lists by posting meeting reports or updates.
> # Reporting / Status updates
> To keep people informed about your work, we suggest each student to
> implement regular reporting habits. As email is our primary medium
> of communication, brief weekly status emails can be a nice way to
> get your information out. If you send them before the week-end,
> chances are
> that some of your news show up in LLVM weekly.
> Previous students also often set up a GSoC blog to irregularly post
> larger status updates, performance results, architecture diagrams, ...
> # GSoC administrative issues
> Please use the public mailing lists for all (non-sensitive)
> administrative issues. You are likely not the only one who has
> similar questions/concerns. Having your questions (and the
> solutions) being
> archived and available in search engines will save us time and be of
> great help for all other students.
> # Introducing yourself
> To kick off your personal GSoC of code, we suggest to introduce
> yourself and your project on the relevant mailing list, invite people
> to provide feedback to your project, and communicate your planned
> timeline as well as the media/location and interval you will use to
> report your status.
> # Project description on llvm.org <http://llvm.org>
> We can have a simple Google form for this task, students will fill
> relevant details and then responses will be added to a simple html file
> (llvm.org <http://llvm.org> 's format). I would be happy to help for
> this task.
I created an -- almost empty -- skeleton for this information (that is
not yet linked to from the LLVM website):
It would be great if people could self-organize to improve this. If you
want to take the lead here, this is definitely great.
More information about the llvm-dev