You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Submit a pull request, merge it back in to Exadler/DMCC_Library.
Split the PyDMCC part out into a different project, nuke the C code here, let the main project host that.
As a variation of 2, do that process and then transfer ownership of the Python project back to Exadler.
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: