git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephan Beyer <s-beyer@gmx.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC v2] Git User's Survey 2008
Date: Sun, 24 Aug 2008 23:36:34 +0200	[thread overview]
Message-ID: <20080824213634.GA16753@leksak.fem-net> (raw)
In-Reply-To: <200808200308.26308.jnareb@gmail.com>

Hi again,

> 8.  Which Git version(s) are you using? 
>  [ ] pre 1.3
>  [ ] 1.3.x
...
>  [ ] master
>  [ ] next

I wonder if people who do not know about master/next being git.git
branches may do "[X] next" because they think they will use the next
version available.

So could you write "master branch of official git repository" and the
same for "next"?

> 12. What other SCM did or do you use?
...
> By "custom (non-published)" it is meant here version control system
> which was not released to the public, for example something written
> for yourself, or internal company project used only in company.

Better:
 "custom (non-published)" means a version control system which has
 not been released to the public, for example, something written for
 yourself or your company only.

And I am unsure if "SCM" is better than "version control system"
in this sentence, but I do not think this is really important.

> 16. I use Git for (check all that apply):
...
> Note that above choices are neither orthogonal nor exclusive.
> You might want to check multiple answers wven for single repository.
                                           ^^^^^^^^^ "even for a"

> 17. How do you obtain Git?
...
>  [ ] pull form main repository
            ^^^^ from

> Explanation: binary package covers pre-compiled binary; source script
> is meant to cover installation in source-based distributions, like
> 'emerge' in Gentoo.

"pre-compiled binary (e.g. from rpm or deb archives)"

Right?
I think naming two popular package formats of distributors should people
help to get the point.

> 29. Which of the following features do or did you use?

I still dislike that there are a lot of choices that generate redundancy
to other questions.
On the other hand, scientific surveys always contain (hidden) redundancy
to ensure that the test person gives sane answers.

> 59. Should Git User's Survey be repeated next year?
  
>  ( ) Yes
>  ( ) No
>  ( ) no opinion
> Reset

I wonder if the "no opinion" choice is not needed because there is the
"Reset" button.


Apropos!

Is it possible to add a header text?

I'd like that there are three things being clarified at the beginning of
the survey page:

 * The survey is anonymous, but all information that the users provide will
   be publicly available on the wiki.

 * The users may skip questions as they like.

 * The user needs JavaScript to submit the survey.

I btw do not like the last fact, but since most users nowadays have
JavaScript activated, it may not be that bad.

Also, I still do not get a succesful message after submitting, but that
may be related to the channel (test), if you have configured it like
that. Have you? ;)

Regards,
  Stephan

