On 2012.7.24 7:55 PM, Eric Wong wrote:
>> After I'm exhausted from volunteering all the coding work, rather than
>> submitting a URL to a remote repository I find I have to learn new
>> tools. It's extra learning and work, an extra step to screw up, and foreign
>> to me (even as a experienced git user). It is of little benefit to me as a
>> casual volunteer submitter.
> Except git is also a "new specialized tool". Your examples are exactly
> why I'm saddened many projects only adopted git, but not the workflow
> which _built_ git (and Linux).
There is an important difference between a tool which is useful for one or two
projects and one which is useful for a broad spectrum of projects. I learn
git once (or diff or bash or Perl or whatever) and I'm going to use it again
and again all over the place. I learn git-send-email and (if I'm not a kernel
developer) I'm going to use it on a handful of projects maybe. It's O(1) vs
Github also has broad spectrum utility. I learn how to fork and work with a
Github pull request once, and I can repeat that on thousands of different
projects of all different sorts of things.
This commonality of tools and techniques is very important to easing the on
ramp for new (to-your-project) developers.
>> I can see if you've been on the git mailing list for a while and have git-am
>> and all that set up, this system is great. But it comes at a cost which is
>> offloaded onto new and casual contributors.
> Email is integral to Free/Open Source development and remains one of the
> few things on the Internet not (yet) controlled by any central entity.
> Once setup, the same email setup can work across all projects which use
> email. These projects need not be hosted on the same websites/servers
> at all.
While I hear your concern about being centrally controlled, it is largely
irrelevant to the new user experience. And remaining independent does not
mean you can't use web tools. Be wary of a false dichotomy between Free and
"We use a mailing list" is by no means an indication of commonality. Every
project of the "send patches to the list" form has their own quirks and ways
of doing it. Usually they're not written down. This is what I've been
struggling with. I've been sending patches to mailing lists for decades and I
can tell you everybody does it differently. "Send a patch to the list" is one
of the steeper project on-ramps.
>> This sort of specialized setup makes people bounce right off the submission
>> process. At OSCON I was asking around for help getting things setup so I
>> could submit patches here properly. As soon as they said "which mail daemon
>> are you running?", I said "stop! I don't want to know any more". I have too
>> many things to do to be fiddling with my mailer configuration just to submit
>> volunteer work in the right form (that said, I'm pleased as punch that
>> git-send-email now has instructions for sending via GMail). You're
>> volunteers, too. We're all volunteers, so a more balanced submission process
>> would be nice.
> How about we educate users about a proper email setup instead? If
> they're capable of learning git, they're surely capable of setting up an
> email client properly, and perhaps more projects can adopt an
> email-centric workflow.
SubmittingPatches would be helped by that, particularly with a clear
step-by-step example of using git-send-email and all its numerous command line
I was showing Jonathan the guide I have for releasing Perl modules which is
both A) step-by-step and also B) covers the numerous little problems that are
usually only in somebody's head or scattered around the docs. It was built in
order to allow a person who had never released a module to release a module.
Then we watched just such a person follow the directions. As they asked
questions, struggled or made mistakes we filled in the gaps in the docs.
But this is also not about capability. Yes, people are capable of figuring
out git-send-email, but its Yet Another Special Thing to learn before they can
submit a patch and call their work done. Volunteers, especially brand new
ones, have only so much volunteerism to burn before they'll walk away. You
want them burning that on productive patching and contributions, not learning
And, finally, the last thing most people want is more email. Seriously. It
sounds like you live in your mailer, but fewer and fewer people do that. Me?
I don't want to join another mailing list. My email management is a disaster!
What it comes down to is this: is it enough to contribute to git.git to know
how to work on git.git? Or do you also need to live in your mailer? Bolt on
that extra requirement and you lose a large swath of contributors.
>> But since you brought Github up... (I get the impression its kind of a dirty
>> word around here)
> (Not speaking for the git project) I'm entirely against the way GitHub
> (or Ohloh or similar services) gamifies software development and tries
> to tie a person to all their other projects.
> Much of my code is public, but I am a private person. I want code to be
> judged solely on its own merits of that code; not from what the author's
> achieved or how "popular" the person might be in the development world.
> Unfortunately, GitHub (and other social networks) is structured to
> encourage that sort of thing (which I know is appealing to many).
FWIW this aspect of Github is just a toy. For some people it acts as a
carrot, but nobody worth caring about takes it seriously. I wouldn't get too
worked up about it.
> For me, the whole social network followers/timeline thing also has a
> _huge_ creepiness factor to it. How one prioritizes and spends time
> between different different (especially unrelated) projects should be
> nobody else's business.
> I don't make it /easy/ for someone (e.g. Junio) to know I'm slacking
> off on my git work to hack on ProjectNoOneUses :)
> One could try using a different account for every project, but that's
> also violating the terms of service.
You want to know what's creepy? That you'd think people work like that.
It doesn't work out that way. People have far better things to do than stalk
your Github commits to see how you're spending your time. You're just not
that interesting. Neither am I!
(If I really wanted to I could just compile your activity from public list
archives and repositories, so you're really not broadcasting any less
information about yourself by staying off Github. But I wouldn't want to,
because you're just not that interesting and I have better things to do with
Besides, Facebook is where all the stalking is at! ;)
>> If all the clicking and opening tabs in a browser feels uncomfortable to
>> you... its something you learn like anything else. Less and less people are
>> comfortable in mail clients. Who is the system optimized for? It doesn't
>> have to be a zero sum game.
> (Still not speaking for others) I believe GUIs are (mostly) harmful.
You can hate GUIs, but you should also realize that just about everyone out
there likes them, and they're not all morons. If you deny GUIs as a tool for
git.git developers because of your blind spot, then you're losing potential
contributors. More and more as time goes on.
Recognize it as a personal blind spot, don't punish your users because of it.
Me? I hate IDEs. Won't touch em. Do I really think emacs or vim are
superior and all those IDE users are deluded? HELL NO! I think I'm ignorant
and don't understand IDEs. I really don't know anything about them. I don't
even know what I don't know. I generally keep my mouth shut and listen rather
than blab a bunch of old guy ignorance.
> Graphical browsers don't interact well with command-line tools.
> Browsers have no concept of a working directory; I can't fire up a
> browser tab/window for each project I work on and edit/apply patches
> directly from the browser like I can with an MUA.
I'm not sure what you're talking about, or what sort of workflow you've got
going with your mailer, but I'm sure with just as much time and effort as
you've put into your CLI and MUA setup you can be just as efficient or moreso
writing or using an add-on. But also, one doesn't have to do EVERYTHING with
a single tool. Amazing But True!
You should consider sitting down with somebody who works very differently from
how you do and see how they do it. You might learn something you don't know
you don't know!
And again, it *does not have to be zero sum*. It doesn't have to be email VS
GUI. You can have your cake and eat it too.
125. Two drink limit does not mean two kinds of drinks.
-- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html