git/list[1] front-page[2] threads[3] people[4] search[5] about
 

GSoC applicants: discuss other applicants patches, perhaps?

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 6, 2015, 07:44 UTC
Message-ID
<CAPc5daV7Dv8K8itmQhdf1CG-opMVw7DYyheHdcdL0r_9zFQR-Q@mail.gmail.com>

The objective of GSoC program is to learn how to work on projects as a part of an open source community, and working in Git project is not only about writing your own patches. Constructively critiquing design and implementation of patches by other people is also an important skill you need to learn in order to effectively collaborate with others.

So, if you have time and inclination, it would be beneficial to read and understand other applicants' patches, think if you agree that the problem they are trying to solve is worth solving, the approach they are taking is the best way (or if you think of a better way to solve it), etc., and respond to their patches with the result of your thinking as a review.

What do mentors and others think?
Next: Matthieu Moy
Message 1 of 5 in “GSoC applicants: discuss other applicants patches, perhaps?”
  1. Junio C HamanoMar 6, 2015
  2. Suggest applicants to participate in review of other peoples' patchesMatthieu Moy, Mar 6, 2015
  3. Jeff KingMar 6, 2015
  4. Junio C HamanoMar 6, 2015
  5. Matthieu MoyMar 8, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.