git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Yann Dirson <ydirson@free.fr>
To: git@vger.kernel.org
Subject: Re: [RFC] Git User's Survey 2010 (resend)
Date: Wed, 7 Jul 2010 12:28:46 +0000 (UTC)	[thread overview]
Message-ID: <loom.20100707T112304-178@post.gmane.org> (raw)
In-Reply-To: 201007032158.57700.jnareb@gmail.com

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.

> === 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").

> === 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.


> === 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 ?


> === 12. What kind of Git tools do you use? ===
> (multiple choice, with other)
[...]
>  + graphical blame or pickaxe tool

Mention gitk as example here ?

> === 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 :)

> === 17. Which of the following features would you like to see implemented in
git? ===

+ sophisticated diffcore stages (eg. directory rename, indent detection,
  content move)

> 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.


> === 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.

> === 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 :)


> === 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

HTH,
-- 
Yann

  parent reply	other threads:[~2010-07-07 12:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-03 19:58 [RFC] Git User's Survey 2010 (resend) Jakub Narebski
2010-07-04  0:21 ` Ævar Arnfjörð Bjarmason
2010-07-04  8:13   ` Jakub Narebski
2010-07-07  9:18     ` Yann Dirson
2010-07-07 21:43       ` Jakub Narebski
2010-07-10 11:01   ` Felipe Contreras
2010-07-04  9:07 ` David Bainbridge
2010-07-04 11:14   ` Jakub Narebski
2010-07-04 20:48     ` David Bainbridge
2010-07-05  7:19       ` Jakub Narebski
2010-07-04 22:43 ` Scott Chacon
2010-07-04 23:48   ` Jakub Narebski
2010-07-07 12:28 ` Yann Dirson [this message]
2010-07-07 21:37   ` Jakub Narebski
2010-07-08  7:24     ` Yann Dirson
2010-07-10 11:31 ` Felipe Contreras
2010-07-10 19:58   ` Jakub Narebski
2010-07-11  9:57     ` Felipe Contreras
2010-07-11 17:42       ` Jakub Narebski
2010-07-12 10:14         ` David Bainbridge
2010-07-12 10:19           ` Felipe Contreras
2010-07-12 10:22             ` David Bainbridge
2010-08-09 21:59 ` Felipe Contreras
2010-08-10 22:16   ` Jakub Narebski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20100707T112304-178@post.gmane.org \
    --to=ydirson@free.fr \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).