-- 
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F

  parent reply	other threads:[~2008-08-24 21:37 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23  1:25 [RFC] Git User's Survey 2008 Jakub Narebski
2008-07-23  4:39 ` Junio C Hamano
2008-07-23  7:47   ` HP-UX issues (WAS: Re: [RFC] Git User's Survey 2008) Miklos Vajna
2008-07-23 21:38     ` Jakub Narebski
2008-07-23 23:45       ` Miklos Vajna
2008-07-23 11:06   ` [RFC] Git User's Survey 2008 Jakub Narebski
2008-07-24 11:46   ` Marek Zawirski
2008-07-24 12:09     ` Mailing lists, was " Johannes Schindelin
2008-07-25 17:23       ` Shawn O. Pearce
2008-07-25 18:49         ` Junio C Hamano
2008-07-25 21:52           ` Jakub Narebski
2008-07-25 21:57             ` Shawn O. Pearce
2008-07-25 22:11               ` Junio C Hamano
2008-07-25 22:13                 ` Shawn O. Pearce
2008-07-26 10:54                   ` Jakub Narebski
2008-07-26 12:19                     ` Marek Zawirski
2008-07-26 21:50                     ` Shawn O. Pearce
2008-07-26 21:52                       ` Jean-François Veillette
2008-07-25 22:15               ` Petr Baudis
2008-07-26 15:51               ` Jing Xue
2008-07-26 16:47                 ` Jakub Narebski
2008-07-26 17:51                   ` Shawn O. Pearce
2008-07-26 18:17                     ` Jakub Narebski
2008-07-26 19:06                       ` Johannes Schindelin
2008-07-26 18:38                     ` Scott Chacon
2008-07-24 14:07     ` Jakub Narebski
2008-07-23  9:53 ` Johannes Schindelin
2008-07-23 13:08   ` Jakub Narebski
2008-07-23 13:18     ` Johannes Schindelin
2008-07-23 14:54       ` Robin Rosenberg
2008-07-23 16:00         ` Johannes Schindelin
2008-07-24 10:44           ` Jakub Narebski
2008-07-23 23:30         ` Jakub Narebski
2008-07-23 23:33           ` Johannes Schindelin
2008-07-23 23:53           ` Stephan Beyer
2008-07-24  5:02             ` david
2008-07-24  8:57               ` Stephan Beyer
2008-07-24 10:37                 ` david
2008-07-24  9:52             ` Jakub Narebski
2008-07-26 15:34               ` Jakub Narebski
2008-07-27 11:24                 ` Nguyen Thai Ngoc Duy
2008-07-23 16:43     ` Junio C Hamano
2008-07-24  0:10       ` Jakub Narebski
2008-07-23 14:54   ` Dmitry Potapov
2008-07-23 16:02     ` Johannes Schindelin
2008-07-23 17:01     ` Stephan Beyer
2008-07-24  8:24       ` Jakub Narebski
2008-07-23 17:17   ` Alex Riesen
2008-07-24  8:15     ` Jakub Narebski
2008-07-23 14:12 ` Stephan Beyer
2008-07-24 22:22   ` Stephan Beyer
2008-07-23 14:38 ` Dmitry Potapov
2008-07-23 15:43   ` Matthias Kestenholz
2008-07-23 20:09     ` Dmitry Potapov
2008-07-23 21:49   ` Jakub Narebski
2008-07-24 18:08     ` Dmitry Potapov
2008-07-24 21:06       ` Jakub Narebski
2008-07-23 21:44 ` Petr Baudis
2008-07-23 21:59   ` Jakub Narebski
     [not found] ` <169F15EC-1A58-4C2A-84FC-3D14F7B4F1C5@yahoo.ca>
2008-07-23 22:46   ` Miguel Arroz
2008-07-23 23:49   ` Jakub Narebski
2008-07-24 10:11     ` Sverre Rabbelier
2008-07-24 14:45 ` Jon Loeliger
2008-07-24 18:18   ` Jakub Narebski
2008-07-24 18:50     ` Lachele Foley (Lists)
2008-07-24 21:08       ` Jakub Narebski
2008-07-24 17:57 ` Dmitry Potapov
2008-07-24 18:42   ` Jakub Narebski
2008-07-31 12:48 ` Jakub Narebski
2008-08-20  1:08 ` [RFC v2] " Jakub Narebski
2008-08-20 11:34   ` Alex Riesen
2008-08-20 12:04     ` Petr Baudis
2008-08-20 13:50       ` Jakub Narebski
2008-08-20 18:18         ` Alex Riesen
2008-08-20 20:14   ` Junio C Hamano
2008-08-21  1:30     ` Jakub Narebski
2008-08-21  3:10       ` Junio C Hamano
2008-08-21 11:19         ` Jakub Narebski
2008-08-20 21:18   ` Stephan Beyer
2008-08-20 21:26     ` Stephan Beyer
2008-08-21 11:11     ` Jakub Narebski
2008-08-21 21:26       ` Stephan Beyer
2008-08-22  0:06         ` Jakub Narebski
2008-08-21  3:22   ` Mike Gant
2008-08-24 21:36   ` Stephan Beyer [this message]
2008-08-25  0:41     ` Jakub Narebski
     [not found]       ` <20080825012653.GB28160@leksak.fem-net>
2008-08-25  1:56         ` Jakub Narebski
2008-08-20  7:31 ` Abhijit Bhopatkar
2008-08-25 22:08 ` [RFC v3] " Jakub Narebski
2008-08-28  0:28   ` Stephan Beyer
2008-08-30  1:33 ` [RFC v4] Git User's Survey 2008 (cover letters) Jakub Narebski
2008-08-30 19:00   ` Garry Dolley
2008-09-01  7:47   ` Paolo Ciarrocchi

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

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

  git send-email \
    --in-reply-to=20080824213634.GA16753@leksak.fem-net \
    --to=s-beyer@gmx.net \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.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.
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 NNTP newsgroup(s).