After reading the thread I can kind of see why both sides have a good argument.<p>The provider of the repo seems to have created this as an opinionated way to lay out a Golang project, so that if you're new to golang you can skip some yakshaving over how to set up your directories.<p>Russ's issue seems to be that this is describing itself as _the standard way to lay out a Golang project_, which it shouldn't.<p>Most of the commenters seem to think changing the name would resolve this issue, and I'm inclined to agree. Opinionated frameworks aren't really a new thing, and while this isn't a framework per se, it's definitely opinionated.
Well, at least now I am aware of that this is not an official standard and most people think that it is more harmful than helpful.<p>This post and the related issue should be spead widely under the go community, so that at least everyone is aware of that.<p>Thank you for sharing.