If you aren't a C coder, you can help to improve the documentation (really, just pick a man page, there are many that can use improving). Or, look at it as an opportunity to learn C -- some parts of git are quite advanced, but there's also lots of areas that are easy to work on.
See the git wiki for some areas that can use love:
(Sadly the wiki is down right now, so please paste those links into google and click the cached link.)
So go on, get yourself listed on http://git-scm.com/about
Even the summaries are terrible:
git-fetch - Download objects and refs from another repository
git-push - Update remote refs along with associated objects
Now, I haven't been a git newbie in ages, but I imagine a beginner asking "what is this objects and refs about?" How about:
git-fetch - Download changes from another repository
git-push - Upload changes to another repository
(Warning: there will be lots of back-and-forth on the mailing list about doc changes. Old timers tend to want the man pages to be technically correct, even though I think this makes the documentation harder on beginners. I suppose the argument is that the man pages are reference type documentation, but I still think there's lots of room for improvement.)
I forget where I read this, but it was someone asking the same thing. I might have been on HN, actually.
it would be a nice way of everybody having a common "icon", much like twitter has the bird.
I know people can link to github, but that's not always possible (mobile apps?) even though people use github..
I think a good solution would be a new open license logo, like the Minefield logo as opposed to the restricted Firefox logo.
We'll get on that ASAP. Nothin' but love.
I love the idea. A couple of months ago I created gistcube, It was a weekend project to learn a bit about Mongodb and Sinatra. Gistcube is a way to discover interesting gist in github. You can vote up, add to favorites, tag gists, and alos sign up to interesting/tags gist using rss.
(1, MALWARE, Phishing, Domain has unusually high traffic volume for a very recent registration. Identified as a phishing or spam-related site., BLOCK-MALWARE, 0x0b216460, 1296449561.941, QAAAAQAAAAAAAAAAG/8ACP8AAAD/AAAAAAAAAAAAAAA=, http://githacking.com/)
Also is the developer responsible for fixing bugs in their solution? Can a developer exploit the process by submitting buggy code they'll be paid extra to fix? Can a developer be required to fix bugs in their solution?
If a company can't inspect code before they pay they can't be certain it's relatively bug free, if they can inspect the code they could use it without paying for it easily.
They could have a reputation system somewhat like that on Mechanical Turk:
* You only pay someone if you like their solution.
* People working on tasks get reputation for how well they are doing.
* People offering tasks get reputation for how many people they are paying.
Where is my e-mail going? What are you planning to do with it?
Also, there is no identification on who is running the project.
The emails will be used once and only once, to announce when we're open to the public.
For maintainers, we're about finding developers to fill the needs of their projects. Open sourcing is step one, promoting and keeping traction can be tough. We want to arm maintainers with more to help accomplish this.
For businesses that rely on the open source code contributors and maintainers support, we want to provide a platform that they can leverage whether it's support or issue resolution. Businesses win because they get fixes, for example. Maintainers and contributors win being rewarded for their efforts.
We have several other ideas we're exploring; lot's more to come.