Break out submodules into a separate project

Really excited about the most recent work that's been happening on this project. I'm curious if you'd be amenable to breaking out the API module from the harvest_projects, harvest_status, and harvest_notifications submodules. My thinking is that most organizations are likely to have very different reporting needs and are going to want to get at the data in different ways. You've done a great job at writing helper functions and setting up a framework for getting at Harvest data.

But in our case, we're likely to write our own variation on the harvest_projects module that scratches our own itch. Again, this isn't a criticism - just a difference in workflow.

Separating the core API module would likely make it easier to create an eco-system of submodules (and really distributions) around your work. It's also likely make it easier to maintain the module, accept patches, etc.