status of AMUSE-dstributed repo

[ipelupessy]

the current source in AMUSE is out of sync and more up to date then the NLeSc repo - the current situation with both (in tree and seperate repo) is not so nice, so either we should
1 drop the NleSc repo, make the code part of AMUSE only (ie delete the update target)
2 drop the AMUSE code, have it a downloadable code from the NLeSc repo
3 combine 1+2: drop the AMUSE code, have it a downloadable code but move the code to a seperate repo as part of the amuse project (so under amusecode)

[nielsdrost]

I vote 1 :-)

[ipelupessy]

I have disabled the update in the AMUSE distributed makefile - maybe you can put a warning in the readme of the repo?

[nielsdrost]

Notice put in repo. We will probably remove this repo at some point.

[ipelupessy]

ok, thanks!! i am still not sure whether to have a seperate repo (as part of amuse)...there may be more codes/ parts that will be seperated (like omuse is now)....also, there are still a few issues on the repo - I guess they are not going to be resolved anytime soon;-) it may be worthwhile to preserve/ document these...

[nielsdrost]

I can also transfer the repo to amusecode if you like. There is already a fork there however, so this may complicate matters.

[ipelupessy]

ok, didn't realize you could do that..

[ipelupessy]

I have removedthe fork..

[nielsdrost]

Great! Last think I need for a transfer is the (temporary) ability to create repo's on github.com/amusecode.

[ipelupessy]

it may work now..

[nielsdrost]

It did :-) Case closed :-)

[ipelupessy]

ok, nice..thanks!

[nielsdrost]

Interestingly enough I cannot close this issue due to lack of permissions ;-)

[ipelupessy]

ok, that should be fixed now;-) the repository defaults where read only for members...
in any case, you can leave it open because the original issue is not fixed yet...