Git puns

[travisby]

We need to figure out what game mechanics we're going to use for various git/github features.

• branching
• commits
• tags
• pull requests
• rebasing?

---

• stash -- inventory

[travisby]

Commits I think definitely need to be something similar to saving (or checkpoints). Maybe checkpoints, so tags can be legitimate saving then.

[travisby]

git stash -- inventory

[travisby]

As per meeting 11/3/2012:

git merge -- end level, and move to door git checkout -- if not predecessor, start building a new structure -- if predecessor, player begins at preceding point -- predecessor must exist when checking out ancestor git stash {,apply} -- inventory git commit -- save full structure, randomly produces bugs git stash -- save inventory

[travisby]

Note: forking exists for others' solutions to levels, but that's a later feature

[travisby]

-- actually hosted on github, as some kind of serialized data --

[travisby]

I would suggest yaml, as opposed to JSON or XML for serializing.

http://www.yaml.org/ [note, yaml's website is valid yaml. Pretty damn readable!]

[travisby]

Not exactly a git pun, but see #3 and @trescenzi on GOTOs

If we want we can correlate things to CS concepts behind the senes for bug creations.
 Like those pesky teleporters(GoTos) boy do they have a tendency to create a ton of bugs. 
I think that something like that, saying that the teleporters are still experimental and are prone to be dangerous,
 makes more sense to everyone than saying place a goto here to teleport.