Hi,

I would be interested in helping with plotly, following the
Package Salvaging procedure outlined in the Developers Reference[1].

I've been NMU'ing the other package "python-mido" of yours many
times already but the changes I envision for "plotly" does not belong in a NMU:
I'd like to split-out the tiny javascript runtime library from the main Python package
to be able to use it in a standalone fashion on embedded edge servers.

This would happend after first upgrading to 6.6.0.


I believe the package would be a great addition to the Python Team
where I plan to further maintain it.


Kind regards
    Alexandre.

[1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging

Hi Alexandre,
for you information I have a fork on Salsa with 6.5.2
https://salsa.debian.org/ballarin/plotly
which can be used as a starting point.

I have tried getting in touch privately with the current maintainer to inform him about my
(at this point, our) availability. First attempt was dated March 2, second
attempt has been done today April 12.

Cheers,
Francesco

Hi Alexandre (and maybe Josue),

Will Plotly 6.x appear in the DELAYED queue soon?

Best,
Nicholas

Hi Nicholas,

I'm working on releasing a new version soon. I just merged ballarin
changes, I want
to do some final adjustments and I'll upload the new version soon.


Is this blocking any downstream/reverse dependencies work?

Hi Josue,

Josue Ortega <josue@debian.org> writes:

That's great news!

Maybe.  I learned about plotly because of a preliminary investigation
into hledger-sankey which is tested with plotly 6.x and not 5.x.  Sankey
generates visual expense reports--they're a great low-effort way of
coming up with a better strategy for finances.

https://github.com/adept/hledger-sankey

There's no rush.  Let me know if you're interested in this software and
I'll start work on evaluating if it's ready for Debian, fixing one of
the UI issues, and packaging it.

Cheers,
Nicholas