Merge, create different project or something else?

[dfarrell07]

I don't want this to turn into a hostile fork. It has already been unmerge from the main project longer than I'd like. Let's figure out what to do with it.

As I see it, we have at least three options:

1. Submit a pull request, merge it back in to Exadler/DMCC_Library.
2. Split the PyDMCC part out into a different project, nuke the C code here, let the main project host that.
3. As a variation of 2, do that process and then transfer ownership of the Python project back to Exadler.

Thoughts, community? @jschornick, @napratin?

I lean towards 2 over 1, as I think it creates a more sensible repo structure. If you want the C code, pull Exadler/DMCC_Library. If you want Python code, pull NCSUHardware/DMCC_Library (which we may rename to NCSUHardware/PyDMCC). The only reason I suggested 3 was because @jschornick mentioned it briefly last weekend. I'm not really sure what utility it would provide.