New: Suggest features and vote for those you want in Gladys! 😍

News
1

Hello everyone,

As the v4 is becoming more widely used, it is becoming increasingly difficult to keep track of the features requested by the community, and above all, it has become urgent to have a way to prioritize developments.

We use GitHub for development to list planned/ongoing/completed developments.

However, I am receiving more and more development requests, and currently, my only way of knowing that « this development is in high demand Â» is to remember that I have seen this request in several posts: in short, it’s not sustainable :sweat_smile:

I have therefore created the Feature requests category on the forum.

This category is very simple: it’s a board where each post is a feature request. Then, everyone on this forum can vote for the features they would like to see in Gladys.

This list, ordered by number of votes, will give anyone who wants to help us with Gladys an idea of the most requested features.

This category does not replace GitHub

Be careful, this category is not meant to replace our current GitHub workflow, which remains the same.

  • Did you find a bug in Gladys? Create a GitHub issue.
  • Do you have a Philips Hue bulb not supported by Gladys? Create a GitHub issue.
  • Are you developing on Gladys and want to reference your development? Create a GitHub issue.

This category is useful upstream of GitHub. It is intended for « users Â» who want to make their voices heard and see if other users want the same feature in Gladys :slight_smile:

The new workflow

  1. The user creates a feature request on the forum
  2. The feature receives a large number of votes
  3. After discussion with the Gladys maintainers, we decide that the feature will be developed
  4. A GitHub issue is created
  5. We add a reference to the GitHub issue on the forum in the feature post
  6. The feature is developed, we close the GitHub issue and the forum topic, with a post explaining the development carried out.

What do you think?

2

Super cool this category
 Can I add Bluetooth or is it already planned?

3

I think you can add it to set an example, even if the work has already started but is still blocked


4

Indeed, we can add some already planned items to set an example and link the forum post to the issue/PR :slight_smile: This will help better connect GitHub, which is only read by developers, with the community, which is only read by users.

5

A limited number of votes is intentional, right? Not allowed to vote for everything at the same time?? :stuck_out_tongue:

6

And maybe remove the best answer feature from this category, even if only the staff can see this option it will avoid mistakes

7

Yes! It’s built-in in the system, for now I’ve left the default values:

Screenshot 2020-09-04 at 10.13.54
Screenshot 2020-09-04 at 10.13.541386×750 29 KB

@AlexTrovato You are a « Trust level 2 Â» member, so you have 6 votes to distribute, right? :slight_smile:

I don’t find it crazy, otherwise everyone will vote for everything and there won’t really be a difference between the features.

We can re-evaluate the number of votes available per user when there are more posts. For example, if there are 100 features in the category, we can give 15 votes so that the user can vote for the 15% they prefer. What do you think?

It’s not possible to disable the best answer feature for a category only, at least I haven’t found it!

8

15% is not bad indeed, and no problem for the « best answer Â» option :wink:

9

I also agree. 15% really allows you to focus on the main features you are looking for. And as progress is made, you can choose other options.

By the way, when you create a topic, does it count as a vote for the creator or do we also have to vote on it? If not, maybe specify that because I’ve seen topics created without votes, and I’ve done the same ^^

10

You need to vote if you support the idea you’re posting :slight_smile:

11

Great idea for adding features.

Can I add to the votes?

  • possibility to use an Arduino
  • have Netatmo product management (thermostatic head, thermostat, camera, 
)
12

@Tlse-vins You are welcome, everyone can post!

13

Could a tag or badge like [In Dev] be added for requests/ideas that are in development?

14

Is it possible to order by the number of votes because it’s not very practical at a glance to know what is most requested

15

In the « new features Â» category, you have a sorting option in the page header, and you can sort by vote.

16

I saw that just before going to sleep, so it’s fine, thanks

17

@pierre-gilles The vote limit does not reset.

I think we need to at least double it because there are quite a few feature requests and we must have all exceeded the quota.

18

I saw that you can remove a vote to put it on another feature request, but this is not a solution.

19

It might be worth checking if the staff can reset the votes when the feature is developed, that could be pretty good

20

Normally, yes! When a feature is developed and the topic is closed, the votes are released, isn’t that the case?

If everyone votes for everything, we will have perfect equality between all features, which defeats the purpose of having a voting system.

If you’ve blown your quota, either you stop voting, or you redistribute your votes differently :slight_smile: it’s up to you to choose what you find most interesting to develop for yourself.

We can add voting credits in the future, but for now, given the fairly low number of features proposed (28 at the time of writing these lines), that means you can vote for 20% of the features, which seems coherent.