Hi, Jakub, thank you very much for doing this. It is a very tedious work, and I deem it invaluable. On Sat, 13 Oct 2007, Jakub Narebski wrote: > * IRC is blocked from work :-( I may try it by tunneling out. > > (Any suggestions here?) I had the same problem, and somebody pointed me to http://ircatwork.com/cgi-bin/irc/irc.cgi (But please be nice, or else it will be shut down...) > * Keep up the UI simplification and make sure the docs start off with > usage somewhat similar to CVS/SVN. I think many users are scared by > Git because they see the more powerful commands thrown around too > early and get scared. > > Git is just too complicated for a typical project. I understand > it's probably great for the Linux kernel but for a smaller project > like mine (Mesa) it's overkill and a frustration. (...) With git > everything seems hard. (...) I've _wasted_ hours trying to figure > out git. That alone is a huge issue. I guess I could go into > specific details about my problems with git but I've already spent > enough time on this survey. I find it always a little strange how people want to use something like git, but are unwilling to ask. Is this such a big attack on the manliness to admist one needs help or what? > Figure out why people find git hard to learn and eliminate those > barriers to entry. Make git more task-oriented rather than > data-model-oriented the way it is now. Frankly, expectations like these make me want to bang somebody's head on the wall. Why do people expect others to work for them for free? Hard? > (...) I'm evaluating Mercurial despite its being based on Python > because it feels cleaner and simpler to use. I would prefer to use > Git. You cannot do much about feelings, not with technical means, you can't. > * No one-pager cheat sheet with the 6 most basic commands on it so > people can go use git. > > (This got corrected. There is git cheat sheet on the Internet; > there is link on GitWiki to it) I think it'd be a good idea to put it on git://git.kernel.org/, linked right before the links to the man pages. Who has permissions to change that page? > I'd like to just stress support for windows and central > repositories. (...) In fact most of my friends really wanted to use > git but they wanted a solid native port. If you read what I wrote above, you know exactly what I want to do here. > * Get a mascot perhaps O'Reilly animal for O'Reilly GitBook > (Git User's Manual) like the svnbook. > > (What animal could Git use for O'Reilly? Herd of horses, or a > pony?) OMG Ponies! Seriously again, is the cheetah taken already? Speaking of cheetah: there is a project called git-cheetah, its goal being to provide a TortoiseCVS lookalike for git. Just wanted to mention it, in case people want it, and are not too shy to participate in making it closer to the goal. > * I'm wondering what the overall goal is - git's origin as a neutral > ground was fine but it hasn't seemed to take off as a viable > alternative for general use. Do you care about that? Is it ok > that git is it's own little niche? > > (Junio, Linus?) I am neither, but FWIW I did not have the impression that it is in its own little niche. At the GSoC mentor summit, I encountered a rather different stance: people did not _know_ what distributed SCM means, and were rather afraid of the concept. Some of them seemed to fight changing their known procedures tooth and nail. Which is fine by me (I don't have to force anybody to use git, thankyouverymuch). A word about the GitFAQ... there was one suggestion that there should be a FAQ maintainer. I really have to ask myself why not more people just edit the GitFAQ on the wiki. I mean, that is the whole purpose of it being on the wiki. It's not hard either. Less hard in any case than to find a volunteer for a FAQ maintainer -- I mean, if most are too busy/lazy/shy to edit the FAQ at all, how do they expect somebody else to step up? Ciao, Dscho - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
