Live data from Hacker News

Got Hacking? Git Hacking.

githacking.com

31–40 of 48 posts

Re: Got Hacking? Git Hacking.

#31
post #29
post #25

Earlier quoted context omitted.

GitHub now owns the octocat art.

You guys should seriously think about allowing other projects to use the octocat when the projects are associated to github. 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..

Twitter previously used some stock bird art, but the logo was just the bubble letters. Now they have an original bird logo. But 3rd party Twitter stuff can use arbitrary bird art, or maybe the old stock one since it's unclear who owns it.

I think a good solution would be a new open license logo, like the Minefield logo as opposed to the restricted Firefox logo.

Re: Got Hacking? Git Hacking.

#32
post #20

Earlier quoted context omitted.

Might want to make that sooner than just "in the coming days."

One thing I've learned from reading HN over the years: Few things kill the buzz of a new site like the introduction of legal/copyright issues.

I don't see the big deal; it's cosmetic. The logo's easy to remove. I can't imagine significant damages. Legal issues are only a problem when the content is infringing, such as video uploads.

Re: Got Hacking? Git Hacking.

#33

Congrats for a great startup weekend. I love the idea. A couple of months ago I created gistcube[1], 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] http://gistcube.com

Cool drop shadow.

Re: Got Hacking? Git Hacking.

#35
This is neat, i intend to use it. I've been thinking recently it would be great if there was "OkCupid for code" and once you have enough data to predict good matches for people projects you could do some interesting things.

Re: Got Hacking? Git Hacking.

#36
post #32
post #20

Earlier quoted context omitted.

One thing I've learned from reading HN over the years: Few things kill the buzz of a new site like the introduction of legal/copyright issues.

I don't see the big deal; it's cosmetic. The logo's easy to remove. I can't imagine significant damages. Legal issues are only a problem when the content is infringing, such as video uploads.

I agree, it shouldn't overshadow other stuff. But that's the odd thing about those kinds of issues -- they tend to overshadow the work anyway.

Re: Got Hacking? Git Hacking.

#37
post #30
post #28

I would like to suggest that folks consider working on git itself. The git mailing list is very friendly and supportive and you will be making a valuable contribution to the git community. You'll also have an opportunity to brush up your C skills with guidance from some excellent C hackers. 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 im…

Thank you for this-- just the reply I was looking for. Out of curiosity, which man pages need the most work right now?

How about the fetch and push man pages:

http://www.kernel.org/pub/software/scm/git/docs/git-fetch.ht...

http://www.kernel.org/pub/software/scm/git/docs/git-push.htm...

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.)

Re: Got Hacking? Git Hacking.

#38
that page is purdy but it really should explain what it's about. what's the plan. all i can tell is that it involves Git and they want an email. to be more specific: what is it beyond what we already have today with something like GitHub?

Re: Got Hacking? Git Hacking.

#39

that page is purdy but it really should explain what it's about. what's the plan. all i can tell is that it involves Git and they want an email. to be more specific: what is it beyond what we already have today with something like GitHub?

For developers, we're about connecting them to projects that they'll likely be interested in contributing to; these projects may or may not be most forked or trending. A lot of repository identification is word of mouth which, for those on on the outer rings of the open source community, may be lacking. We want to change that.

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.

Post reply on HN