Move to JuliaLang Github Organization

[mkitti]

We should considering moving Revise.jl to https://github.com/JuliaLang.

The general problem is that Revise.jl has become such a fundamental part of using Julia, but it is difficult for new users to discern the close relationship between Revise.jl and the Julia project as a whole as Christopher Rackauckus recently articulated.

Given the following indicators, a general concensus now exists that Revise.jl is part of Julia.

• It's mentioned in the official documentation: https://docs.julialang.org/en/v1.9/manual/workflow-tips/#Revise-based-workflows
• It's supported by the julia-vscode extension

To make it clearer, especially to new users, that this package is closely integrated with Julia development, I suggest moving this package to the JuliaLang organization.

edit: Make the motivation for moving this package clearer.

[KristofferC]

Who are "we" here? I don't see why any of your points warrants a move of the repo. I don't think this needs to be an open issue since there isn't really anything to fix.

[mkitti]

We as in the community, or perhaps effectively, whomever has maintainership over this package, which is quite unclear at the moment.

Why is https://github.com/JuliaLang/PrecompileTools.jl in the JuliaLang organization and not Revise.jl?

[mkitti]

The problem is as @ChrisRackauckas stated on Discourse of how do people determine if Revise.jl is "part of Julia" or not.

Quoting @timholy 's response:

I suppose we could move Revise to JuliaLang, if there’s a general consensus that it’s better there. But where do you draw the line? To me, Cthulhu and JET seem to be in the same camp as Revise. My suspicion is that JET in particular will come to occupy a much more central role once we get full static compilation. In the long term, I think PackageCompiler will go away, but JET will only grow in importance.

I would like to gauge here if a general consensus now exists.

[ufechner7]

Who are "we" here? I don't see why any of your points warrants a move of the repo. I don't think this needs to be an open issue since there isn't really anything to fix.

Well, it would be good if it would be clear that Revise is a core part of the Julia language ecosystem, and not just a hobby project of some private developer... And moving the repo could make this more clear.

[stevengj]

To me, once a package becomes widely used, it should really be moved into some organization (JuliaLang or other), if only to have a clear structure of multiple owners potentially able to step in if the original maintainer moves on.

[rben01]

Revise is a core part of using Julia — it's even part of the official docs (see below)! I think once a package is recommended in the official docs, it should probably be moved under JuliaLang, both to indicate that it's quasi-official (and it is, since the docs recommend it) and to place it under a larger group of people than just @timholy.

Whether you're at the REPL or in IJulia, you can typically improve your development experience with Revise. It is common to configure Revise to start whenever julia is started, as per the instructions in the Revise documentation.

As for other “core-ish” packages like JET and Cthulhu, my guess is that they are not nearly as core as Revise. When it comes to developer experience, JET and Cthulhu are nice-to-haves, whereas Revise is simply a necessity. Furthermore, JET and Cthulhu seem rather experimental and unstable at this point in time, whereas Revise is quite stable.

[StefanKarpinski]

This seems like a fine idea to me. At the very least, it should be moved out of @timholy's personal GitHub account. We really shouldn't have key pieces of ecosystem infrastructure that aren't in some kind of org.

[DaniGlez]

I believe that Revise is a step above the mentioned analysis packages in terms of spread, if only because it's a default addition to the integrated REPL with the Julia extension for VS Code.

[timholy]

I'd be happy to move Revise to JuliaLang once it can be implemented sanely. But currently it's insanely heroic and requires a huge software stack. There are also relatively few people who are able/willing to maintain Revise, and I think all of them already have full commit access.

[LilithHafner]

Triage says that we should move this to JuliaLang to signify that it is a core part of the Julia language tooling and such and so that more than one person has owner permissions. Nobody at the meeting would be willing to die on this hill, but we all agree that it would be good.

There is no requirement that things in the JuliaLang org be sane. ;)