Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separating code in multiple packages #108

Closed
davibarreira opened this issue Jul 1, 2021 · 6 comments
Closed

Separating code in multiple packages #108

davibarreira opened this issue Jul 1, 2021 · 6 comments

Comments

@davibarreira
Copy link
Member

davibarreira commented Jul 1, 2021

It was discussed the idea of splitting the code in multiple and using OptimalTransport.jl as a "unifying interface". Are we going to follow this route? I've started the creation of the ExactOptimalTransport.jl package with the algorithms for the exact ot problem, but I have some questions about things like documentation. I mean, are we going to have documentation for each package, or just for the OptimalTransport.jl? Also, should we implement all the badges such as Zenodo, or just leave it in the main package?

@devmotion
Copy link
Member

In my experience it is better to have separate documentations. Otherwise the documentation is outdated and does not refer to specific versions.

We also have to make sure that we keep the git history when we refactor and split OptimalTransport.

@davibarreira
Copy link
Member Author

So I can go on with the ExactOptimalTransport.jl package? Can I add it to the organization already or should I fixed the documentation first? I already adjusted the dependencies and tests, and it’s all working already.

Also, What about the DOI? Should I create another Zenodo badge or is it unnecessary ary?

@devmotion
Copy link
Member

devmotion commented Jul 1, 2021

Have you preserved the git history or did you just copy the files?

@davibarreira
Copy link
Member Author

Just copied -.- (sorry I’m a noob)

@devmotion
Copy link
Member

No worries 🙂 We should preserve the git history though since otherwise it is not clear why and by whom different things were implemented. This will make it easier for future contributors (and ourselves) to understand the design. Moreover, it will lead to better structured commits.

Usually, it is easiest to extract the relevant files with https://github.com/newren/git-filter-repo/ (if it is not nicely separated yet, we would want to refactor it in OptimalTransport.jl first) and then add the remaining Pkg + Documenter stuff in an initial PR. You can try it, otherwise I can take a stab at it within the next days.

@devmotion
Copy link
Member

I just noticed that I completely forgot this issue. I just extracted the relevant files and git history to https://github.com/JuliaOptimalTransport/ExactOptimalTransport.jl. I'll make a PR that gets the package into a runnable state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants