From: Kousik Sanagavarapu <five231003@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: [TOPIC 07/11] New Contributors and Discord
Date: Sat, 21 Sep 2024 22:32:11 +0530 [thread overview]
Message-ID: <Zu78E+0Uk5fMSeQv@five231003> (raw)
In-Reply-To: <Zu2Eup+vjI3dALYu@nand.local>
Taylor Blau <me@ttaylorr.com> writes:
> How to attract new contributors? + Community Discord
> =====================================================
>
> (moderator: Jonathan N + Calvin Wan, notetaker: Emily)
>
> * jonathan: we talk about this a lot 🙂 let's avoid the common pitfall
> of catering to the tiktokkers and the youths (hypothesizing about
> "current generation"):
I guess I would fall into the "youths" category ;)
I started contributing about a year ago although most of my activity was
during the GSoC'23 period.
> * jonathan: related to community discord server - what does it mean to
> function better as a community?
> * calvin: the entry point doesn't need to be discord, but we should pick
> some entry point that lets users contribute other than mailing list
> participation
> * and need to be able to navigate new contributions comfortably
> * brian: how to write text that's accessible to non-native english
> speakers, for example? the mailing list isn't great for these kinds of
> changes.
> * discord is proprietary, that is sometimes an issue
> * moderation on discord is an issue - having an unmoderated discord will
> actually drive away contributors. that means actual dedicated
> moderation
> * balancing between sufficient moderation (list) and ease of use
> (discord)
I don't know if we get new contributors complaining about our workflow
being centered on the mailing list but I personally find the list really
intuitive to work with.
Even if we do eventually move towards a more "user-friendly" interface
_for_ new contributors, they may still need to read through history for
certain changes they maybe working on, ON the list.
> * patrick: new contributors sending changes but the changes being
> ignored
I do remember the time when I first contributed and was anxious about
the reply but I guess even if someone else doesn't review a particular
patch, Junio gets around to it eventually (which is not ideal, we want
more reviewers...) so they are not completely lost... everytime.
Although it would be great if there was some kind of an interface to say
that this patch is a new contribution to anyone going through the
messages similar to what Calvin said above. So that if the patch were
simple enough then maybe some of the newer contributors may also have a
go at reviewing the patch.
> * brian: git-send-email is a barrier, but so are PRs/MRs in some cases
I think the main barrier is the configuration of git-send-email rather
sending the patches themselves. Since most people have gmail accounts,
the setup becomes a pain because of the two-factor-auth and creating app
passwords and for someone who is mailing a minor change, this indeed
feels like a lot of effort not worth the time or energy.
> * jonathan: we don't advertise well that we can accept contributions in
> a different way if people are committed to the improvement
> * peff: sometimes a mentor can "translate" a contribution. Individual
> contributors are already interested in mentoring, do we need
> more/different mentoring?
I think having mentors would be great thing. Even if it is not 1:1.
Another thing that would be great is having a list of things on which a
new contributor could work on. GitGitGadget's issues used to do this by
tagging the appropriate issues "good-first-issue" but I guess it is not
properly maintained anymore.
I know there is also searching for "#leftoverbits" or "low hanging fruit"
on the list but the "good-first-issue" tagged issues on GitGitGadget are
probably more new-contributor-friendly than whole email threads.
> * nasamuffin: Gerrit has a community meeting once/month, should we
> use discord for f2f video meetups?
> * peff: if people want to do big group meetups great. we could also
> use it for 1:1 meetups that way, and advertise that it's an option
I think we hit on this topic last year too in the virtual contributor's
summit and I agree that having a regular meetup would be great and
something I personally would very much look forward to. This would also
help put faces to names.
Not exactly a regular community meeting but Review Club was kind of a
large step towards this I guess. I was exactly in one review club
meeting and it sadly got shutdown right after that :').
next prev parent reply other threads:[~2024-09-21 17:02 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 14:15 Notes from the Git Contributor's Summit, 2024 Taylor Blau
2024-09-20 14:17 ` [TOPIC 01/11] Rust Taylor Blau
2024-09-20 16:20 ` rsbecker
2024-09-23 2:25 ` Sean Allred
2024-09-23 12:17 ` rsbecker
2024-09-24 15:30 ` Phillip Wood
2024-09-24 22:44 ` rsbecker
2024-09-27 9:37 ` Sean Allred
2024-09-27 12:23 ` rsbecker
2024-09-27 17:40 ` rsbecker
2024-09-20 14:17 ` [TOPIC 02/11] Top-level lib/ directory Taylor Blau
2024-09-20 14:18 ` [TOPIC 03/11] Structured Error Handling Taylor Blau
2024-09-20 14:19 ` [TOPIC 04/11] Platform Support Policy Taylor Blau
2024-09-20 14:19 ` [TOPIC 05/11]: SHA 256 / Git 3.0 Taylor Blau
2024-09-20 19:22 ` Junio C Hamano
2024-09-20 14:20 ` [TOPIC 06/11] Git and Software Freedom Conservancy Taylor Blau
2024-09-20 14:20 ` [TOPIC 07/11] New Contributors and Discord Taylor Blau
2024-09-20 22:48 ` Junio C Hamano
2024-09-21 17:02 ` Kousik Sanagavarapu [this message]
2024-09-22 19:15 ` Junio C Hamano
2024-09-22 19:44 ` Junio C Hamano
2024-09-23 13:51 ` Konstantin Ryabitsev
2024-09-23 21:31 ` Junio C Hamano
2024-09-24 18:06 ` Konstantin Ryabitsev
2024-09-24 19:15 ` Junio C Hamano
2024-09-24 19:23 ` Konstantin Ryabitsev
2024-09-27 10:08 ` Phillip Wood
2024-09-27 19:22 ` Junio C Hamano
2024-10-01 15:23 ` Phillip Wood
2024-09-20 14:21 ` [TOPIC 08/11] Modern Build Systems Taylor Blau
2024-09-23 2:01 ` Eli Schwartz
2024-09-24 12:13 ` Patrick Steinhardt
2024-09-20 14:22 ` [TOPIC 09/11] Bundle-URI on fetch / resume-able clone Taylor Blau
2024-09-20 14:22 ` [TOPIC 10/11] Project Tracking Taylor Blau
2024-09-20 19:41 ` Junio C Hamano
2024-09-20 19:49 ` Junio C Hamano
2024-09-23 9:15 ` Phillip Wood
2024-09-20 14:23 ` [TOPIC 11/11] git-scm.com state of the site Taylor Blau
-- strict thread matches above, loose matches on Subject: below --
2024-08-24 17:20 [GSoC][PATCH] unit-tests: add tests for oidset.h Ghanshyam Thakkar
2024-08-26 7:02 ` Patrick Steinhardt
2024-08-26 9:31 ` Christian Couder
2024-08-26 15:46 ` Junio C Hamano
2024-09-26 18:28 ` Junio C Hamano
2024-09-26 19:12 ` [PATCH] howto-maintain-git: discarding inactive topics Junio C Hamano
2024-09-27 8:57 ` [GSoC][PATCH] unit-tests: add tests for oidset.h Christian Couder
2024-09-27 18:47 ` Junio C Hamano
2024-09-28 7:02 ` Patrick Steinhardt
2024-09-30 18:48 ` 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=Zu78E+0Uk5fMSeQv@five231003 \
--to=five231003@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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).