How does it work - feature requests đź‘Ť or down?

Ask the Community Password Manager
, ,
1

Hello,
I wonder how does it work with Feature Requests and votes. Let’s say there is a request for a feature XY with ca. 500 votes following a constructive discussion. Does it mean that this feature will be implemented sooner or later? Who decicdes what happens during the actual and following year (see Roadmap).
Or, there are 500 votes for feature XY but the “head” (?) of the developer team thinks that this feature is not needed or important enough. So it will not be implemented?
Or, if there is is an detail to fix/make better (but not a feature) - how do the developers learn about such a request? Is the “head” of the developer team (or the developers) also follow this forum?

I just wonder and would like to learn more about the structures (no details, just to get some general idea of it).

Greetings and Takk!

2

Hi @clausimausi, the Bitwarden Roadmap is driven by multiple sources, both internally and externally, with the forums serving as a place to vote and discuss ideas.

If you filter by top voted feature requests, you can see that many community suggested items have been implemented by the team.

Some community members also contribute code to the Bitwarden codebase.

1 Like
3

Thank you @dwbit for the answer.
And, just to get an impression, how many developers work on BW, probably from more or less all aorund the world? Do you also have something like a real office for e.g. accounting or so?
I am impressed how the whole BW team manages this - to work on such a great and complex software.

4

No problem! The activity on Github & Linkedn will give you a good idea. :+1: