epezent
🐦🔥 Project Revival & v0.17 Roadmap 🐦🔥
Hey @epezent, thank you for your work on this awesome project.
It's very unfortunate to see it being abandoned (except for some maintenance fixes by Omar himself). There is clearly interest in contributions judging by open PRs.
Would you be open with giving write permissions to myself or a trusted member of the community to keep this going? Perhaps a fork as well - but ideally you'd still merge a PR to direct users there for the transition.
Thank you for your time!
cc'ing people who recently tried to contribute, for visibility: @bostick @mihaly-sisak @howprice @prybicki @vincentjzy @ACvanWyk @BitCourier @brccabral @moe93 @luc16 @GameChaos @SamuMazzi @Gargaj
Hi @VelocityRa, thanks for starting this thread.
Just to add some context, I'm Breno, the author of ImPlot3D. I've been in touch with @epezent about the ImPlot's future earlier this year. We were discussing a refactor to build ImPlot3D on top of ImPlot and avoid duplicated code.
Evan mentioned he's been swamped with his work at Meta and hasn't had much time for open-source, which is totally understandable.
In our last chat, he suggested I could step in as a maintainer to help out. I'm still happy to do that and can start helping with the open PRs and issues.
@epezent, no pressure, but if you get a chance, this seems like a good place to figure out a path forward for the community.
For some other projects a good way forward was placing the project itself in a Github organization and build a small team of co-maintainers to share the work. That way you can eliminate potential pressure points and make continuation of the project much smoother.
@VelocityRa thanks for the much needed poke.
As @brenocq pointed out, he and I have had sporadic discussions about helping out this year, given his inside-out knowledge of ImPlot and ability to contribute novel, high-quality code as evidenced by ImPlot3D.
As of today, @brenocq has permisions to accept and merge PRs. He will begin by working through outstanding PRs, particularly low-hanging ones, with the intent to cut a v0.17 release as soon as possible. Following that, we'll start looking at heavier, feature-related PRs and issues.
I won't say more to plans beyond that, other than we are both fully aware that ImPlot needs new life breathed into it and that the community still very much cares about it.
Evan
@epezent thanks for the official announcement and for the trust ❤️
As Evan noted, I'm currently going through the open issues and PRs to find the ones that should be in the release v0.17. I've created the milestone v0.17 to aggregate the issues/PRs that should be merged before the v0.17 release (only bug fixes & small features, no breaking changes). It is very likely that I left some important ones behind, so I would very much appreciate if you guys could tag me on the issues/PRs you think should be merged before v0.17. Let's bring the ImPlot development hype back :)
Tagging relevant people: @ocornut @VelocityRa @BenBE @bostick @mihaly-sisak @howprice @prybicki @vincentjzy @ACvanWyk @BitCourier @brccabral @moe93 @Luc16 @GameChaos @SamuMazzi @Gargaj @sonoro1234 @ozlb @sergeyn @JaapSuter @ChiefyChief23 @pthom @dimateos @RT2Code @brutpitt (I probably missed some people, everyone is welcome to help)
Note that ImPlot is currently included in https://github.com/IDI-Systems/UnrealImGui/ which means there will be issues getting all those changes downstream.
Thanks for raising this @Gargaj (tagging @segross and @jonpas for visibility). After the official v0.17 ImPlot release, I think they need to update the UnrealImGui codebase.
P.S.: ImPlot3D would love to be there too :)
Thanks to the effort of @epezent and @brenocq , it is nice to see the project become active again. Indeed, Implot has been an indispensable module for anyone who want to make amazing GUI based on Dear ImGui. Further development will definitely benefit the whole community of Dear ImGui.
