git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Andrew Ardill <andrew.ardill@gmail.com>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
	Doug Rathbone <doug@dougrathbone.com>,
	David Bainbridge <david.bainbridge@gmail.com>,
	Stefan Beller <sbeller@google.com>
Subject: Re: [RFC] Proposed questions for "Git User's Survey 2016"
Date: Fri, 26 Aug 2016 16:58:14 +1000	[thread overview]
Message-ID: <CAH5451nMeuZttRgM8LK3JcPhfOYHieyawV2pJzp0jdh2KAf60Q@mail.gmail.com> (raw)
In-Reply-To: <90165dce-c508-4cb4-ec6e-c3d271181fe3@gmail.com>

Hi,

Jakub Narębski <jnareb@gmail.com> wrote:
> Andrew Ardill pisze:
> > Jakub Narębski <jnareb@gmail.com> wrote:
> >> 25. What [channel(s)] do you use to request/get help about Git [(if any)]
> >
> > It may also be useful to ask how people hear news about git, such as
> > when a new release comes out. Not sure if worth a separate question,
> > as there is a lot of crossover in the resources available for this and
> > for requesting help, but knowing this information would help us
> > understand what kinds of users are responding and which communication
> > channels are effective for git news.
>
> How would you propose such question would look like, and what proposed
> answers would be (if it were not a free-text / essay question)?

Something like:

XX. How do you hear about git related news (such as new releases and
community events)?
    (multiple choice or single choice?)
 * I wasn't aware there was any news
 * I don't read any news, but I'm aware of it
 * through news aggregation sites (such as reddit or hacker news)
 * from a newsletter (such as Git Rev News)
 * from a mailing list (such as the git developer or the git for windows list)
 * other

It would be good to allow a list of specific resources to be written
to capture things we don't know about, and specific instances of the
categories above, eg:
"hacker news, git mailing list, git rev news"

> Note that there might be a problem of severe bias: people who heard
> about Git User's Survey 2016 are probably ones that watch news about Git.
> Still, it would be useful to know if people read RelNotes...

Agreed, the intent behind the question is to work out what are the
effective communication channels so that they can be used more
effectively.


> That is, if people have a pattern to their upgrade of Git, and can
> tell how often they upgrade.
>
> XX. How often you upgrade Git?
>     (multiple choice or single choice?)
>
>  * as soon as new version is released
>  * when there is new binary package / distribution package
>  * when updating distribution / system
>  * around every month, or more often
>  * around every 6 months or more often
>  * I use what is installed on system
>
> Something like that?

Exactly, looks great.

Regards,

Andrew Ardill

  reply	other threads:[~2016-08-26  6:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-20 18:56 [RFC] Proposed questions for "Git User's Survey 2016" Jakub Narębski
2016-08-20 21:29 ` Eric Wong
2016-08-25 10:26   ` Jakub Narębski
2016-08-21 23:59 ` Andrew Ardill
2016-08-25 14:53   ` Jakub Narębski
2016-08-26  6:58     ` Andrew Ardill [this message]
2016-08-26 11:42       ` Jakub Narębski
2016-08-26  6:15 ` Eric Wong
2016-08-26 11:52   ` Jakub Narębski
     [not found]     ` <CAFO0PHfy_teFFMiuFdjKYohCgRZHNT+Cc8hXOjsPeRTi9gAHPQ@mail.gmail.com>
2016-08-26 23:46       ` Jakub Narębski
2016-08-28  9:49     ` Eric Wong
2016-08-28 11:22       ` Jakub Narębski
2016-08-27 22:00 ` [RFCv2] Proposed questions for "Git User's Survey 2016", take two Jakub Narębski
2016-09-05 21:27   ` [RFCv3] Proposed questions for "Git User's Survey 2016", take three Jakub Narębski
     [not found]     ` <CAFO0PHc48OmWNcRrh2Wu30L6Oarqyw+co+zNPpsPEWerCiqanw@mail.gmail.com>
     [not found]       ` <CAFO0PHdGppfgSSYW4YB-0LEsuohyzSCkrk48fovppNfDYZx78w@mail.gmail.com>
2016-09-09 20:20         ` Jakub Narębski

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=CAH5451nMeuZttRgM8LK3JcPhfOYHieyawV2pJzp0jdh2KAf60Q@mail.gmail.com \
    --to=andrew.ardill@gmail.com \
    --cc=david.bainbridge@gmail.com \
    --cc=doug@dougrathbone.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=sbeller@google.com \
    /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).