Re: Git and GSoC 2013

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Mar 28, 2013 at 5:45 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote:
> Christian Couder <christian.couder@xxxxxxxxx> writes:
>
>> On Wed, Mar 27, 2013 at 7:52 PM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote:
>>> Jeff King wrote:
>>>
>>>> There was a big thread about a month ago on whether Git should do Google
>>>> Summer of Code this year[1].
>>
>> I think we should do it.
>>
>> It looks strange to me to say that students are great and at the same
>> time that we should not do it.
>>
>> Let's give them and us one more chance do to well. This is the only
>> way we can improve.
>
> Do you mean we should be doing the same thing over and over again
> and expecting different results?  Einstein may not like it, and I
> certainly don't.

No, I don't mean we should be doing the same. I agree that smaller
projects are helpful and insisting on submitting right away on the
mailing list is helpful.
But if we don't even try we have no chance to see if it works. We just
lose time.

> What I gathered from the discussion so far is that everybody agrees
> that our mentoring has been suboptimal in various ways (not enough
> encouragement to engage with the community early, working in the
> cave for too long, biting too much to chew etc.).  What makes you
> think we would do better this year?

The fact that we will be more conscious that we need smaller projects
and that we need to push even more for students to send their patch
soon on the mailing list.

If it doesn't work at all we will be set and we will know that there
is not much we can do to make it work.

If we don't even try we will not know soon, so not be able to improve
or decide to stop.

It's like software or science. If you don't test soon your hypothesis
you don't progress fast.

Or do you think we just stand no chance to progress?

By the way we say that students should post soon to the mailing list
to get a feedback soon, but it looks like we don't want to try our
hypothesis around mentoring as soon as we can.
Doesn't it sound strange to you? Aren't we saying "do as I say not as I do"?

> "We have a track record of being not great at mentoring, and we
> haven't made an effort to improve it." is a perfectly valid and
> humble reason to excuse ourselves from this year's GSoC.

It is also a perfectly valid justification to decide to make an effort
to improve our mentoring and to try again.

> "Students are great" is immaterial.

"We are not great at mentoring" is as much immaterial.

> In fact, if they are great, I think it is better to give them a
> chance to excel by working with organizations that can mentor them
> better, instead of squandering their time and GSoC's money for
> another failure, until _we_ are ready to take great students.

How do we know we are ready if we don't try?

By waiting we just lose the experience we already have, because some
mentors might not be around next year, or they will not remember well
about the process.

And some organizations that will perhaps be accepted, if we decide not
to do it, might have no mentoring experience at all. How do you know
they will mentor students better than what we have been doing?

Best regards,
Christian.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]