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

On 19 August 2016 at 13:50, Bruce Hoult <bruce at hoult.org>
wrote:
> For people who are doing read-only access, to include llvm in the build of
> some other project, the impact might be as small as a one-time changing of
> the URL for the "svn checkout" in their script.
For that kind of use, I believe the GitHub SVN interface will "just
work". I have tested it read-only and read-write access and my SVN
client was very happy with it.

Some people said it was a bit slow, but that should only make a
difference if you're checking out the whole thing. (svn relocate may
help, too).

But there's also the idea of changing the process to Git, which would
involve some changes to their scripts, but not a big one.

I'm more worried with huge build systems that heavily use SVN as a
core part of their infrastructure, making it a lot harder to "move to
git".

I'm expecting this number to be small nowadays...

cheers,
--renato

I think that if we’re going to do a survey we should gather more information
about how people interact with the LLVM projects, not just opinions on the
proposals.

A few questions I think would be useful.

(1) Which project(s) do you contribute to?
(2) Which project(s) do you regularly use?
(3) How often do you bisect LLVM with one or more subproject?
(4) Do you use any of the llvm.org <http://llvm.org/> projects without
LLVM or with out-of-sync LLVM (i.e. trunk libunwind with an old LLVM)?
(5) In which ways do you get LLVM sources from LLVM.org
<http://llvm.org/>?
   (a) SVN
   (b) llvm.org <http://llvm.org/> Git mirrors
   (c) Git-SVN
   (d) GitHub Git mirrors
   (e) Other
(6) Do you, or an organization you are affiliated with, maintain tooling or
infrastructure that interacts with llvm.org <http://llvm.org/> and is not
public?

-Chris

> On Aug 19, 2016, at 5:57 AM, Renato Golin via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> On 19 August 2016 at 13:50, Bruce Hoult <bruce at hoult.org> wrote:
>> For people who are doing read-only access, to include llvm in the build
of
>> some other project, the impact might be as small as a one-time changing
of
>> the URL for the "svn checkout" in their script.
> 
> For that kind of use, I believe the GitHub SVN interface will "just
> work". I have tested it read-only and read-write access and my SVN
> client was very happy with it.
> 
> Some people said it was a bit slow, but that should only make a
> difference if you're checking out the whole thing. (svn relocate may
> help, too).
> 
> But there's also the idea of changing the process to Git, which would
> involve some changes to their scripts, but not a big one.
> 
> I'm more worried with huge build systems that heavily use SVN as a
> core part of their infrastructure, making it a lot harder to "move to
> git".
> 
> I'm expecting this number to be small nowadays...
> 
> cheers,
> --renato
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160819/475f1fa5/attachment.html>

Hi Chris,

Bear in mind that the more questions we have, the harder it will be to
interpret the results. If we have 20+ questions, it'll be impossible
to understand anything.

Also, the multiple choice questions are meant as a guide to understand
"how many" people fall into one or another category, while the free
text ones are meant to complement and give technical reasons for their
answers.

So, we should focus our multiple choice questions on divisive topics
and let everything else to the free text-fields.


On 19 August 2016 at 18:06, Chris Bieneman <beanz at apple.com>
wrote:
> (1) Which project(s) do you contribute to?
> (2) Which project(s) do you regularly use?
I've added these two as one. I know they're slightly different, but so
will be the the answer to the first question, which will work to
disambiguate this one.

> (3) How often do you bisect LLVM with one or more subproject?
I understand that this is a contentious issue around the git move, but
we should focus on the bigger picture, which is day to day usage as
well as infrastructure.

> (4) Do you use any of the llvm.org projects without LLVM or with
out-of-sync
> LLVM (i.e. trunk libunwind with an old LLVM)?
This looks very specific to me, I'm trying to avoid side questions
here and let people write up on the free text areas what their usage
is.

> (5) In which ways do you get LLVM sources from LLVM.org?
>    (a) SVN
>    (b) llvm.org Git mirrors
>    (c) Git-SVN
>    (d) GitHub Git mirrors
>    (e) Other
I don't think that previous usage is relevant. It may be relevant to
the people doing it and to their responses on how hard it will be, but
this should be encoded in the other questions. Some of that already
is.

> (6) Do you, or an organization you are affiliated with, maintain tooling or
> infrastructure that interacts with llvm.org and is not public?
This is a topic for the free-text fields.

 cheers,
--renato