Johannes Lange
Johannes Lange
You are right, spamming thousands of notifications is not clever. Dunst would also show them all. I also think grouping these as "Downloaded xxx files" is fine. In that case...
I indeed follow what's happening here, but I don't have push rights to this repo, sorry.
I would not recommend moving development to a different fork. It is hard for users to find it and even harder to tell which of the hundreds of forks is...
> If you are serious about maintaining it I would start with a fresh repo and not from a fork. People tend to be skeptical when they see forked repos....
@vivien at least it would not harm. As I said, I'm following the developments here, anyway, so I can also help as a maintainer.
At the moment not, no. I wasn't that active here during the last weeks, because I'm quite busy. But I will try to improve that soon!
You are probably using an outdated version of i3blocks. See https://github.com/vivien/i3blocks/issues/279 and #132.
> I propose is to make a new major release of dask-jobqueue soon (in the coming days or week), version 0.8.0 Sounds good. > What about 6 months? Or maybe...
Pay attention to the title:  Also see quantifiedcode/quantifiedcode#14. Apparently, good test coverage does not solve all problems. So I tend to looking into the other option...
Ok, Code Climate is not free... *Edit* False alarm. The "velocity" product is not free. The "quality" product is, though.