git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Derrick Stolee <stolee@gmail.com>,
	ananyakittu1997@gmail.com, git <git@vger.kernel.org>
Subject: Re: [PATCH][Outreachy] remove all the inclusions of git-compat-util.h in header files
Date: Wed, 10 Oct 2018 11:13:46 +0200	[thread overview]
Message-ID: <CAP8UFD1_CH-OGytqcLya0GdFAM3=TLpgwiXQCO__9GSR6SXe_Q@mail.gmail.com> (raw)
In-Reply-To: <xmqq4ldumbo1.fsf@gitster-ct.c.googlers.com>

On Wed, Oct 10, 2018 at 10:46 AM Junio C Hamano <gitster@pobox.com> wrote:
>
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > Personally, I find the "whoever is picking it up should do the thinking"
> > much too harsh for a first-time contributor who specifically came through
> > the Outreachy program, i.e. expected to have a gentle introduction into
> > the project, and into the ways we work.
>
> Oh, absolutely I agree.
>
> Any random discussion participant can say "left over bits" in any
> random message with an idea that is left on the table.  Looking for
> it may narrow the set messages to be examined, but the query result
> will inevitably be still full of chaff.  It is not a very good match
> for "gentle introduction" material for GSoC/Outreachy microprojects.
>
> List of reasonable low-hanging fruits is hard to maintain, as the
> cost of building and maintaining such a list would easily outweigh
> the cost (and fun) of picking these low-hanging fruits yourself X-<.
>
> I do not think of a good solution to help newcomers offhand.

In the "How to find other ideas for microprojects" on
https://git.github.io/SoC-2018-Microprojects/ there is already the
following:

"When you find something you are interested to work on, please ask
first on the mailing list if it’s worth doing and if it’s appropriate
for a microproject before starting to work on what you find. Even if
it looks straightforward, there could be hidden reasons why it is too
difficult or just inappropriate."

So I think one solution to this problem is already proposed on our web site.

  reply	other threads:[~2018-10-10  9:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08 17:05 [PATCH][Outreachy] remove all the inclusions of git-compat-util.h in header files Ananya Krishna Maram
2018-10-08 17:13 ` Derrick Stolee
2018-10-09  2:16   ` Ananya Krishna Maram
2018-10-09 10:13   ` Junio C Hamano
2018-10-10  8:06     ` Johannes Schindelin
2018-10-10  8:46       ` Junio C Hamano
2018-10-10  9:13         ` Christian Couder [this message]
2018-10-10 12:22           ` Junio C Hamano

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='CAP8UFD1_CH-OGytqcLya0GdFAM3=TLpgwiXQCO__9GSR6SXe_Q@mail.gmail.com' \
    --to=christian.couder@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=ananyakittu1997@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=stolee@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;
as well as URLs for NNTP newsgroup(s).