I dunno, I associate "trunk" very strongly with svn.

My company's internal repos usually use "devel" as our default branch, but that's partly a convention inherited from the ROS ecosystem where the different main releases have a codename and fixes get patched between branches with names like jade-devel, kinetic-devel, lunar-devel, etc.

I don't like devel, because its usually coupled with git flow and stale release branches.

I hear trunk and think telephony. SVN was always odd in going with the tree metaphor, as trees never really grow back into themselves normally.

To be fair, branching in svn is kind of a one-way street. A functional merge and conflict resolution workflow was part of what won over a lot of us to git from it.