Add "downloads" badge to README

[piskvorky]

Trying the idea from piskvorky/smart_open#440.

Motivation

In general, seeing how much others use a package improves confidence in its robustness and maintenance. A kind of social proof.

I see no downsides, except if the service that provides this badge (https://pepy.tech/) proves unstable or unreliable.

Badges for gitter and wheels seem useless, so I removed them.

Checklist

Before you create the PR, please make sure you have:

• Picked a concise, informative and complete title
• Clearly explained the motivation behind the PR
• Linked to any existing issues that your PR will be solving
• Included tests for any new functionality
• Checked that all unit tests pass

[piskvorky]

@mpenkov unrelated, but the "build" badge on the main page is red now, failing.

[piskvorky]

I'm also considering removing the "Anaconda Cloud" badge; WDYT?

It's still crowded up there, and this one seems near-useless (and out of our control).

[piskvorky]

@mpenkov ready to merge! CC @gojomo @menshikh-iv do you see anything else vital enough to be communicated in a badge on very top of our README?

[gojomo]

If you wanted to drive more usage/support-traffic to Gitter, I could see that badge making sense, but not sure that's a goal.

If you wanted to more generally show affiliations with, or usages of, many other projects/tech as a sort of broad-community-spirit signal, I could see adding more - but probably at a separate section at the bottom, or else they'd dilute the importance/usefulness of the top few. Not important though.

[piskvorky]

Gensim's Gitter is a ghost town. At least I never go there… I wonder if anyone does.

[menshikh-iv]

Looks fine

I'm also considering removing the "Anaconda Cloud" badge; WDYT?

Not sure than this needed, many persons use them, but up to you.

It's still crowded up there, and this one seems near-useless (and out of our control).

Not true, we control them via conda-forge/gensim-feedstock#43

BTW don't forget to merge the latest develop to your branch (before merging PR), looks like you branched from an old (broken) commit

[piskvorky]

Thanks for the heads up – develop merged.