-
Notifications
You must be signed in to change notification settings - Fork 66
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
Does NLsolve want to move in with Optim? #85
Comments
|
|
sure. my contributions here were so small as to not seem copyrightable, but I agree to relicense. |
Thanks @sebastien-villemot for getting this started and being willing to use MIT! |
I think most major contributors have agreed, but we can wait and see. I think it would be great to have optim and nlsolve together in an org, so very excited to see that great feedback on the request here. |
I agree to relicense the code I have added to NLsolve under the MIT license. |
So do I
…On Mon, Feb 13, 2017 at 12:04 PM Tim Holy ***@***.***> wrote:
I agree to relicense the code I have added to NLsolve under the MIT
license.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#85 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AF733eOna2fk_L_IzahrcCEcpnrLKddKks5rcI0ygaJpZM4L90gF>
.
|
I also agree. |
Ok from me.
…On Feb 13, 2017 12:44 PM, "Spencer Lyon" ***@***.***> wrote:
Excellent, once we hear from @mlubin <https://github.com/mlubin> we are
good to go!
@pkofod <https://github.com/pkofod> how do you want to handle this? One
option would be to give me write (maybe need admin?) permissions in the new
org so I can make the transfer. Are you ok with that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#85 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABp0M78LMDUrGORs0UuapeNZ_tV_2zRlks5rcJZvgaJpZM4L90gF>
.
|
There's no code here derived from other sources, is there? |
@sebastien-villemot wrote most of the package, so I'll defer to him (and anyone else who knows the answer!) |
I don’t remember all the details, but since I put a Of course I cannot tell for the code contributed by others. |
Any objections (from those who haven't already approved)? If not I'll make the transfer soon |
Thank you all. Transfer completed. |
Thanks. And please go ahead with the modification of |
Guys, it seems you forgot about this... JuliaNLSolvers#85 Got mentioned in chat, shoutout to gitter and @ChrisRackauckas If anything needs to be improved/got any comments critiques, they are more than welcome, as well as resubmissions.
Guys, it seems you forgot about this... JuliaNLSolvers#85 Got mentioned in chat, shoutout to gitter and @ChrisRackauckas If anything needs to be improved/got any comments critiques, they are more than welcome, as well as resubmissions.
ref: JuliaNLSolvers/Optim.jl#358
Optim is leaving JuliaOpt, as the latter is refocusing, such that it will be an org for MathProgBase, JuMP and extensions, and backend solvers. This means that Optim+LineSearches+LsqFit is looking for a new home; a new org (current most likely name according to the issue above:
JuliaNLSolvers
).The org is going to contain a quite tightly knit collection of packages: A base package, Optim, LineSearches, some benchmarking and testing packages, and a Least Squares package + curve fitting (LsqFit currently - not sure if there's some refactoring that makes sense there). There's a lot of common code base in there, so it actually does make a lot of sense for us to move.
I was hoping that NLsolve could follow, such that we could get a stack of solver packages (optimization and nonlinear equations solving) written in Julia, and with a (to the extent possible) similar API. There's a lot of code that is repeated across Optim and NLsolve, so I think we can really improve the development work flow and throughput by joining forces formally.
Below, I've CCed everyone who has contributed to this package. The reason is, that I very much prefer that NLsolve (NLSolve?...another discussion) moves into our new home as an MIT licensed package. If people do not agree, we can discuss it, but let's just say that I prefer it that way, and I know other people in the Optim stack do as well.
So this issue is really about the following two questions:
Thanks!
cc: @KristofferC @sebastien-villemot @timholy @ChrisRackauckas @matthieugomez @tkelman @sglyon @mlubin
The text was updated successfully, but these errors were encountered: