Re: GSoC 2016: applications open, deadline = Fri, 19/2
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 22, 2016, 21:56 UTC
- Message-ID
- <xmqqlh6c5ryz.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <20160222214246.GE15595@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 6 quoted lines
> I agree that there are a lot of different ways to resolve each instance, > and it will vary from case to case. I think the original point of a > microproject was to do something really easy and not contentious, so > that the student could get familiar with all of the other parts of the > cycle: writing a commit message, formatting the patch, posting to the > list, etc.
I had an impression that Micros are also used as an aptitude test, and one important trait we want to see in a potential developer is how well s/he interacts with others in such a discussion. So "easy and not contentious" might not be a very good criteria.
I dunno.
> It seems like this has a high chance of frustrating students as they get > embroiled in back-and-forth review. I dunno. Maybe it should be marked > with a star as a "challenge" microproject. :)