# New organization for Optim+family

**URL:** <https://discourse.julialang.org/t/new-organization-for-optim-family/2037>\
**Category:** Optimization (Mathematical)\
**Created:** [February 11, 2017, 12:47pm UTC](https://discourse.julialang.org/t/new-organization-for-optim-family/2037 "2017-02-11T12:47:24Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![ChrisRackauckas](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chrisrackauckas/32/77_2.png) [@ChrisRackauckas](https://discourse.julialang.org/u/ChrisRackauckas)\
**Post date:** [February 11, 2017, 2:59pm UTC](https://discourse.julialang.org/t/new-organization-for-optim-family/2037/4 "2017-02-11T14:59:11Z")

</div>

> [@pkofod](#):
>
> This new org will have a pretty specific package setup: A base package, a line searches package, the Optim package, an NLsolve-ish package (probably NLsolve exactly, but licensing issues just needs to be sorted out), and various auxiliary packages (tests etc). The idea is that the equations solver and the optimization package will have very similar code base and API (much like now, but the link will be strengthened even more).

I hope the Base package makes the API non-package specific. There are some good nonlinear solvers outside of this crew (Kinsol from Sundials is one, Roots.jl is another). It would be great for library code to finally have swap-ability between them, a la

> [@A Unified Interface for Rootfinding](https://discourse.julialang.org/t/a-unified-interface-for-rootfinding/698/19):
>
> Where exactly is this at now? I kind of got lost but want to revive this.

Do you have an idea for what this API is going to be looking like? We can talk more in the chats if it’s still at an idea stage and don’t want to set anything in stone, but I know you’ve been working on it for a bit so maybe there’s already a proposal somewhere?

---

_[View the full topic](https://discourse.julialang.org/t/new-organization-for-optim-family/2037)._
