From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Mike Hommey <mh@glandium.org>, Derrick Stolee <stolee@gmail.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>,
Jeff King <peff@peff.net>,
Emily Shaffer <emilyshaffer@google.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Garima Singh <garimasigit@gmail.com>
Subject: Re: [DISCUSSION] Growing the Git community
Date: Tue, 01 Oct 2019 17:03:23 +0200 [thread overview]
Message-ID: <865zl8pkxw.fsf@gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1909232316300.15067@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Mon, 23 Sep 2019 23:28:05 +0200 (CEST)")
Hello,
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> On Fri, 20 Sep 2019, Mike Hommey wrote:
>> 6. Newcomers don't really have any idea /what/ they could contribute.
>> They either have to come with their own itch to scratch, or read the
>> code to figure out if there's something to fix.
>
> I think this is very related to the "not only open the door, but invite
> contributors in" idea mentioned upthread.
>
> Speaking from my experience as mentor in particular in Outreachy, it is
> often not obvious to old-timers in this here project (including myself!)
> how intimidating even the idea of "scratching your own itch" is, and
> it can be tremendously helpful to even so much as seeing the problem
> stated by somebody else first ("Others agree with me! I need not have
> doubted myself when I ran into this problem, it really is a bug that
> needs to be fixed!").
>
> Additionally, it is no longer all that easy to come up with an "own
> itch" to scratch, as the most common workflows work reasonably well in
> Git. Yet, it seems that some users _still_ want to "give back" by
> contributing patches. Or they just want to see their name in the next
> version's announcement mail.
>
> To address both concerns, I started this little experiment a while ago
> (but announced it only during a Git IRC standup):
> https://github.com/gitgitgadget/git/issues is open, intended to
> accumulate possible project ideas. It seems to work reasonably well,
> there already have been volunteers who picked up on some of those ideas
> I (and Denton) listed.
>
> Hopefully this issue tracker (together with https://crbug.com/git which
> targets users more comfortable with that flavor of issue trackers) will
> help address your bullet point?
It would be nice to have those issue trackers announced more widely (on
the homepage, on the Git Rev News homepage, maybe also in docs e.g.
CONTRIBUTING).
For me, beside being the place where to find out some ideas on how to
contribute, would be having a place to put my ideas that I have not had
time to even start to do, like adding `git gui diff` (e.g. borrowing
from tkdiff) and `git instaweb --serve`.
Best,
--
Jakub Narębski
next prev parent reply other threads:[~2019-10-01 15:03 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 16:30 [DISCUSSION] Growing the Git community Derrick Stolee
2019-09-19 17:34 ` Denton Liu
2019-09-19 20:43 ` Emily Shaffer
2019-09-19 22:26 ` Jeff King
2019-09-20 17:48 ` Junio C Hamano
2019-09-20 15:22 ` Garima Singh
2019-09-20 17:51 ` Junio C Hamano
2019-09-19 18:44 ` Klaus Sembritzki
2019-09-19 19:12 ` Klaus Sembritzki
2019-09-19 20:20 ` Klaus Sembritzki
2019-09-20 5:04 ` Klaus Sembritzki
2019-09-20 5:41 ` Klaus Sembritzki
2019-09-20 6:54 ` Klaus Sembritzki
2019-09-20 7:43 ` Klaus Sembritzki
2019-09-20 10:25 ` Klaus Sembritzki
2019-09-19 21:40 ` Mike Hommey
2019-09-23 21:28 ` Johannes Schindelin
2019-10-01 15:03 ` Jakub Narebski [this message]
2019-09-19 22:16 ` Jeff King
2019-09-20 2:17 ` Derrick Stolee
2019-09-20 2:23 ` Jeff King
2019-09-19 22:21 ` Elijah Newren
2019-09-25 13:36 ` Pierre Tardy
2019-09-25 14:02 ` Derrick Stolee
2019-10-04 12:39 ` Jakub Narebski
2019-09-25 14:14 ` Philip Oakley
2019-10-04 10:48 ` Jakub Narebski
2019-11-12 18:45 ` Emily Shaffer
2019-11-12 20:01 ` Johannes Schindelin
2019-11-13 6:45 ` Christian Couder
2019-11-13 15:06 ` Thomas Gummerer
2019-11-14 2:31 ` Emily Shaffer
2019-11-14 6:06 ` Jeff King
2019-11-15 4:48 ` Junio C Hamano
2019-11-14 6:08 ` Pratyush Yadav
2019-11-14 10:01 ` Thomas Gummerer
2019-09-20 10:48 ` Philip Oakley
2019-09-20 14:36 ` brian m. carlson
2019-09-20 15:16 ` Randall S. Becker
2019-10-04 14:27 ` Jakub Narebski
2019-09-20 15:20 ` Garima Singh
2019-09-20 17:43 ` Junio C Hamano
2019-09-20 18:52 ` Junio C Hamano
2019-09-23 12:36 ` Derrick Stolee
2019-09-23 21:46 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=865zl8pkxw.fsf@gmail.com \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=emilyshaffer@google.com \
--cc=garimasigit@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=mh@glandium.org \
--cc=peff@peff.net \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).