From: Jakub Narebski <jnareb@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC] Git User's Survey 2007
Date: Mon, 30 Jul 2007 15:40:55 +0200 [thread overview]
Message-ID: <200707301540.56401.jnareb@gmail.com> (raw)
In-Reply-To: <20070730033543.GP20052@spearce.org>
Shawn O. Pearce wrote:
> Jakub Narebski <jnareb@gmail.com> wrote:
>> Paolo Ciarrocchi wrote:
>>> git-gui ?
>>>
>>>> 9. Which git GUI do you use
>>>> (zero or more: multiple choice)
>>>> - gitk, git-gui, qgit, gitview, giggle, other
>> tig, instaweb, (h)gct, qct, KGit
>>
>> I consider git-gui an UI (like qgit or tig), not a porcelain. To be
>> a porcelains tool need to add some SCM functionality not present in
>> git-core.
>
> Odd. I consider git-gui to be a porcelain, just as I consider
> tig and qgit to also be porcelain. Though I think git-gui is more
> of a porcelain than the others, as it tries to rely *less* on the
> core porcelain and just on the plumbing. I don't always succeed,
> but I'm heading in that direction.
>
> To me a porcelain is any tool that layers over the plumbing and makes
> it easier for the end-user to operate it. Early git only had things
> like read-tree/write-tree/commit-tree. Tying that all up into a neat
> "Commit" command for the end-user is the job of porcelain.
>
> Anyway. Just so long as git-gui is included in the survey. I'm
> interested in seeing how many people use it, because I know it has
> a pretty decently sized userbase. Which is probably going to grow
> in the future with the i18n work going on.
Well, if we use the notion that porcelain are tools which provide
high level access to core git, making SCM from git plumbing, then
being porcelain and being git UI are not mutually exclusive.
Nevertheless I'd rather keep them separate, and put git-gui in UI
camp, while egit (which I have forgot about) in the porcelain camp.
Or should I use "version control interface layers" instead of
"porcelains"?
> Do we have any questions in the survey about the user's native
> language? About their desire to have git translated into their
> native language? Folks are now working on translating git-gui,
> and that work will be in git-gui 0.9.x, if not 0.8.1/2. So it may
> be nice to know what languages our users are interested in.
----
About you
1. What country are you in?
2. What is your preferred non-programming language?
[...]
Internationalization
1. Is translating GIT required for wider adoption?
- yes/no/somewhat
2. What do you need translated?
(zero or more: multiple choice)
- GUI (git-gui, gitk, qgit, ...), git-core messages,
manpages, other documentation
3. For what language do you need translation for?
----
Do you want other questions about internationalization and translating
git into one's native language?
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-07-30 21:18 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 1:58 Git User's Survey 2007 Jakub Narebski
2007-07-25 16:19 ` Marco Costalba
2007-07-26 4:52 ` Steven Grimm
2007-07-27 11:20 ` [RFC] " Jakub Narebski
2007-07-27 12:21 ` Nguyen Thai Ngoc Duy
2007-07-27 13:01 ` Andy Parkins
2007-07-27 19:07 ` Jakub Narebski
2007-07-28 8:02 ` Andy Parkins
2007-07-29 16:50 ` Paolo Ciarrocchi
2007-07-29 17:05 ` Paolo Ciarrocchi
2007-07-30 0:21 ` Jakub Narebski
2007-07-30 3:35 ` Shawn O. Pearce
2007-07-30 13:40 ` Jakub Narebski [this message]
2007-07-30 7:44 ` Paolo Ciarrocchi
2007-07-30 13:26 ` Jakub Narebski
2007-07-30 19:26 ` David Kastrup
2007-07-30 21:12 ` Junio C Hamano
2007-07-30 21:37 ` Jakub Narebski
2007-07-30 22:38 ` David Kastrup
2007-07-30 21:25 ` Nguyen Thai Ngoc Duy
2007-07-30 21:35 ` Jakub Narebski
2007-07-30 20:56 ` [RFC (take 2) " Jakub Narebski
2007-07-31 0:32 ` Shawn O. Pearce
2007-07-31 0:45 ` Jakub Narebski
2007-07-31 1:09 ` Shawn O. Pearce
2007-07-31 1:24 ` Junio C Hamano
2007-07-31 1:31 ` Shawn O. Pearce
2007-07-31 11:22 ` Jakub Narebski
2007-07-31 11:33 ` Paolo Ciarrocchi
2007-07-31 12:30 ` Jakub Narebski
2007-07-31 16:35 ` Git User's Survey 2007 - web survey site Jakub Narebski
2007-07-31 19:07 ` Paolo Ciarrocchi
2007-08-02 4:51 ` Martin Langhoff
2007-08-02 13:04 ` Paolo Ciarrocchi
2007-08-04 0:50 ` [RFC (take 3)] Git User's Survey 2007 Jakub Narebski
2007-08-04 5:41 ` Shawn O. Pearce
2007-08-04 12:10 ` Jakub Narebski
2007-08-04 7:40 ` David Kastrup
2007-08-05 20:06 ` Jakub Narebski
2007-08-06 0:29 ` Johannes Schindelin
2007-08-05 9:30 ` Asger Ottar Alstrup
2007-08-06 1:17 ` Jakub Narebski
2007-08-06 5:48 ` Asger Ottar Alstrup
2007-08-06 15:44 ` Jakub Narebski
2007-08-05 20:51 ` [RFC (take 4)] " Jakub Narebski
2007-08-14 1:51 ` [RFC (final)] " Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2007-08-14 22:38 [RFC} " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200707301540.56401.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.com \
--cc=spearce@spearce.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).