# Help us test the Feature Voting plugin

**URL:** <https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188>\
**Category:** Site feedback\
**Created:** [2017年三月1日 19:02 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188 "2017-03-01T19:02:31Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)\
**Post date:** [2017年三月1日 19:02 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/1 "2017-03-01T19:02:31Z")

</div>

We’ve just opened up the long-dormant #feature:integrations category to the general public.

This category is running with @joebuhlig’s [Feature Voting plugin](https://meta.discourse.org/t/discourse-feature-voting/40121) enabled. We’ve officially adopted this plugin, and will be working together with Joe to make it stable enough for use with our hosted customers.

### Go test things!

Go to the #feature:integrations category and vote your heart out. Do weird things; break it. Add new integrations for people to vote on.

- Bug reports or feature requests should be posted to the plugin’s own topic.

- Questions about the voting process here on Meta can be asked here in this topic.

The future of the Integrations category and the use of Feature Voting on Meta is not yet determined.

---

<div class="post-metadata">

**Author:** ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)\
**Post date:** [2017年三月1日 19:03 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/2 "2017-03-01T19:03:14Z")

</div>



---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2017年三月3日 21:28 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/3 "2017-03-03T21:28:54Z")

</div>

OK, now that we’ve gotten it pared down to a reasonable state, @sam had the following feature requests he wanted to get to:

- Replace “Top” with “Voted” on “voting” categories.
- Suppress likes on OP for “voting” topics
- Sane behavior when you reach your limit, “You can not vote anymore, here is a list of stuff you voted for”
- Handle edge case, deletion does not reclaim votes
- Strip useless words off screen that shows who voted

One note, **every time you vote it should tell you how many votes you have remaining**. I had no idea votes were even limited in this manner. Something like.

> You’ve cast 3 of your 5 available votes.

And

> You’ve cast 5 of your 5 available votes. To cast more or change your votes .. {blah}

Also @erlend_sh **this is a fork and will remain a fork** , so I think it deserves its own topic, like `discourse-official-feature-voting` or similar? I believe there’s been a bit of a misunderstanding on where comments should go, because this plugin has significantly different functionality in first party delivered form…

---

<div class="post-metadata">

**Author:** ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)\
**Post date:** [2017年三月3日 22:15 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/4 "2017-03-03T22:15:23Z")

</div>

> [@codinghorror](#):
>
> this is a fork and will remain a fork

Why? @joebuhlig already agreed to move the plugin to our official repo. It’s been “ours” for months:

[https://github.com/discourse/discourse-feature-voting](https://github.com/discourse/discourse-feature-voting)

Does it need to be a fork? Can’t it just be v2?

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2017年三月3日 22:16 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/5 "2017-03-03T22:16:17Z")

</div>

If these people were relying on “supervotes” they may be in for a bit of a surprise..

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [2017年三月3日 22:23 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/6 "2017-03-03T22:23:29Z")

</div>

> [@codinghorror](#):
>
> If these people were relying on “supervotes” they may be in for a bit of a surprise..

I think anybody expecting this thing to even boot on beta or stable are in for a slightly bigger surprise.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2017年三月3日 22:24 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/7 "2017-03-03T22:24:16Z")

</div>

OK then I recommend removing the old topic and creating a new one @erlend_sh – we’re rebooting this. It will be confusing to find old out of date info..

---

<div class="post-metadata">

**Author:** ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)\
**Post date:** [2017年三月3日 22:43 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/8 "2017-03-03T22:43:22Z")

</div>

Ok, once there’s a new topic let’s link to it, close the old one and eventually archive and unlist it. There are lots of discussions and ideas worth holding on to there, so I definitely don’t want to delete it completely.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2017年三月3日 22:49 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/9 "2017-03-03T22:49:17Z")

</div>

I don’t subscribe to that theory. I subscribe to the “if it’s a good idea, it will come up again naturally” theory.

We’d also be polluting search results _forever_ with the strategy you suggest.

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [2017年三月3日 22:57 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/10 "2017-03-03T22:57:22Z")

</div>

I think this is a general problem lots of our plugins have, also discourse solved has it, mountains of irrelevant out of date discussion, it’s like each plugin struggles to be a category but is trapped in a topic

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2017年三月3日 22:58 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/11 "2017-03-03T22:58:08Z")

</div>

We could certainly have one subcategory for each official plugin, there aren’t _that_ many.. tags are also an option?

---

<div class="post-metadata">

**Author:** ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)\
**Post date:** [2017年三月3日 22:58 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/12 "2017-03-03T22:58:35Z")

</div>

