> Qualified imports last, even if they're stdlib or framework?

That was my intention, yes. Perhaps splitting qualified into the same three groups, but having them all together after the unqualified ones.

I modified this rule from [here](https://github.com/tibbe/haskell-style-guide) because I dislike mixing qualifieds in with normal imports, I find it hard to parse visually if you don't align them like:

```haskell
import           Data.Text      (Text)
import qualified Data.Text as T
```

And I actually dislike that (hypocrite, I know) because it's *too* wide and sparse.

> s/framework/third party/ ?
>
> stdlib = ghc, or Haskell Platform?

My intention was to be somewhat loose here. I consider Yesod/Persistent to be the second group, and Control.Monad.State to be the first -- even through they both come from packages on hackage. I'm open to attempts to make it more exact, but don't feel its necessary myself.

> When a new version of HP comes out, should we re-arrange our imports?

I would not be in favor of going back to change existing imports for any reason really, even if the ecosystem changes such that code begins breaking this rule. We have an over-arching rule about not changing code just to put it in line with the style guide.