Re: [PATCH 0/1] documentation: guide of best practices for GIT developer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Apr 13, 2022 at 4:36 PM Shaoxuan Yuan
<shaoxuan.yuan02@xxxxxxxxx> 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



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux