archive/phabricator
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

Update a couple of links in "Feature Requests" documentation

Browse Source 
Summary:
These are a little out of date:

  - Link to Starmap since it explicitly exists now.
  - Link to "Planning" instead of the old task.
  - Link to "Prioritization" instead of telling anyone to build stuff themselves.

Test Plan: Read documentation.

Reviewers: chad

Reviewed By: chad

Differential Revision: https://secure.phabricator.com/D14328
This commit is contained in:
epriestley
2015-10-24 08:13:28 -07:00
parent 1582bb54f6
commit b3d8ea88ec
1 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
src/docs/contributor/feature_requests.diviner
View File

@@ -114,7 +114,8 @@ 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.
@@ -127,7 +128,8 @@ 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.
@@ -137,9 +139,9 @@ 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