# Voting system to assess community demand for various features

**URL:** <https://discourse.julialang.org/t/voting-system-to-assess-community-demand-for-various-features/627>\
**Category:** Internals & Design\
**Created:** [November 29, 2016, 1:45pm UTC](https://discourse.julialang.org/t/voting-system-to-assess-community-demand-for-various-features/627 "2016-11-29T13:45:43Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![pitao](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pitao/32/116_2.png) [@pitao](https://discourse.julialang.org/u/pitao)\
**Post date:** [November 29, 2016, 1:45pm UTC](https://discourse.julialang.org/t/voting-system-to-assess-community-demand-for-various-features/627/1 "2016-11-29T13:45:43Z")

</div>

A few years back I was using Unity3D.

They had a nice system where each developer gets 10 votes and can vote for ideas (or even create a new idea and award it votes). One is allowed to spend multiple votes on a single idea. Switching votes is okay.

It worked very well as a way of probing the weak points of the technology.

I wonder if there is any way of doing something like this with Discourse.

We could create a thread (& pin it) and every idea could be a post and everyone could use the ‘like’ button. Not perfect because some ideas would generate replies & it will get a bit messy. Also one has infinite 'like’s.

But it might be useful. I notice conversations on Github going along the lines of _“We are very surprised to see so many developers like e.g. `x and y` over `x && y`!”_. Some kind of feature voting system might reduce surprise in certain situations.

---

_[View the full topic](https://discourse.julialang.org/t/voting-system-to-assess-community-demand-for-various-features/627)._