I don’t like the practice of completely erasing good deeds from history. @joebuhlig deserves a lot of credit for taking my spec and building a fully functional plugin. Loads of other people helped test and reported bugs. The likes that were doled out during this back and forth had meaning; they were by and large acknowledgements of various contributions.

Archive & unlist the topic. Don’t delete it.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2017年三月3日 22:59 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/13 "2017-03-03T22:59:48Z")

</div>

The problem is this old out of date information is penalizing all future visitors, _forever_. So there is a rather steep (and forever growing!) cost to retaining it. As Spock once said, the needs of the many outweigh the needs of the few.

The only way to do what you propose is to completely disallow it from appearing in any search… somehow. I don’t think archiving and unlisting do that.

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [2017年三月3日 23:26 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/14 "2017-03-03T23:26:14Z")

</div>

Actually a handy feature may be an option on a category to exclude from search including google.

Then users get to keep karma and badges and the many are not punished, we just chuck content like this into a graveyard category

---

<div class="post-metadata">

**Author:** ![cpradio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cpradio/32/4970_2.png) [@cpradio](https://meta.discourse.org/u/cpradio)\
**Post date:** [2017年三月3日 23:34 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/15 "2017-03-03T23:34:20Z")

</div>

Does unlisting a topic prevent the badges? As unlisting the topic would prevent google from indexing it anymore

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [2017年三月3日 23:37 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/16 "2017-03-03T23:37:12Z")

</div>

Unlisting is still not what is desired, you want to still show off that you had a +20 likes post, but we don’t want people to find it outside of visiting your profile, graveyard or badge list

Unlisting hides from search, badge queries and user page

---

<div class="post-metadata">

**Author:** ![Remah](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/remah/32/70590_2.png) [@Remah](https://meta.discourse.org/u/Remah)\
**Post date:** [2017年三月3日 23:37 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/17 "2017-03-03T23:37:54Z")

</div>

我对这场关于“家庭”的讨论感到困惑。起初，它看起来像是突然结束，没有任何结果，让人感觉讨论已经转入线下。😌

@codinghorror，meta.discourse 上充斥着过时信息，为什么这对 #Customization > Plugin 来说却成了个问题？

@erlend_sh，删除那些在当时有价值、但现在只会让搜索者困惑的过时信息，有什么问题吗？我阅读了该主题，发现其中大部分内容并不会被怀念。

#### 以插件发布主题作为部分解决方案？

我想知道这是否与 Discourse 将 #releases 作为功能变更的权威记录有关？如果是这样，那么这是否也可以成为官方插件设立发布主题的选项？

这将更清晰地表明，插件的开发是有条理且足够重要，值得被简洁且永久地记录。这也使得贡献能够永久地获得 prominence（突出展示）。

如果保留原始主题，它们可以被关闭，并附上指向发布主题的链接。

---

<div class="post-metadata">

**Author:** ![joebuhlig](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/joebuhlig/32/193054_2.png) [@joebuhlig](https://meta.discourse.org/u/joebuhlig)\
**Post date:** [2017年三月4日 00:12 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/18 "2017-03-04T00:12:46Z")

</div>

Of course I’m biased, but why not rename the original topic to deprecated, close it, and create a new supported plugin topic? That process is done elsewhere. The only difference being the plugin category.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2017年三月4日 03:45 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/19 "2017-03-04T03:45:24Z")

</div>

Because it clutters search results with irrelevant, obsolete information for eternity. That is my main objection. We could move it to the lounge so it won’t get indexed.

---

<div class="post-metadata">

**Author:** ![joebuhlig](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/joebuhlig/32/193054_2.png) [@joebuhlig](https://meta.discourse.org/u/joebuhlig)\
**Post date:** [2017年三月4日 12:57 UTC](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188/20 "2017-03-04T12:57:43Z")

</div>

At what point do you go back and filter out old topics? I run across outdated code here on Meta all the time. That’s the nature of development. Things progress and old methods no longer work. Rather than try to hide or delete all the old information, wouldn’t it make more sense to flag it in some way (rename it and close it) and give people a way to get to the new information (create a new topic and link to it from the old).

If I understand your logic correctly (and I’m not sure I do), wouldn’t that mean you need us to start flagging topics that contain obsolete information?

I’m not an SEO expert by any means but I’ve always assumed that Google prefers new content to old. By closing the old and sending users to the new, wouldn’t you be weighting the search results to the update information anyway?

You understand these things a lot better than I do. I’m simply struggling to follow your rationale here.

[下一頁](https://meta.discourse.org/t/help-us-test-the-feature-voting-plugin/58188.md?page=2)
