Golang project structure in an application versus a package
<p>My organization uses Rails to develop its app but I'm attempting to re-write one of our back-end processes in Golang because it's much quicker. </p>

<p>I've structure my application with our company a namespace for my app (<code>example.co</code>), and a subfolder for each of the packages within my app. </p>

<p>Each library that I've included (e.g. <code>sqlx</code>, etc...) also has it's own folder. </p>

<pre><code>src/
  github.com/
    jmoiron/
      (sqlx package files)
  example.co
    my_app/
      (my app package files)
    model/
      (model package files...)
</code></pre>

<p><a href="https://github.com/jmoiron/sqlx" rel="nofollow">However looking at other packages like sqlx</a>, it appears they scrap this directory structure entirely and put all their files in the root directory</p>

<p>Is this because I'm writing an application and sqlx is a package that's meant to be included in other applications? Or is it just a difference in preference since there's no real accepted "standard"</p>