# Hackathons for JuliaCon

**URL:** <https://discourse.julialang.org/t/hackathons-for-juliacon/12183>\
**Category:** 2018\
**Tags:** juliacon\
**Created:** [July 5, 2018, 3:00pm UTC](https://discourse.julialang.org/t/hackathons-for-juliacon/12183 "2018-07-05T15:00:26Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![odow](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/odow/32/28685_2.png) [@odow](https://discourse.julialang.org/u/odow)\
**Post date:** [July 9, 2018, 3:25am UTC](https://discourse.julialang.org/t/hackathons-for-juliacon/12183/8 "2018-07-09T03:25:22Z")

</div>

> [@ChrisRackauckas](#):
>
> Given the audience, I would be surprised if JuMP / optimization wasn’t another big topic.

Unfortunately, none of the core JuMP developers are attending this year’s JuliaCon. (Although Juan Pablo will be giving a [tutorial](http://juliacon.org/2018/talks_workshops/7/).) However, we recently held a well attended [workshop](http://www.juliaopt.org/meetings/bordeaux2018/), and progress is being made regarding the upcoming transition to MathOptInterface. You can read more about the transition [here](https://discourse.julialang.org/t/mathoptinterface-and-upcoming-breaking-changes-in-jump-0-19/4874).

---

_[View the full topic](https://discourse.julialang.org/t/hackathons-for-juliacon/12183)._
