git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Questions for "Git User's Survey 2011"
Date: Tue, 2 Aug 2011 15:37:51 +0200	[thread overview]
Message-ID: <201108021537.51651.jnareb@gmail.com> (raw)
In-Reply-To: <CAMP44s2CWvzKyBAskVRq6Vte-CyCKwxBCZbSw_mbp=4a6ngCOw@mail.gmail.com>

On Sun, 31 Jul 2011, Felipe Contreras wrote:
> 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.
> 
> > === 16. Which of the following Git features do you use? ===
> > (multiple choice, with other)
[...]
> >  + interactive commit / per-hunk comitting / partial commit
[...]
> >  + 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)

Well, it is there... sort of.  I can certainly extend this answer. 
 
> > === 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?

I think I'll keep what we used before.
 
> > === 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?

Portability, certainly.

IDE integration is a bit out of scope, as it is not strictly about Git
itself, but about Git "ecosystem".

As I wrote in separate email, I am thinking about adding a new question:

  21. In your opinion, what Git tools are needed, and which need improvements?
 
> > == 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).

They are not git hosting sites ;-)

Anyway, on Google+ there are 36 people who have me in their circles,
I have 28 followers on Twitter.  Identi.ca, Plurk, Facebook - here
I don't have or almost don't have "friends"/"subscribers"/"fans".

That's not much, so please: forward / share.
 
> > 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 :)

Thanks in advance.
 
> > 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.

Thanks in advance, again.

-- 
Jakub Narebski
Poland

  reply	other threads:[~2011-08-02 13:38 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 20:33 [RFC] Questions for "Git User's Survey 2011" Jakub Narebski
2011-07-25 21:58 ` Phil Hord
2011-07-26 10:37   ` Jakub Narebski
2011-07-26 12:14     ` Phil Hord
2011-07-31 13:37       ` Felipe Contreras
2011-08-01 20:57         ` Jakub Narebski
2011-09-03  8:45   ` David Aguilar
2011-09-03  9:00     ` Jakub Narebski
2011-09-03 23:41       ` David Aguilar
2011-07-31 13:53 ` Felipe Contreras
2011-08-02 13:37   ` Jakub Narebski [this message]
2011-08-01 23:43 ` Heiko Voigt
2011-08-02 11:41   ` Jakub Narebski
2011-08-02 18:52 ` Jens Lehmann
2011-08-03 11:27   ` Jakub Narebski
2011-08-03 16:40 ` Ævar Arnfjörð Bjarmason
2011-08-03 17:40   ` Jakub Narębski
2011-09-03 12:58 ` Felipe Contreras
2011-09-03 15:38   ` Jakub Narebski
2011-09-14 16:14     ` Felipe Contreras
2011-09-14 17:39       ` Jakub Narebski
2012-09-19 17:35         ` Felipe Contreras
2012-09-22 22:45           ` Jakub Narębski
2012-09-23  8:09             ` Junio C Hamano
2012-09-23  9:47               ` Jakub Narębski
2012-09-24 13:23             ` Michael J Gruber
2012-09-24 14:31               ` Jakub Narębski
2012-09-24 15:37             ` Matthieu Moy
2012-09-24 16:11               ` Jakub Narębski
2012-09-24 16:18                 ` Matthieu Moy
2012-09-24 16:23                   ` Jakub Narębski
2012-09-24 19:35                     ` Matthieu Moy
2012-09-24 19:43                       ` Jakub Narębski
2012-09-25  6:17                         ` Matthieu Moy
     [not found]                           ` <CANQwDweD-OSDKkA9P1FPr4jhvv2su5W86J+P8BRV8MmEBgC8BA@mail.gmail.com>
2012-09-25  6:57                             ` 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

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

  git send-email \
    --in-reply-to=201108021537.51651.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --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.
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).