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

Re: Starting on a microproject for GSoC

From
Andrew Ardill <andrew.ardill@gmail.com>
Date
Jan 28, 2016, 06:17 UTC
Message-ID
<CAH5451=u1MB=LJyBv+Z9e4Y5ncHktMw+oEycOWV1YXASaawMDA@mail.gmail.com>
In-Reply-To
<56A96380.3020308@moritzneeb.de>
On 28 January 2016 at 11:40, Moritz Neeb <lists@moritzneeb.de> wrote:
> I suppose just fixing/revising this would be kind
> of a too low hanging fruit?

I am in no way qualified to speak to the majority of your post, but I can't imagine anyone refusing your work because it was 'too low hanging fruit'.

Indeed, the general gist of getting people to start with a microproject has always appeared to help potential applicants understand what it takes to get a patch accepted in git. As long as the low hanging fruit is useful (your example of polishing a patchset to get it into master is definitely useful, assuming the patchset is useful) then I'd say go for it.

In the worst case, if you feel your contribution was not 'meaty' enough, there is nothing to stop you working on some other problem, or extending the first further. That said, I do remember previous applicants trying to do as many microprojects as possible, leaving few for other people.

Regards,
Andrew Ardill
Previous: Moritz NeebNext: Johannes Schindelin
Message 4 of 7 in “Starting on a microproject for GSoC”
  1. Moritz NeebJan 28, 2016
  2. Stefan BellerJan 28, 2016
  3. Moritz NeebJan 28, 2016
  4. Andrew ArdillJan 28, 2016
  5. Johannes SchindelinJan 28, 2016
  6. Lars SchneiderJan 28, 2016
  7. Junio C HamanoJan 28, 2016

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.