Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Yopa Nelly <yopatatchou@gmail.com>,
	 git@vger.kernel.org, tangajoris@gmail.com,
	 kaartic.sivaraam@gmail.com
Subject: Re: [Outreachy][PATCH v2] promisor-remote: honor promisor.fetchOrder when trying remotes
Date: Fri, 13 Nov 2026 11:58:37 -0800	[thread overview]
Message-ID: <xmqqy0awa4gi.fsf@gitster.g> (raw)
In-Reply-To: <CAP8UFD0zMp-e3Fp5SjXuHiu25718=vf+qetzwpRZmBPMJ8Vb0Q@mail.gmail.com> (Christian Couder's message of "Fri, 13 Nov 2026 18:10:43 +0100")

Christian Couder <christian.couder@gmail.com> writes:

> First in https://git.github.io/General-Microproject-Information/ we
> have a "Don’t work on a proposed project right away" section, but
> unfortunately this patch is addressing the main issue of a project we
> are proposing.
>
> In general I think that there should be a design doc or a long
> discussion before we start implementing something, because the problem
> could be complex.

Thanks for clarification.  Perhaps you would want three tier set of
projects next year?  Microprojects to help you get your toes into
the community, middle sized projects to let you demonstrate how
capable you are to help you get chosen as an intern, and the real
projects?

      parent reply	other threads:[~2026-11-13 19:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 17:24 [Outreachy][PATCH] promisor-remote: honor promisor.fetchOrder when trying remotes Yopa Nelly
2026-11-05 14:30 ` Tanga Joris
2026-11-05 16:31 ` Kaartic Sivaraam
2026-11-05 22:55   ` Tatchou Yopa Nelly
2026-11-13  9:51     ` Kaartic Sivaraam
2026-11-13 12:13       ` Tatchou Yopa Nelly
2026-11-05 22:52 ` [Outreachy][PATCH v2] " Yopa Nelly
2026-11-05 23:09   ` Junio C Hamano
2026-11-13 17:10     ` Christian Couder
2026-11-13 19:46       ` Tatchou Yopa Nelly
2026-11-13 19:58       ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqy0awa4gi.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=tangajoris@gmail.com \
    --cc=yopatatchou@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox