search

iTrace-Dev / iTrace

Infrastructure supporting implicit eye tracking on software artifacts within the IDE and browser.
http://www.i-trace.org
2 stars 0 forks source link

separate iTrace core repo from iTrace Eclipse plugin #96

Closed shbonita closed 7 years ago

shbonita commented 7 years ago

To keep things modular, we decided to have separate repos for each major product. This means we should separate the iTrace core from the plugins.

After the engine is complete enough to be usable, here are couple of options to do the above.

  1. Leave iTrace repo as is as legacy. Create a new repo iTraceCore for engine stuff. Create a new repo iTraceEclipse for Eclipse plugin stuff. Preseve history into new repos.
  2. make the current iTrace repo the engine and pull out Eclipse plugin parts to new repo iTraceEclipse

I am leaning towards 1. I'd like your feedback. Comment on pros and cons for each.

mjdecker commented 7 years ago

You could also do 1 and make it a super-repository. The other repos would be submodules. That way if someone wants everything, they can do a recursive clone on the super-repository. boost does something similar.

shbonita commented 7 years ago

The separation has been made. Closing issue.