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

Re: [RFC] Questions for "Git User's Survey 2011"

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Jul 31, 2011, 13:53 UTC
Message-ID
<CAMP44s2CWvzKyBAskVRq6Vte-CyCKwxBCZbSw_mbp=4a6ngCOw@mail.gmail.com>
In-Reply-To
<201107252233.02088.jnareb@gmail.com>
2011/7/25 Jakub Narebski <jnareb@gmail.com>:
> I am planning doing annual Git User's Survey, and I'd like to ask for
> feedback.
Show 56 quoted lines
> === 16. Which of the following Git features do you use? ===
> (multiple choice, with other)
>
>  + localization of command-line messages (i18n)
>  + git bundle (off-line transport)
>
>  + eol conversion (crlf or eol)
>  + gitattributes (any)
>  + custom diff/merge driver
>  + word diff
>  + merge strategy options (e.g. -Xrenormalize)
>  + textconv
>
>  + submodules (subprojects)
>  + subtree merge (optionally git-subtree)
>
>  + partial (sparse) checkout, or assume-unchanged bit
>
>  + separate worktree / core.worktree
>  + multiple worktrees (e.g. git-new-worktree)
>  + gitdir mechanism (.git file pointing to repository)
>
>  + alternates mechanism (sharing object database)
>  + stash (optionally "git stash --keep-index")
>  + shallow clone (e.g. "git clone --depth=<n>")
>  + detaching HEAD (e.g. "git checkout --detach")
>  + commit message templates
>  + interactive commit / per-hunk comitting / partial commit
>  + interactive rebase (small scale history editing)
>  + git-filter-branch or equivalent (large history rewriting)
>  + bisect (optionally "git bisect run <script>")
>  + tracking code movement with git-blame ("git blame -M" etc.)
>  + committing with dirty tree (keeping some changes uncommitted)
>
>  + non-default hooks (from contrib/hooks/ or other)
>  + shell completion of commands
>  + git-aware shell prompt
>  + git aliases, shell aliases for git, or own git scripts
>
>  + one-way interaction with other SCMs (from SCM to git)
>  + two-way interaction with other SCMs (from SCM to git, from git to SCM)
>
>  + git-cvsserver
>  + git notes
>
>
>  + Other, please specify
>
> NOTES:
> ^^^^^^
> The problem is come up not with exhaustive list of features: there are
> too many of them to list.  The problem is coming up with list of
> important and used enough often features.
>
> So: what features should be included in this list?  What features
> should be removed from above list of answers?
*staging*! I have suggested this multiple times, it should be here this one!
- stage add / partial commit / interactive commit / per-hunk comitting
(e.g. git add -u/-i/-p)
+ stage / partial or interactive commits (e.g. git add -u/-i/-p, git
diff --cached)
Show 16 quoted lines
> === 19. Overall, how happy are you with Git? ===
> (single choice)
>
>  * unhappy
>  * not so happy
>  * happy
>  * very happy
>  * completely ecstatic
>
> NOTES:
> ^^^^^^
> I'm not sure if this question is at all useful.
>
> There is also problem, that the current wording is considered biased
> by some, but on the other hand changing wording of answers would make
> it impossible to compare it to answers from previous surveys...
What wording would you use?
Show 16 quoted lines
> === 20. In your opinion, which areas in Git need improvement? ===
>        Please state your preference.
> (matrix)
>
>   Columns: don't need / a little / some / much
>  + user-interface
>  + documentation
>  + performance
>  + more features
>  + tools (e.g. GUI)
>  + localization (translation)
>
> NOTES:
> ^^^^^^
> Are there any general areas that are missing from this list?
> What are they?
IDE integration, portability?
Show 39 quoted lines
> == About this survey. Open forum. ==
>
> === 26. How did you hear about this Git User's Survey? ===
> (single choice, with other)
>
>  * git mailing list
>  * git-related mailing list (e.g. msysGit, Git for Human Beings)
>  * mailing list or forum of some project
>  * #git IRC channel topic
>  * announcement on IRC channel
>  * git homepage
>  * git wiki
>  * git hosting site (or blog related to such site)
>  * software-related web site
>  * news or social news site (e.g. Digg, Reddit)
>  * blog (or blog planet)
>  * other kind of web site
>  * Twitter or other microblogging platform
>
>  * other - please specify
>
> NOTES:
> ^^^^^^
> This list would of course be updated to reflect the list of (planned)
> announcement channels.
>
> There of course will be announcement on Git Mailing List, and perhaps
> also on msysGit list / Google Group, and on Git For Human Beings
> Google Group (if it exists).  I'll announce it on #git, and ask op to
> put short announcement in channel description, and I can announce it
> on other IRC channels.  I would add announcement to main page of Git
> Wiki, and as Git Homepage administrator to put announcement about Git
> User's Survey.
>
> I usually tried to contact administrators of git hosting sites,
> including git.kernel.org, repo.or.cz, GitHub, Gitorious, Assembla,
> Codebase and Unfuddle, asking them to put announcement about
> Git User's Survey either somewhere on the site, or in their blog
> (if there is any).  What git hosting sites it is worth to ask?
Google+ (maybe facebook).
Show 8 quoted lines
> I would like to have announcement of Git User's Survey 2010 at
> LWN.net, but this would need to be send at least two weeks in advance,
> if I remember correctly.  Is it worth it?  What other news site should
> I (or you) send announcement to?
>
> If you can Digg / Reddit announcment on some site, please do.  I can
> announce Git User's Survey 2-1- at Twitter, Identi.ca and Plurk, but I
> don't have wide area of followers.  So please RT.
I can post it on reddit :)
> Should we contact some bloggers (besides asking Junio to put
> announcement on his blog) to post an anouncement?  Which bloggers
> would respond positively (perhaps Linus...)?
I can post it on gitlog. It looks like there are now many people checking it.
-- 
Felipe Contreras
Previous: David AguilarNext: Jakub Narebski
Message 10 of 35 in “[RFC] Questions for "Git User's Survey 2011"”
  1. Jakub NarebskiJul 25, 2011
  2. Phil HordJul 25, 2011
  3. Jakub NarebskiJul 26, 2011
  4. Phil HordJul 26, 2011
  5. Felipe ContrerasJul 31, 2011
  6. Jakub NarebskiAug 1, 2011
  7. David AguilarSep 3, 2011
  8. Jakub NarebskiSep 3, 2011
  9. David AguilarSep 3, 2011
  10. Felipe ContrerasJul 31, 2011
  11. Jakub NarebskiAug 2, 2011
  12. Heiko VoigtAug 1, 2011
  13. Jakub NarebskiAug 2, 2011
  14. Jens LehmannAug 2, 2011
  15. Jakub NarebskiAug 3, 2011
  16. Ævar Arnfjörð BjarmasonAug 3, 2011
  17. Jakub NarębskiAug 3, 2011
  18. Felipe ContrerasSep 3, 2011
  19. Jakub NarebskiSep 3, 2011
  20. Felipe ContrerasSep 14, 2011
  21. Jakub NarebskiSep 14, 2011
  22. Felipe ContrerasSep 19, 2012
  23. Jakub NarębskiSep 22, 2012
  24. Junio C HamanoSep 23, 2012
  25. Jakub NarębskiSep 23, 2012
  26. Michael J GruberSep 24, 2012
  27. Jakub NarębskiSep 24, 2012
  28. Matthieu MoySep 24, 2012
  29. Jakub NarębskiSep 24, 2012
  30. Matthieu MoySep 24, 2012
  31. Jakub NarębskiSep 24, 2012
  32. Matthieu MoySep 24, 2012
  33. Jakub NarębskiSep 24, 2012
  34. Matthieu MoySep 25, 2012
  35. Jakub NarębskiSep 25, 2012

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.