[scribus-dev] to gsoc or not to gsoc?

Craig Bradney cbradney at scribus.info
Tue Mar 19 16:16:02 UTC 2013





On 19/03/2013, at 16:19, Gregory Pittman <gpittman at iglou.com> wrote:

> On 03/19/2013 08:37 AM, JLuc wrote:
>> There is a wider list of ideas for GSOC13
>> http://wiki.scribus.net/canvas/GSoC_2013_Ideas
>> 
>> Some projects probably dont require as much mentor involvment
>> in case the student is serious and competent enough.
>> 
>> I'm quite sure a serious and competent student can do a lot of good
>> and get results that can be merged, even without requiring too much
>> help, code and availability from the mentor.
>> 
>> And as far as my 2012 experience is worth,  and looking at
>> how it happened with the various students, succeeding or not,
>> it is quite possible to know right at the begining (and before engaging)
>> wether a student is serious and has chance to succeed or not.
>> 
>> So maybe the answer should be YES : lets propose a couple of subjects,
>> BUT with the following appropriate decision :
>> - make sure we engage only with students we have a strong faith in.
>> (if none convince us, lets just say when required "we dont engage")
>> - make sure the devs of the students are thoroughfully tested
>> in real time, so they can be merged immediatly.
> 
> I'm a little concerned with this approach, even though it may have some
> merits.
> Are we going to ask potential students to make an application, then
> maybe we withdraw our support because we have no confidence in them?
> Are we going to potentially get an approval from GSoC, only to turn it
> down later because we have no confidence in the student?
> 
> Either of these sets us up to be a potentially undependable project. Why
> would students show interest in us? Why would GSoC show interest in us?
> 
> 

The team is not participating this year due to other commitments unless someone like JLuc steps up to mentor.

Craig


More information about the scribus-dev mailing list