search

sglyon / PlotlyBase.jl

Generate plotly.js JSON in Julia -- nothing less, nothing more.
Other
23 stars 33 forks source link

Move to JuliaPlots #103

Open BeastyBlacksmith opened 1 year ago

BeastyBlacksmith commented 1 year ago

Hey @sglyon, would you be okay with moving this to JuliaPlots also?

BeastyBlacksmith commented 1 year ago

@etpinard @Mo-Gul @hhaensel I am inclined to fork this to JuliaPlots then. Is any of you in for helping maitaining it?

hhaensel commented 1 year ago

I'm certainly not an expert in PlotlyBase but I'd be in for maintaining.

Mo-Gul commented 1 year ago

@BeastyBlacksmith, unfortunately I can't speak much more than "Hello World" in Julia. So the only help I can offer is finding more bugs, testing features and proofreading documentation ...

etpinard commented 1 year ago

@BeastyBlacksmith yes, I can help with the maintenance duties.

sglyon commented 1 year ago

Hey @etpinard and @BeastyBlacksmith

In principle I'm ok with this... however I'm not convinced that a move will help with maintenance. I think there have only been about 12 commits to PlotlyJS.jl since the move to JuliaPlots two years ago.

Would you be up for a staged approach where we try to get support maintaining here and -- if we do get strong support -- we can make the move at that time?

BeastyBlacksmith commented 1 year ago

My concern is less increasing contributors ( which of course is always nice, but as you point out, is also not something that will magically happen just because its moved ) than being part of an organization will increase the likelihood that it doesn't become unmaintained for whatever reason with no way to pass over than forking it. I mean, as JuliaFolds shows thats also no panacea, but JuliaPlots has 8 owners with some who will very likely vanish anytime soon, so I am confident that won't happen to us.

disberd commented 1 year ago

I have been dabbling with plotlybase for quite some time and would also be available to contribute if needed. It is indeed a pity that this library is almost unmaintained.

For example I just had some issues today with some wrong counter for SubPlots and realized that the PR fix was merged 9 months ago but no patch release has happened since.

empet commented 1 year ago

@sglyon is the author of this package. He has invested a lot of time and energy into creating, updating and maintaining it over the years. In the last two years, he most likely had new commitments and lacked the time needed for maintenance. At the same time, we, the users, would like it to be updated at the same pace as plotly.py. I think it would be fair that if PlotlyBase moves to JuliaPlots, the Readme file should mention his name, just as the Readme file for Plots.jl displays the name of its creator, Tom Breloff: https://github.com/JuliaPlots/Plots.jl#readme..

hhaensel commented 7 months ago

Just submitted two PRs together with @sjkelly, the first is already merged. Maybe, @sjkelly would also be in for maintainance?

@sglyon I understand if you don't like the moving of the package. You could consider adding some users as contributors and agree on how changes are submitted, e.g. only by feature branches.

BTW, will anyone of you be at the JuliaCon? That could be a good place to meet and discuss.

Mo-Gul commented 7 months ago

@hhaensel, great that there are some updates again to this package. And I plan to be at the JuliaCon, but can't promise it yet ...