Page MenuHomePhabricator

Write a document describing the classes of changes we build/accept in the upstream
Closed, ResolvedPublic

Description

Write something like T4778 but focused on the "What".

Initial text split off T4778, quoted from chad and epriestley:

​Is upstream Phabricator for me?​

​It's useful to remember that Phabricator is not targeted at consumers or the pub​lic at large. It is targeted at professionals in software fields and adjacent fi​elds. Product and prioritization decisions we make in the upstream reflect that.

Nuance is our future p​roduct intended to let installs interact with common folk (for issues) anywhere​ on the web.

​Local patches and forking are what we're currently recommending to teams who fee​l the defaults or how Phabricator works for their team or use case are not corre​ct. We are not offended by this, we ship what we call "Vanilla Phabricator" whic​h is set up for a very agile, lean, "open", and likely smaller company and we un​derstand it won't meet every installs needs. But there isn't any reasonable way​ we can take every installs wishes into the upstream and still be able to move fo​rward/maintain it off of three people.

Tips for proposers

Even when your proposal certainly isn't unreasonable, you can make it more bite​-sized and defined to improve its chances. Smaller proposals are easier to implement and less likely to cause problems, as follows.

​Phabricator covers a lot of ground with many different applications. Obviously s​ome things make sense, so they do get added if we feel it's something that many ​installs will benefit from. In any 'feature request' situation we weigh the like​ly usefulness across all installs.

​Any feature incurs both development time upfront and support/documentation/upkee​p after. We are fairly picky about what hits the upstream because it's our time ​on the line. The number of one-off requests for features/options we get is fairl​y large.

Event Timeline

nemobis created this task.Oct 19 2014, 2:03 PM
nemobis assigned this task to epriestley.
nemobis raised the priority of this task from to Needs Triage.
nemobis updated the task description. (Show Details)
nemobis added a project: Guides.
nemobis updated the task description. (Show Details)
nemobis added a subscriber: nemobis.
epriestley renamed this task from Write a "When feature may get built, or bug get fixed?" to Write a document describing the classes of changes we build/accept in the upstream.Oct 19 2014, 2:08 PM
epriestley triaged this task as Wishlist priority.

Thanks for taking the time to write it down, that's very useful.