[Bf-committers] a note for students who have submitted a gsoc proposal

[Sean Olson]

I think the purpose of this requirement is to prove that you are capable of
working with blenders source and can hit the ground running.  I think that
makes you covered Jason since you have participated in previous gsocs for
Blender and already have code committed to trunk- correct me if I'm wrong
Tom.

-Sean
On Apr 8, 2012 8:31 PM, "Jason Wilkins" <jason.a.wilkins at gmail.com> wrote:

> I was probably going to submit a couple of patches tonight anyway.
> Does this mean I need to go ahead an link those into my proposal?
>
> On Sun, Apr 8, 2012 at 4:04 PM, Tom M <letterrip at gmail.com> wrote:
> > Students,
> >
> > if you have submitted a gsoc proposal, part of the qualification
> > process is that you should also submit a patch to our patch tracker
> > (and a link to the patch in either your proposal or in the proposal
> > comments).  Preferably the patch should be for the area of code that
> > you want to work on (ie fluids work would provide a fluids patch,
> > rendering work a rendering patch, modeling work a modeling patch, ui
> > work a ui patch, etc.)
> >
> > Note that if you have already had a patch committed, then that will
> > count as a qualification.
> >
> > So if you haven't done such a patch already, please do a patch and add
> > a link to it in the comments on your proposal.
> >
> > Email me if there are any questions or difficulties.
> >
> > LetterRip
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>