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

Re: Re* [PATCH v4] MyFirstContribution: refrain from self-iterating too much

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 31, 2023, 15:25 UTC
Message-ID
<xmqqr0oo14tc.fsf@gitster.g>
In-Reply-To
<ivxtqzb46kp5uz5luuxkow6fjzwqrnvxu6f7mgu5a4mnatt6hc@djeykymbumn6>
Jacob Abel <jacobabel@nullpo.dev> writes:
> Maybe something along the lines of "wait 24 hours after any discussion
> regarding the current revision has settled before publishing the next
> revision" would be a good guideline even if it's not included in this 
> patch?
Perhaps.

Usually after an iteration or two of a topic, it will become clear who are available and interested in the topic, and "Wait and give them enough time to respond to what you write" would become the most appropriate guideline at that point.

But for new contributors and for more experienced ones alike, the interest level from others is much harder to assess for the first iteration, until everybody on the list has chance to notice and get interested in the topic. So "wait at least for 24 hours after posting the first iteration" would be a good guideline for those who do not know who on the list are the likely candidates to be interested and know how quick their responses usually have historically been.

A mistake I have often seen by new folks is to send their v2 soon after they get a single minor response to their v1, without saying why they are sending v2 at the time (e.g. "I am only fixing the typo that was pointed out"). It takes much shorter time to come up with a response to point out a typo or two in the proposed log message than giving a deeper analysis, which may only come after a few iterations of such trivial changes.

Previous: Jacob AbelNext: Linus Arver
Message 15 of 20 in “MyFirstContribution: refrain from self-iterating too much”
  1. MyFirstContribution: refrain from self-iterating too muchJunio C Hamano, Jan 22, 2023
  2. Torsten BögershausenJan 22, 2023
  3. Junio C HamanoJan 22, 2023
  4. Junio C HamanoJan 22, 2023
  5. MyFirstContribution: refrain from self-iterating too muchJunio C Hamano, Jan 23, 2023
  6. Torsten BögershausenJan 23, 2023
  7. MyFirstContribution: refrain from self-iterating too muchJunio C Hamano, Jul 19, 2023
  8. Linus ArverJul 27, 2023
  9. Junio C HamanoJul 28, 2023
  10. MyFirstContribution: refrain from self-iterating too muchJunio C Hamano, Jul 28, 2023
  11. Jacob AbelJul 28, 2023
  12. Junio C HamanoJul 28, 2023
  13. Re* [PATCH v4] MyFirstContribution: refrain from self-iterating too muchJunio C Hamano, Jul 28, 2023
  14. Jacob AbelJul 29, 2023
  15. Junio C HamanoJul 31, 2023
  16. Linus ArverJul 28, 2023
  17. Junio C HamanoJul 28, 2023
  18. Torsten BögershausenJul 28, 2023
  19. Junio C HamanoJul 28, 2023
  20. Sean AllredJan 23, 2023

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.