Changeset View
Changeset View
Standalone View
Standalone View
src/docs/contributor/feature_requests.diviner
| Show First 20 Lines • Show All 108 Lines • ▼ Show 20 Lines | |||||
| Setting Expectations | Setting Expectations | ||||
| ==================== | ==================== | ||||
| We have a lot of users and a small team. Even if your feature is something we're | We have a lot of users and a small team. Even if your feature is something we're | ||||
| interested in and a good fit for where we want the product to go, it may take | interested in and a good fit for where we want the product to go, it may take | ||||
| us a long time to get around to building it. | us a long time to get around to building it. | ||||
| We work full time on Phabricator, and our long-term roadmap has many years worth | We work full time on Phabricator, and our long-term roadmap (which we call our | ||||
| [[ https://secure.phabricator.com/w/starmap/ | Starmap ]]) has many years worth | |||||
| of work. Your feature request is competing against thousands of other requests | of work. Your feature request is competing against thousands of other requests | ||||
| for priority. | for priority. | ||||
| In general, we try to prioritize work that will have the greatest impact on the | In general, we try to prioritize work that will have the greatest impact on the | ||||
| most users. Many feature requests are perfectly reasonable requests, but have | most users. Many feature requests are perfectly reasonable requests, but have | ||||
| very little impact, impact only a few users, and/or are complex to develop and | very little impact, impact only a few users, and/or are complex to develop and | ||||
| support relative to their impact. It can take us a long time to get to these. | support relative to their impact. It can take us a long time to get to these. | ||||
| Even if your feature request is simple and has substantial impact for a large | Even if your feature request is simple and has substantial impact for a large | ||||
| number of users, the size of the request queue means that it is mathematically | number of users, the size of the request queue means that it is mathematically | ||||
| unlikely to be near the top. | unlikely to be near the top. | ||||
| You can find some information about how we prioritize in T4778. In particular, | You can find some information about how we prioritize in | ||||
| [[ https://secure.phabricator.com/w/planning/ | Planning ]]. In particular, | |||||
| we reprioritize frequently and can not accurately predict when we'll build a | we reprioritize frequently and can not accurately predict when we'll build a | ||||
| feature which isn't very near to top of the queue. | feature which isn't very near to top of the queue. | ||||
| As a whole, this means that the overwhelming majority of feature requests will | As a whole, this means that the overwhelming majority of feature requests will | ||||
| sit in queue for a long time without any updates, and that we won't be able to | sit in queue for a long time without any updates, and that we won't be able to | ||||
| give you any updates or predictions about timelines. One day, out of nowhere, | give you any updates or predictions about timelines. One day, out of nowhere, | ||||
| your feature will materialize. That day may be a decade from now. You should | your feature will materialize. That day may be a decade from now. You should | ||||
| have realistic expectations about this when filing a feature request. | have realistic expectations about this when filing a feature request. | ||||
| If you want a concrete timeline, you can build the feature yourself. See | If you want a concrete timeline, you can work with us to pay for some control | ||||
| @{article:Contributing Code} for details and alternatives to working with the | over our roadmap. For details, see | ||||
| upstream. | [[ https://secure.phabricator.com/w/prioritization/ | Prioritization ]]. | ||||
| Describe Problems | Describe Problems | ||||
| ================= | ================= | ||||
| When you file a feature request, we need you to describe the problem you're | When you file a feature request, we need you to describe the problem you're | ||||
| facing first, not just your desired solution. Describing the problem you are | facing first, not just your desired solution. Describing the problem you are | ||||
| facing is the **most important part** of a feature request. | facing is the **most important part** of a feature request. | ||||
| ▲ Show 20 Lines • Show All 87 Lines • Show Last 20 Lines | |||||