git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Guillaume Cogoni <cogoni.guillaume@gmail.com>
To: Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
Cc: git@vger.kernel.org, Matthieu Moy <Matthieu.Moy@univ-lyon1.fr>,
	Jonathan Bressat <git.jonathan.bressat@gmail.com>,
	Derrick Stolee <derrickstolee@github.com>,
	guillaume.cogoni@gmail.com
Subject: Re: [PATCH 0/1] documentation: guide of best practices for GIT developer
Date: Wed, 13 Apr 2022 18:36:42 +0200	[thread overview]
Message-ID: <CAA0Qn1tZxGR0cUi2JSJtTFYe2Nk9xoGuHkruji1-53-Fhokmig@mail.gmail.com> (raw)
In-Reply-To: <CAJyCBOS=xCEmX3yPduDEQfkVYUUiawQ7sYgNHi2dGe-R2W5r-g@mail.gmail.com>

On Wed, Apr 13, 2022 at 4:36 PM Shaoxuan Yuan
<shaoxuan.yuan02@gmail.com> wrote:

> Wouldn't there be a possibility that this doc can degrade into a list of
> personal taste?

Of course, it could end like this, if someone writes something in this
document, it's because that person likes it. People are not going to
recommend something they don't use. But, I also think that it's not
really bad because the purpose it's to have a bunch of tools that
might interest others.

> The tools that people use can vary in an incredible way, thus the workflow
> defined by multiple tools can go even further. I think a workflow here is highly
> opinionated, and such a thing may disturb newcomers?

Yup, you got a point, it's a bit complicated to recommend a workflow
because there is a lot of variety. But, about tools, it's possible
because you just say how this tool can be useful for the project. In
my first recommendation I propose the built-in debugger of VS Code and
say that "It can be used to isolate certain parts of code, with this
you may be able to ask more precise questions when you are stuck.". I
think that recommendation may not disturb newcomers or other Git
developers because it's only a tip, use the tool or not, you have the
choice.

> Wouldn't it be better to let people decide on their own tools and Git
> should stay respectful?

It's just a tool recommendation, and I don't force anyone to use it.
Is it the name of the file "WorkingOnGit" that makes you think it's a
mandatory thing? Maybe "HelpToolForGit" is better?

> Let alone most people come into the community as
> developer, if they are going to be "WorkingOnGit", so they may already be
> well-suited in their own workflow?

Yes, naturally, but even if people have their own workflow with this
tool or this tool, maybe if you recommend a tool that is "better" for
working on Git, will they change their habits? But, as I said it's
just a recommendation, the final choice of whether to use it or not,
is up to them.

Thanks, I appreciate your answer and I hope I've answered your questions.
I think simply recommending tools is a good thing, because, as you
mentioned, recommending a workflow is complicated.

SIncerely,

COGONI Guillaume

  reply	other threads:[~2022-04-13 16:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 20:25 [PATCH 0/1] documentation: guide of best practices for GIT developer COGONI Guillaume
2022-04-12 20:25 ` [PATCH 1/1] " COGONI Guillaume
2022-04-13 14:36 ` [PATCH 0/1] " Shaoxuan Yuan
2022-04-13 16:36   ` Guillaume Cogoni [this message]
2022-04-16 12:34     ` [PATCH v1 0/1] Documentation/ToolsOnGit.txt: gather information about tools COGONI Guillaume
2022-04-16 12:34       ` [PATCH v1 1/1] " COGONI Guillaume
     [not found]       ` <63d7dc69656e47f7bc7bce4839711f32@SAMBXP02.univ-lyon1.fr>
2022-04-16 13:25         ` Matthieu Moy
2022-04-16 14:51           ` Philip Oakley
2022-04-16 17:11           ` Junio C Hamano
2022-04-17  9:35             ` [PATCH v2 0/1] Documentation/ToolsForGit.txt: Tools for developing Git COGONI Guillaume
2022-04-17  9:35               ` [PATCH v2 1/1] " COGONI Guillaume
     [not found]             ` <33d2087c66e44037b03db818dae60fea@SAMBXP02.univ-lyon1.fr>
2022-04-17 12:25               ` [PATCH v2 0/1] " Matthieu Moy
2022-04-20 13:06                 ` [PATCH v3 " COGONI Guillaume
2022-04-20 13:06                   ` [PATCH v3 1/1] " COGONI Guillaume
2022-04-20 21:23                     ` Junio C Hamano
2022-04-21  8:45                       ` [PATCH v4 0/1] " COGONI Guillaume
2022-04-21  8:45                         ` [PATCH v4 1/1] " COGONI Guillaume

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=CAA0Qn1tZxGR0cUi2JSJtTFYe2Nk9xoGuHkruji1-53-Fhokmig@mail.gmail.com \
    --to=cogoni.guillaume@gmail.com \
    --cc=Matthieu.Moy@univ-lyon1.fr \
    --cc=derrickstolee@github.com \
    --cc=git.jonathan.bressat@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=guillaume.cogoni@gmail.com \
    --cc=shaoxuan.yuan02@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).