From a quick look; - python@ was added as primary maintainer without asking us - packages have no tests - packages are missing ||die - packages are missing remote-ids I'm going to revert the relevant packages while they're still fresh.
Do you mind if I find a new home for that (like sci-something) or you don't like at all packages with no test? For those packages I have not found any test, I only tested the build using it in a jupyter environment. I agree with you that I have not asked python team, but vim created metadata.xml with python team and me as maintainer, and I thought it was a standard thing Sorry for the noise
(In reply to Tupone Alfredo from comment #1) > Do you mind if I find a new home for that (like sci-something) or you don't > like at all packages with no test? For those packages I have not found any > test, I only tested the build using it in a jupyter environment. Category doesn't matter. What matters is that you made python@ maintainer of these packages without following our guidelines. You're basically expecting us to go figure out how to test this. It's not fair. That said, while jupyter-dash doesn't seem to have tests, at least dash has them. And missing ||die is not a mistake you should be doing these days. Feel free to readd them without python@ in metadata. But please at least add remote-ids and tests where available upstream. Use GitHub archive tarballs if necessary.
Packages readded in sci-visualization, as they could handle more then python. I am now the only maintainer To add test I need to add other packages in, so I will delay this. I added the remote Ids
