-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
move the package to an org? #275
Comments
I'm fine moving it to an org. I unfortunately have a pretty limited amount of time to get to issues these days. I know @ChrisRackauckas has also talked about bringing it into SciML before as well. Whichever works best is fine for me. |
I have sufficient permissions (on SciML org end) to move this to SciML |
Okay cool. Let's do that then. I imagine its a somewhat complicated process, so I can look into what I need to do to transfer it this weekend. |
Sounds good. I think we need to add you as a member of SciML then you will have permission to transfer. |
Okay. It should probably be my non-work account since that's the one that owns this repo. |
I gave an invite. |
Simple PRs,like #272 and #273 , which update the package compat bounds,
are taking a long time to be merged. This is blocking users' environments and downstream development
LuxDL/Lux.jl#1061
Maybe it is better to move the package to an org like JuliaArrays in order to help maintenance.
Also relaxing the policy in
Settings -> Actions -> General -> Approval for running fork pull request workflows from contributors
allow to automatically trigger the workflows in those PRs.
The text was updated successfully, but these errors were encountered: