[PATCH] D24167: Moving to GitHub - Unified Proposal

Krzysztof Parzyszek via llvm-commits llvm-commits at lists.llvm.org
Fri Sep 2 11:56:37 PDT 2016

kparzysz added a comment.

In https://reviews.llvm.org/D24167#533142, @beanz wrote:

> In https://reviews.llvm.org/D24167#532327, @jlebar wrote:
> > Wait a second.  We're choosing between two proposals.  The three of us here are among the experts.
> Assuming that we're somehow experts on workflows above other contributors seems a bit presumptuous to me. Keep in mind the difference in the proposals isn't Git, so being a Git expert (which I'm certainly not) isn't really relevant. I'm not an expert on other people's workflows, so I would prefer if we approach this from a perspective of providing information and allowing people to form their own opinions.

I think this is more about addressing people's needs: we can't know everyone else's workflow, but we (well, not me) can certainly provide the answers to "how do I do this in git".  In that sense being a git expert definitely helps.

> > We absolutely should be comparing the two proposals explicitly, to draw users' attentions to the differences that we think are important.  Because we actually know something that others don't!



> Really? No offense, but this comes off as incredibly condescending. You're asserting that you know better than everyone else. I'm not saying we shouldn't help people compare the proposals. I'm saying we shouldn't draw conclusions for them. Our community is filled with a lot of really smart people and I strongly believe they are capable of forming their own informed decisions.

I am not an expert in either git or svn, nor do I want to become one for the sole purpose of making an informed decision here.  I cannot predict all possible consequences of either approach that could affect my work, and I do welcome a summary of the differences with their potential impact.  Moreover, it may very well be that the differences in the proposed solutions will not be significant to me and my workflow.  In that case, I would give preference to the solution that helps the the rest of the "core" developers.


More information about the llvm-commits mailing list