[Bf-committers] GSoC-2017

[Jacob Merrill]

checkout rightclickselect.com and then investigate what these features
would take.

in general game logic will need a bunch of work.
(but is a bit of a tangle)(bricks ui to cycles nodes for example)

pbvhtree was added in a previous gsoc and someone should in theory be able
to accelerate a bunch of tools including new ones like painting vertex
color and sculpting in 1 stroke. (think leave a zipper or weld in 1 stroke
on a high poly sculpt(on multiple channels))

I would love to have the ability to keyframe uv cords (for sprites etc)
for use in the game engine* but I think a texture action would be usefull
even to cycles users etc.

The 2.8 project will also undoubtedly have sections that need work, so I
would get on the viewport mail list, and also look into openGL/ glsl, and
vulkan etc. (if you plan on working with the graphics pipeline)
shadertoy.com is cool for this.

On Dec 1, 2016 4:10 PM, "Sebastián Barschkis" <sebbas at sebbas.org> wrote:

> Dear Varun,
>
> Yes, with strong Python and C skills you should be able to navigate the
> code base.
> In addition to that, I think it would also be helpful to know the basics of
> computer graphics. Especially in the area that you would like to work in.
>
> To get started with Blender, I'd suggest you do the following:
>
> 1. Build Blender from source.
> 2. Check out this years GSoC ideas page:
>     https://wiki.blender.org/index.php/Dev:Ref/
> GoogleSummerOfCode/2016/Ideas
> 3. Identify some areas that you like and where you could see yourself
> working in.
> 4. Visit the Blender developers IRC channel (#blendercoders) and ask about
> your
>     area of choice. Figure out current issues and who is working in that
> area.
>
> Someone will probably tell you where in the code its best to start. Try to
> understand that code (don't worry if it takes some time), make some
> changes and
> play around :)
>
> From there, it's basically a process of "lather, rinse, repeat". That is:
> come
> back to IRC, ask something, try it out in the code, repeat.
> If your changes turn out to be useful you can bundle them and submit a
> patch.
> And boom - your on your way to GSoC'17 :)
>
> Hope this helps, feel free to ask if you get stuck!
>
> Best wishes,
> Sebastián
>
> P.S.: It might also be a good idea to ask some of the previous GSoC
> students
> about their experience. Some, including me, are still on IRC regularly.
>
> > On Dec 1, 2016, at 8:29 PM, Varun Garg <varun.garg03 at gmail.com> wrote:
> >
> > Dear Developers,
> >
> > I am interested in applying for Google Summer of Code'17. I have a pretty
> > strong base in Python and C . Would I be needing anything else to
> > contribute to Blender Foundation? From where should I start?
> >
> > Regards
> > Varun Garg
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > https://lists.blender.org/mailman/listinfo/bf-committers
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>