Use filter rather than filter_by, just for consistency
Document the path property
Add a fullname property that renders forks project differently

Projects will render as <project name> while forks render as <user>/<project name>

This is used in the repo_info template.
Add a fork property providing a boolean to check if the project is a fork or not
Add relation in the model between the project table and itself to model forks

If the project is a fork we are interested in accessing its parent
Change the repo info view to rely on the fullname property
If the repo is a fork display the name of its parent in the repo info view
When retrieving a project, only retrieve forks if a user is specified
Exclude forks from the list of projects in the front page
Fix the fullname and fork properties, they were just the opposite of what they should be
Fix the parent relation so that we actully access the parent repo
Fix the link to the parent repo
Update the fork controller to retrieve the info from the DB rather than the filesystem
Forward the repo object to the repo info view