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

Re: [RFC] Git User's Survey 2010 (resend)

From
Jakub Narebski <jnareb@gmail.com>
Date
Jul 7, 2010, 21:37 UTC
Message-ID
<m3k4p7m0sv.fsf@localhost.localdomain>
In-Reply-To
<loom.20100707T112304-178@post.gmane.org>
Yann Dirson <ydirson@free.fr> writes:
Show 10 quoted lines
> Jakub Narebski <jnareb <at> gmail.com> writes:
> 
> > === 07. I use Git for (check all that apply): ===
> [...]
> >  + work projects
> >  + unpaid projects
> 
> "Unpaid" could be further split between personnal use, cooperating in
> public projects (includes "OSS development" below), working for NGO's
> and the like.
"Unpaid projects" simply means here not work (related).  I am not sure
if adding other options is worth it; I'd rather not have too many
possibile answers for a question.
 
Show 14 quoted lines
> > === 08. How do/did you obtain Git (install and/or upgrade)? ===
> > (multiple choice, with other)
> [...]
> > Description:
> > ~~~~~~~~~~~~
> > Explanation: "binary package" covers pre-compiled binary (e.g.  from
> > rpm or deb binary packages); "source package" covers things like
> > deb-src and SRPMS / *.src.rpm; "source script" is meant to cover
> > installation in source-based distributions, like 'emerge' in Gentoo.
> 
> Do we care about particular binary packages, like distro-provided,
> distro backports, RPMs for kernel.org and similar "official as in
> listed on git-scm.org" packages, 3rd-party packages (maybe with
> "please specify").
No, I don't think we do worry about this.
 
Show 7 quoted lines
> > === 09. On which operating system(s) do you use Git? ===
> [...]
> > OpenSolaris died, so I removed it.
> 
> It does not seem to have died, only "free-beer solaris" seems to -
> opensolaris.org still shows activity.  And even so, people may still
> have been using machines installed with it.
Nevertheless it's install base, as shown by previous surveys, is IMVHO
too small for it to have it as a separate option.
 
Show 11 quoted lines
> > === 11. What Git interfaces and frontends do you use? ===
> [...]
> > The problem with split part is that people can have troubls with
> > distinguising between interfaces, implementations, frontends and tools
> > (although "I don't know ..."  answer should, I think, help here).  The
> > problem with having it everything together is that the list of
> > possible answers gets long and a bit unwieldy.
> 
> "interface" is confusing, as shown by the need for "I only use
> (graphical) tools".  Use "command-line interfaces and frontends"
> instead ?
 
That's a good idea.  Thanks.
 
Show 6 quoted lines
> > === 12. What kind of Git tools do you use? ===
> > (multiple choice, with other)
> [...]
> >  + graphical blame or pickaxe tool
> 
> Mention gitk as example here ?
You meant here "git gui blame", didn't you?
Show 6 quoted lines
> > === 16. Which of the following features do you use? ===
> > (multiple choice, with other)
> [...]
> >  + one-way interaction with other SCMs (from SCM to git)
> 
> One-way from git to other SCM ?  I'm sure we care if many people do that :)
One way from SCM to git.
Show 5 quoted lines
> > === 17. Which of the following features would you like to see implemented in
> git? ===
> 
> + sophisticated diffcore stages (eg. directory rename, indent detection,
>   content move)
Thanks.

BTW. I think wholesame directory rename detection is one of proposed features already.

Show 7 quoted lines
> > What features should be mentioned besides those above?  What criteria
> > should we have for including features in this list?
> 
> Not sure if any reasonable idea that appeared on the list should be
> left out.  Answers would provide feedback for features not necessarily
> interesting to the average git@vger reader, but still appealing to our
> users.
I don't think ideas about _internal_ changes need to be here.  Also,
I do not remember _every_ feature proposel that appeared on the list...
 
Show 9 quoted lines
> > === 22. How do you compare the current version with the version from one year
> ago? ===
> [...]
> > This question was mainly excuse for providing list of main changes
> > from the year ago.  I think that this question should be removed, as
> > it doesn't bring any important information.
> 
> It still says whether the work done on dev side is seen as valuable by
> end users.
Ego stroking ;-))))

I'm not sure if it is worth having this question. If there were any big controversial changes, perhaps...

Show 5 quoted lines
> > === 23. How useful have you found the following forms of Git documentation? ===
> [...]
> >  + on-line help
> 
> Spell as "online" ?  At least I had difficulties to parse it :)
 
O.K.
 
> > === 28. How did you hear about this Git User's Survey? ===
> > (single choice, with other)
> 
> + relaying by co-workers bridging the team to the community
Hmmm... good catch.
-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: Yann DirsonNext: Yann Dirson
Message 14 of 24 in “[RFC] Git User's Survey 2010 (resend)”
  1. Jakub NarebskiJul 3, 2010
  2. Ævar Arnfjörð BjarmasonJul 4, 2010
  3. Jakub NarebskiJul 4, 2010
  4. Yann DirsonJul 7, 2010
  5. Jakub NarebskiJul 7, 2010
  6. Felipe ContrerasJul 10, 2010
  7. David BainbridgeJul 4, 2010
  8. Jakub NarebskiJul 4, 2010
  9. David BainbridgeJul 4, 2010
  10. Jakub NarebskiJul 5, 2010
  11. Scott ChaconJul 4, 2010
  12. Jakub NarebskiJul 4, 2010
  13. Yann DirsonJul 7, 2010
  14. Jakub NarebskiJul 7, 2010
  15. Yann DirsonJul 8, 2010
  16. Felipe ContrerasJul 10, 2010
  17. Jakub NarebskiJul 10, 2010
  18. Felipe ContrerasJul 11, 2010
  19. Jakub NarebskiJul 11, 2010
  20. David BainbridgeJul 12, 2010
  21. Felipe ContrerasJul 12, 2010
  22. David BainbridgeJul 12, 2010
  23. Felipe ContrerasAug 9, 2010
  24. Jakub NarebskiAug 10, 2010

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.