Make the JS graph show Python 2 dropping status #491
Conversation
Also: - Remove Group graphs entirely - Avoid the DB in the web app - Require networkx
|
Not sure how do I read that graph yet, but it is indeed CPU hungry :D |
|
Shouldn't the text above the graph be updated? |
|
Ah, good catch! I knew I forgot something. |
| Darker colors mean more dependencies. | ||
| Here is a graph showing dependency relationships for | ||
| packages in Fedora Rawhide that need Python 2 in some way. | ||
| Brighter colors roughly mean the package can be removed sooner. |
There was a problem hiding this comment.
OK, I guess I don't get that part. I see the same colors as in portingdb. How is their brightness showing when they can be removed?
There was a problem hiding this comment.
The ones that can't be removed easily are dark (and they're in the center).
Granted, it's not very obvious – and perhaps not even helpful. Should this just use the same colors as everywhere else?
Here's the graph with this shading turned off:
There was a problem hiding this comment.
I only see it on the green ones. And only now when you showed me. Better ask another person as well.
There was a problem hiding this comment.
Well, the "hard to remove" ones are mostly green (and gray).
There was a problem hiding this comment.
Are we bikeshedding at this point?
Also:
And, this makes the graph CPU-hungry again.