search

JuliaAI / MLJ.jl

A Julia machine learning framework
https://juliaai.github.io/MLJ.jl/
Other
1.78k stars 156 forks source link

Migrate packages to JuliaAI #765

Closed ablaom closed 3 years ago

ablaom commented 3 years ago

Eventually it would make sense to move the whole MLJ ecosystem to JuliaAI but already very helpful and not too disruptive would be to move the "interface only" packages listed below. These are currently difficult for developers to find, unless they have them bookmarked.

edit Here are the steps to move a repo:

@sjvollmer I have invited you to JuliaAI. If you accept, you will be able to do step (i) (and will be the only one able to do so unless Turing will grant someone else access). An alternative would be for Turing to give Mose or me (temporary) access.

@giordano Do you already have privileges to transfer repos owned by alan-turing-institute?

Transferred:

PR to General has been posted:

other stuff sorted:

giordano commented 3 years ago

@giordano Do you already have privileges to transfer repos owned by alan-turing-institute?

I'd need to be admin of a repository to be able to transfer it to another organisation, I don't think I'm admin of any of them

ablaom commented 3 years ago

Here are the rest:

Transferred:

PR to General has been posted:

other stuff sorted:

Note: MLJFlux lives at Flux org, which provides GPU testing.

ablaom commented 3 years ago

@DilumAluthge When transferring ownership to a new organization, what steps should we take, typically, to handle the documentation, when this is hosted by the repo's github pages?

For example, in the case of MLJScientificTypes, I guess we just update the make.jl deployment url. Are there any unexpected consequences of doing this we should worry about? Or some other step I'm missing?

cc @vollmersj

DilumAluthge commented 3 years ago

Updating the make.jl file should be sufficient, actually.

DilumAluthge commented 3 years ago

All the docs themselves are in the gh-pages branch, so when you transfer the repo, the docs should automatically show up at the new URL.

DilumAluthge commented 3 years ago

In addition to updating make.jl, you'll need to update the URLs for the "docs" badges in the README.

ablaom commented 3 years ago

Thanks!

zsz00 commented 3 years ago

Why create a new organization? Why is it called JuliaAI? Why not move to the existing JuliaML?

ablaom commented 3 years ago

Fair enough question.

The packages of the MLJ universe (about two dozen) which are tightly integrated, have (for whatever reason) evolved mostly independently of packages in the older JuliaML ecosystem. For administrative convenience, it makes sense for the MLJ packages to have a common umbrella - currently they get rather lost in the alan-turing-institute org, and there is no concept of nested organizations in GH.

I personally don't have any political objection to the packages living under JuliaML (although some members of JuliaML, might, since a lot of that interface has not been extended by MLJ). However, I do think this is would be less convenient, and probably confusing. It may be that some convergence in the two visions is possible, but not without a lot more resources coming into play, and not any time soon.

I chose "JuliaAI" because "MLJ" and a bunch of other alternatives were already taken.

DilumAluthge commented 3 years ago

Could we move the MLJRegistry.jl repo (https://github.com/alan-turing-institute/MLJRegistry.jl) to the JuliaAI organization?

I know that it is archived, but I think that it still makes sense for MLJRegistry.jl to live in the same place as MLJModels.jl and MLJBase.jl.

cc: @ablaom @vollmersj @sjvollmer

ablaom commented 3 years ago

This is all done except MLJ itself. So closing in favour of separate issue.

DilumAluthge commented 3 years ago

FYI, https://github.com/alan-turing-institute/MLJRegistry.jl has not been migrated - would be good to do so, even though it is archived.