git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC] GIT user survey

From
PCPaolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Date
Jun 25, 2006, 14:04 UTC
Message-ID
<4d8e3fd30606250704vf0e77dx9c3a029807e3dccd@mail.gmail.com>
In-Reply-To
<7vfyhtv6iw.fsf@assigned-by-dhcp.cox.net>
On 6/25/06, Junio C Hamano <junkio@cox.net> wrote:
Show 12 quoted lines
> "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com> writes:
>
> > About you
> >
> >    1. What country are you in?
> >    2. What is your preferred language?
> >    3. What's your gender?
>
> Demography is interesting and quite relevant to understand the
> bias in the answers to the rest of the questions, although I do
> not see much point about #3.  Question #2 is relevant in i18n,
> of course.
Yeah, removed item #3.
> I would also ask if the respondent has her own patch in the
> git.git repository.  If most of them are git developers, the
> answer to the question "was git easy to learn" becomes
> suspicious, for example.
OK.
Show 9 quoted lines
> > Getting started with GIT
> >
> >    1. How did you hear about GIT?
> >    2. Did you find GIT easy to learn?
> >    3. What helped you most in learning to use it?
>
> Also "When did you start using git?" -- old timers who learned
> git when it was still young and small would have had an easier
> time to learn it.
OK.
Show 16 quoted lines
> > How you use GIT
> >
> >    1. Do you use GIT for work, unpaid projects, or both?
> >    2. How do you obtain GIT?  Source tarball, binary package, or
> >       pull the main repository?
> >    3. What platforms (hardware, OS, version) do you use GIT on?
> >    4. How many people do you collaborate with using GIT?
> >    5. How big are the repositories that you work on? (e.g. how many
> >       files, how much disk space)
> >    6. How many different projects do you manage using GIT?
> >    7. Which porcelains do you use?
>
> After seeing the Mercurial survey result, I think question #3
> should be stated a bit more concretely.  The results having
> mixture of i386 and Linux are not very interesting.  I would
> also add "how deep the history" to #5.
OK
Show 13 quoted lines
> > Getting help, staying in touch
> >
> >    1. Have you tried to get GIT help from other people?
> >          * If yes, did you get these problems resolved quickly and to
> >            your liking?
> >    2. Do you subscribe to the mailing list?
> >          * If yes, do you find it useful, and traffic levels OK?
> >    3. Do you use the IRC channel (#git on irc.freenode.net)?
> >          * If no, did you know that all of the core developers use
> >            IRC, and that there's almost 24-hour help available?
>
> About #3, I do not see some people I consider "core" often on
> the IRC.  Maybe "most of the core".

I think I can remove that part of the sentece, Pasky already had the same comment when I was discussing the sruvey on #GIT. My mistake.

New version attached.
About you
    1. What country are you in?
    2. What is your preferred language?
Getting started with GIT
    1. How did you hear about GIT?
    2. Did you find GIT easy to learn?
    3. What helped you most in learning to use it?
    4. When did you start using git?
How you use GIT
    1. Do you use GIT for work, unpaid projects, or both?
    2. How do you obtain GIT?  Source tarball, binary package, or
       pull the main repository?
    3. What hardware platforms do you use GIT on?
    4. What OS (please include the version) do you use GIT on?
    5. How many people do you collaborate with using GIT?
    6. How big are the repositories that you work on? (e.g. how many
       files, how much disk space, how deep is the histoty)
    7. How many different projects do you manage using GIT?
    8. Which porcellains do you use?
    9. Is the git.git repository including codes produced by you?
What you think of GIT
    1. Overall, how happy are you with GIT?
    2. How does GIT compare to other SCM tools you have used?
    3. What do you like about using GIT?
    4. What would you most like to see improved about GIT?
       (features, bugs, plugins, documentation, ...)
    5. If you want to see GIT more widely used, what do you
       think we could do to make this happen?
Documentation
    1. Do you use the GIT wiki?   If yes, do you find it useful?
    2. Do you find GIT's online help useful?
    3. What is your favourite user documentation for any software
       projects or products you have used?
    4. What could be improved on the GIT homepage?
Getting help, staying in touch
    1. Have you tried to get GIT help from other people?
          * If yes, did you get these problems resolved quickly and to
            your liking?
    2. Do you subscribe to the mailing list?
          * If yes, do you find it useful, and traffic levels OK?
    3. Do you use the IRC channel (#git on irc.freenode.net)?
Open forum
    1. What other comments or suggestions do you have that are not
       covered by the questions above?
-- 
Paolo
http://paolociarrocchi.googlepages.com
http://picasaweb.google.com/paolo.ciarrocchi
Previous: Junio C HamanoNext: Sam Ravnborg
Message 14 of 17 in “[RFC] GIT user survey”
  1. Paolo CiarrocchiJun 24, 2006
  2. Randal L. SchwartzJun 24, 2006
  3. Paolo CiarrocchiJun 24, 2006
  4. Randal L. SchwartzJun 24, 2006
  5. Petr BaudisJun 24, 2006
  6. Linus TorvaldsJun 24, 2006
  7. Petr BaudisJun 24, 2006
  8. Adrien BeauJun 24, 2006
  9. Matthias KestenholzJun 24, 2006
  10. Jakub NarebskiJun 29, 2006
  11. Martin LanghoffJun 24, 2006
  12. Paolo CiarrocchiJun 25, 2006
  13. Junio C HamanoJun 25, 2006
  14. Paolo CiarrocchiJun 25, 2006
  15. Sam RavnborgJun 25, 2006
  16. Jakub NarebskiJul 4, 2006
  17. Pavel RoskinJul 6, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.