On Wed, Apr 13, 2022 at 7:29 AM COGONI Guillaume <cogoni.guillaume@xxxxxxxxx> wrote: > > Hello, > > This patch has for purpose to introduce a file where GIT developers can share > their own best practices, tools or workflows to the community in order to > help the GIT developer. Wouldn't there be a possibility that this doc can degrade into a list of personal taste? I think the rules that new developers *should* know have already been documented in 'MyFirstContribution.txt' or 'SubmittingPatches' and things like that. If there is a *common* recommended practice, if not "their own", I guess it can be added into existing documentations. > The discussion about this idea begin in this thread: > Message-Id: <20220407204001.112287-2-cogoni.guillaume@xxxxxxxxx> > > Derrick Stolee and I agreed that is can be a good idea. > And, I think, it can help a newcomer, but not necessarily people with a > lot of experience on various projects. But, we can give it a try and > see where it goes. > > PS: > I do not believe it is a good idea to give detailed tutorials because there > are a lot on the internet. However, give the reader pros, cons and curiosity > to test those tools, practice or workflow can be really good. 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? Wouldn't it be better to let people decide on their own tools and Git should stay respectful? 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? -- Thanks & Regards, Shaoxuan
