It is everybody's interest that Phabricator upstream maintainers put their attention and resources in the tasks and patches that matter most to Wikimedia. The better we prioritize our feedback and contributions upstream, and the better we play by their rules, the more effective our collaboration will be.
* «features which are aimed at a different group of users (like students, casual projects, or inexperienced computer users) may be harder to get upstreamed» etc. https://secure.phabricator.com/book/phabcontrib/article/feature_requests/
* Any task landing in #phabricator.org must go through the //Need Discussion// phase and be moved to //Ready To Go// only when there is consensus.
* It is fine to Decline tasks that we don't think that should be pushed as Wikimedia requests upstream.
**Use of the [[ https://secure.phabricator.com/tag/wikimedia/ | #Wikimedia ]] project upstream**
* Only tasks placed in //Ready To Go// or //Reported Upstream// in #phabricator.org can be associated with the [[ https://secure.phabricator.com/tag/wikimedia/ | #Wikimedia ]] project upstream.
* The Wikimedia Phabricator team maintains the #Wikimedia workboard upstream. In case of doubt they can add or remove related tasks.
* Only the Phabricator maintainers decide the priorities of these upstream tasks, not us.
* This process and the upstream policies for external contributions need to be documented at https://www.mediawiki.org/wiki/Phabricator/Code
**Contributions at your own risk**
* Individuals can always push their own feedback and patches upstream, without using the #Wikimedia tag. In this case, they are on their own, out of the #phabricator.org process.