[Bf-committers] GSoC 2018 student requirements
Brecht Van Lommel
brechtvanlommel at pandora.be
Sat Feb 17 14:52:36 CET 2018
Hi,
GSoC is also about attracting new developers to Blender (and open source in
general), so I don't think we should have too strict requirements.
In my opinion it's reasonable to say: if you submit a patch for a bugfix or
quick hack (or have already contributed), then that will significantly
increased your chances of being accepted. The FAQ says something like that,
but it could be more clear:
https://wiki.blender.org/index.php/Dev:Ref/GoogleSummerOfCode/Getting_Started#Application_FAQs
I'm not sure we need to require much beyond that, there's still too many
unreviewed patches so requiring to have a reviewed patch is already
problematic.
Regards,
Brecht.
On Sat, Feb 17, 2018 at 2:23 PM, Sybren A. Stüvel <sybren at stuvel.eu> wrote:
> Hey list,
>
> Ton suggested to me at some point that we should only accept GSoC students
> who already have worked on Blender in the past (submitted patches that
> actually got a positive review, or who already are active Blender
> developers). I fully agree that this is a good idea, as GSoC is not about
> teaching students how the innards of Blender work, but to get a concrete
> result that is useful to Blender's users.
>
> Shall we adopt this as official policy? Or have we already and did I
> simply miss it?
>
> Cheers,
>
> Sybren
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>
More information about the Bf-committers
mailing list