From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Christian Couder" <christian.couder@gmail.com>,
"Markus Jansen" <mja@jansen-preisler.de>,
"Jakub Narębski" <jnareb@gmail.com>
Subject: Collaborative community interview for Git's 20th anniversary
Date: Mon, 14 Apr 2025 18:01:14 +0530 [thread overview]
Message-ID: <85ea4aa0-c595-4f0b-a2ac-d0113aca464a@gmail.com> (raw)
Hello all,
As part of the Git's 20th year anniversary, we from the Git Rev News
team are thinking of doing a community interview where we would share a
list of questions that we've prepared and we would like to welcome
answers from anyone in the community for them. We could gather the
answers for them upto a particular time (like 25/April or so) and begin
curating the answers into a special interview for this month's edition.
The questions are below. Feel free to respond with your answers to this
mail thread. Let me know if I've missed to include any particularly
compelling question.
- What's your favorite Git trick or workflow that you wish more people
knew about?
- What was your worst Git disaster, and how did you recover from it?
- If you could go back in time and change one design decision in Git,
what would it be?
- Which Git feature or improvement over the past 20 years do you think
had the biggest impact on your workflow?
- What Git problem that existed 10 years ago has been most
successfully solved?
- Which Git commands or workflows do you think are still misunderstood
or underutilized today?
- What's one Git based project, tool, or extension you think deserves
more recognition from the community?
- What Git feature or capability surprised you most when you first
discovered it?
- What's your boldest prediction about how version control might look
in another 20 years?
Looking forward to see interesting answers. :-)
--
Sivaraam for the Git Rev News team.
next reply other threads:[~2025-04-14 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 12:31 Kaartic Sivaraam [this message]
2025-04-14 12:37 ` Collaborative community interview for Git's 20th anniversary Luca Milanesio
2025-04-14 15:04 ` Lucas Seiki Oshiro
2025-04-23 22:41 ` Elijah Newren
2025-05-02 5:35 ` Kaartic Sivaraam
2025-05-02 5:37 ` Kaartic Sivaraam
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=85ea4aa0-c595-4f0b-a2ac-d0113aca464a@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=mja@jansen-preisler.de \
/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