llvm dev - Aug 2016 - [RFC] GitHub Survey - Please review

On 19 August 2016 at 18:20, Justin Bogner <mail at justinbogner.com>
wrote:
> The one time cost of the mono-repo proposal is drastically different
> than that of the multi-repo.
True.

But maybe not as different as from one company / project to another.
I'm assuming some people will suffer a lot more than others on either
choice.

> I already use git, but depending on how things are organized in the new
> world this may completely change how I work with LLVM.
It will, but you already work around with Git-SVN, which is a pain.

I don't see "the other option" being more cumbersome than Git-SVN,
whatever is the one option you pick. But this is just my opinion.

If that doesn't work for you, can you suggest a solution that will?

cheers,
--renato

Renato Golin <renato.golin at linaro.org> writes:
> On 19 August 2016 at 18:20, Justin Bogner <mail at justinbogner.com>
wrote:
>> The one time cost of the mono-repo proposal is drastically different
>> than that of the multi-repo.
>
> True.
>
> But maybe not as different as from one company / project to another.
> I'm assuming some people will suffer a lot more than others on either
> choice.
>
>
>> I already use git, but depending on how things are organized in the new
>> world this may completely change how I work with LLVM.
>
> It will, but you already work around with Git-SVN, which is a pain.
I think you misunderstood what I meant here. Whether "moving to git"
will affect my workflow depends very much on "how we're moving to
git". For example, if we do a monorepo, I may now need to lay code out
differently on my filesystem (since I currently check out multiple repos
rooted at llvm), or if we do a multirepo I probably need to learn some
new commands to associate llvm and clang repos (rather than using git
svn find-rev). If we do something where there's a monorepo of some of
the stuff but not all, I probably have to adapt to things from each.

What I'm saying is "How much will moving to git affect your
workflow?"
isn't a meaningful question without concrete data on what the repos will
look like if we do move.
> I don't see "the other option" being more cumbersome than
Git-SVN,
> whatever is the one option you pick. But this is just my opinion.
>
> If that doesn't work for you, can you suggest a solution that will?

On 19 August 2016 at 19:35, Justin Bogner <mail at justinbogner.com>
wrote:
> I think you misunderstood what I meant here. Whether "moving to
git"
> will affect my workflow depends very much on "how we're moving to
> git".
That's exactly what I understood. :)

> For example, if we do a monorepo, I may now need to lay code out
> differently on my filesystem (since I currently check out multiple repos
> rooted at llvm), or if we do a multirepo I probably need to learn some
> new commands to associate llvm and clang repos (rather than using git
> svn find-rev). If we do something where there's a monorepo of some of
> the stuff but not all, I probably have to adapt to things from each.
My point is: either way, you'll have to "change your workflow".
For
some people workflow A will be "less change", for others, it will be
workflow B. For some others still, neither A nor B will be easier than
Git-SVN, or just SVN.

My other point was: *a lot* of people already "adapt" their workflow,
so capturing how much each option will make to each person is less
important than catching how much *any* change will mean to *most*
people.

To capture and weigh each edge of a graph with hundreds of nodes will
need a very smart AI. But I can do it reasonably well with a dozen or
so on my own. I don't have the time nor the expertise to build such an
AI, and it would ultimately have uncertainties, which could very well
amount to the same ones we get with less, imprecise questions.

This whole exercise has already deviated the focus and work of *A LOT*
of people in the community. I'm trying to make it less painful.

So, I think it's perfectly acceptable to lose some of the semantics on
the questions if we get the gist of what the community wants.

makes sense?

--renato