Display Map Time during Voting

I was thinking map[map timer]!

How about displaying the maps like/dislike ratio instead. For instance, [Map name] 100(likes) : 200(dislikes)?

Yes, I think roundtime is much preferable to likes to dislikes. Players deserve to know the roundtime of the maps they're voting on, whereas likes to dislikes are very arbitrary

Instead of showing the round time for each level individually, the map voting pool should consist of 3 maps with the exact round time, based on player count. The round time could be displayed above or below all the maps instead for a label for every map. The "time based on player count" suggestion was certainly brought up in the past, and if it is indeed planned for post-rewrite, this suggestion could be implemented as well, but only in the form that I have described. Keep in mind that another suggestion is already being implemented which does a similar thing but displays Trial status instead, so if round time was shown as well it could potentially use up a lot of space in the chat.

I agree that keeping it random is the most fair, although I don't think fairness is enough to determine its effectiveness. Think of a hypothetical scenario like this: 3 players are online on the server. A round ends, and voting for the next map begins. Available maps to vote on are an 8 minute, 6 minute and 4 minute map.
Player A is an experienced player that has already played through all the maps, and votes for the short, 4 minute round, due to the low player count.
Player B is a new player that just recently began playing on the server and doesn't quite understand what round time means and if it matters, so they vote for the map that catches their attention the most: the 8 minute map that just so happens to be the one with the most interesting name.
Player C is a decent player that completely dismisses the vote.
Effectively, the votes are 50-50 between the very long and the very short map. If the very long map wins from RNG, the round becomes stale and boring. The beginning zombie would have very little choice of winning unless Player A is chosen (33%), and even then the sheer size of the map would make the whole round just not fun to play and players would eventually leave.
Player A wouldn't be satisfied because a round has been wasted on a long and boring map, and leave the server.
Player B wouldn't be satisfied as they would take the gamemode as boring, and leave the server.
Even if Player C doesn't care and doesn't leave anyways, he would still be affected by the the others that had just left and would follow suit.
This might be a bit too specific and too much of an exaggeration, but I've seen lots of situations like that play out in many similar ways. I believe that the map voting should be dynamically balanced for the player count to avoid such situations. I don't think maps would repeat too often as player counts would change gradually over time, and there could be some additional code written specifically to avoid matching up the same maps too often. Another way to avoid this would be to occasionally include a longer/shorter map (depending on current player count) as a third map as an alternative to two other maps with normal times, so that if people do wish to play a different map, they can vote on it to do so. Also, map queueing exists if people really need to play a "rare" map once in a while (rare in quotation marks mainly due to the chances of a specific map appearing in a single vote being quite low).