Comment by jamesgeck0 | Hacker News Reader

Comment by jamesgeck0 | Hacker News Reader

Parent Full thread

> The Challenge

> Take an existing game or game jam entry on GitHub, fork it and do something awesome with it.

> Take a look at the following resources to see if there's one you'd be intersted in forking....

> Once you've found a game repository, fork it...

> Make sure your code is pushed to the default branch of your forked repository...

And, on the submission form, talking about your Readme file:

> Mention the Game Off, what changes you made, who was on your team, what technologies you used, throw in a screenshot, etc.

I dunno, all that seems pretty explicit to me.

I would call that very suggestive, not explicit.

  > Take an existing game or game jam entry on GitHub, fork it and do something awesome with it.

Consider the edge cases:

What if you can't fork it because you've already forked it 5 months ago (but made 0 commits on your fork)? This is probably okay, right? If not, you could delete your existing fork and fork again.

What if you can't fork it because you have an unrelated repo with the exact same name already? This is also okay, right?

What if you can't fork it because it's your own repo and you don't need to fork it? This is not okay? Or is it okay? No clear answer.

There are times where it helps to have explicit rules/conditions.

Dude, it's not like there is major prize money involved.

This is just a "just for fun, do something cool by forking something that already exists and we'll show off the best."

Relax, have fun, make a cool game.

Reply on news.ycombinator.com