Live data from Hacker News

Got Hacking? Git Hacking.

githacking.com

11–20 of 48 posts

Re: Got Hacking? Git Hacking.

#11
post #5

I actually spent a longer moment looking for signup form, then I started to think what to input there (email, login, or what).

Thanks. We're updating it right now. It'll be up in a few minutes.

Maybe you can add gray text on input field saying 'enter your email' or something like that, that disappears when input field is clicked?

Re: Got Hacking? Git Hacking.

#12
post #11

Earlier quoted context omitted.

Thanks. We're updating it right now. It'll be up in a few minutes.

Maybe you can add gray text on input field saying 'enter your email' or something like that, that disappears when input field is clicked?

We're on it. Thanks for the help. We're putting it in right now and should be up in a few.

Re: Got Hacking? Git Hacking.

#14
post #3

I like the business model, but what prevents someone from looking at a developer's solution and incorporating it without paying the developer? Say the company is charged when they use the patching mechanism to bring developer's work into their product. What would stop them from simply going around this mechanism and just copy and paste the solution into their own repository? Also is the developer responsible for fixi…

>What would stop them from simply going around this mechanism and just copy and paste the solution into their own repository?

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.

Re: Got Hacking? Git Hacking.

#15

This seems like a cool idea. You might want to check with a lawyer about the logo up top though, thats definitely GitHub's octocat hiding behind Apple's Terminal.app logo.

Yeah, working on that too. Our creative juices started to run dry after the weekend sprint. We'll refresh that in the coming days.

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

Re: Got Hacking? Git Hacking.

#16

Great idea! 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.

Hi. We're Chris (@chrisbaglieri), John (@codingjester), Josiah (@bluepojo), and Aaron (@aaronfeng). This company was born over the course of 54 hours at Philadelphia Startup Weekend.

The emails will be used once and only once, to announce when we're open to the public.

Re: Got Hacking? Git Hacking.

#17

Great idea! 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.

Hi. We're Chris (@chrisbaglieri), John (@codingjester), Josiah (@bluepojo), and Aaron (@aaronfeng). This company was born over the course of 54 hours at Philadelphia Startup Weekend. The emails will be used once and only once, to announce when we're open to the public.

Thank you. Perhaps add that to the site and you'll give off a lot more "warm and fuzzies."

Re: Got Hacking? Git Hacking.

#18

This seems like a cool idea. You might want to check with a lawyer about the logo up top though, thats definitely GitHub's octocat hiding behind Apple's Terminal.app logo.

No need to consult a lawyer, just open an issue at http://support.github.com and ask if it's okay.

Re: Got Hacking? Git Hacking.

#19

Earlier quoted context omitted.

Hi. We're Chris (@chrisbaglieri), John (@codingjester), Josiah (@bluepojo), and Aaron (@aaronfeng). This company was born over the course of 54 hours at Philadelphia Startup Weekend. The emails will be used once and only once, to announce when we're open to the public.

Thank you. Perhaps add that to the site and you'll give off a lot more "warm and fuzzies."

Added a quick note about only using emails once and only once. We'll add an about page in the coming day profiling each of us.

Re: Got Hacking? Git Hacking.

#20

Earlier quoted context omitted.

Yeah, working on that too. Our creative juices started to run dry after the weekend sprint. We'll refresh that in the coming days.

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.
Post reply on HN