search

cms-dev / isolate

Sandbox for securly executing untrusted programs - DEPRECATED, use: https://github.com/ioi/isolate
47 stars 14 forks source link

Which one is the actual project upstream? #24

Closed seirl closed 8 years ago

seirl commented 8 years ago

Is it https://github.com/cms-dev/isolate or https://github.com/ioi/isolate? Where should we submit patches and issues? Shouldn't the other repository disable issue creation and redirect to the other projects?

gollux commented 8 years ago

ioi/isolate is the upstream repository, please submit patches and issues there, except possibly for issues related to the interaction between CMS and Isolate.

stefano-maggiolo commented 8 years ago

Confirmed, we recently moved to tracking ioi/isolate. We should probably change the readme to reflect this.

giomasce commented 8 years ago

The README already appears to point to ioi/isolate. cms-dev/isolate is meant to be a fork with just the small modifications required to integrate isolate with CMS. However issues remain active on cms-dev/isolate, becuase there might be the need to track something related to the CMS fork of isolate. On the other hand, most of isolate issues open at the moment on cms-dev/isolate were just submitted before ioi/isolate existed. They should be migrated (if applicable) or closed (if they're not relevant anymore), but I'm not sure of when I will have time to do it.