Yes, I'd like a package name with no project name in it for this class. If you're using Eclipse or something equally capable you might be able to pull off the move in the package view with no typing atoll. I'm able to open all my projects at once and do things like this with great ease.
Robert Martin suggests the package is a
unit of deployment. You could shrink wrap it, deploy a single changed package to various clients, etc. We've debated this at length in the forum and there are certainly other ways to bundle your code. But it might be a helpful way to think about this and would encourage moving it out of any project package.
Let us know what you wind up doing!