First/origo makes more sense to me than 'main' following that logic. I've seen plenty of projects where the 'main'/'mainline'/'master' isn't actually where any

First/origo makes more sense to me than 'main' following that logic. I've seen plenty of projects where the 'main'/'mainline'/'master' isn't actually where any development is done or any code deployed from. Other branches originate from them, but the focus of the developers is in other parts of the tree. That's also why I think 'trunk' is a good name. It describes the positional relationship that part of the tree has to other parts, without ascribing any organizational importance to it. I don't think 'first' is ideal though, since that has a temporal component and would be better applied to the root commit.