I want to volunteer to take this on in the next TPG cycle (starting 6/25/15). If anyone is subscribed to this task, please add any known wiki pages regarding phab. I will be linking the ones I know as well.

here is one:
https://www.mediawiki.org/wiki/Phabricator/Help#Searching_for_items

In T98521#1382938, @DStrine wrote:

please add any known wiki pages regarding phab

We have centralized documentation: https://www.mediawiki.org/wiki/Category:Phabricator
(and https://wikitech.wikimedia.org/wiki/Phabricator is just technical aspects)

The bottom of the tips page lists the dozen or so WMF phab doc pages I'm aware of.

Thanks for taking this on David!!!

TPG Tea Time
2015-07-02

Special Guest Andre Klapper!
Phabricator Roles and Responsibilities:

(David will merge this with existing Phab documentation (which in turn is yet to be fully merged))

• everyone in foundation, as users
  • bug and task tracking
  • Release Roadmapping (deprecated) <- Greg G
  • Track Goals (experimental)
  • project management
    • task lists, backlogs
    • forecasting (burnups, etc)
    • personal task tracking (Spaces)
  • Diffusion
  • long run: gerrit (code merges (Zuul, etc))
• mukunda (RelEng) is responsile for deploying new versions and maintaining customizations (eg security restrictions)
• wm-de are maintaining phragile, to supersede Sprint extension in the long run
• sprint extension developed by Christopher, WMDE contractor; upstream has their own agenda
  • Constraints on submitting to Phabricator upstream:
    • has specific vision for Phabricator, which limits patch acceptance
    • consider maintenance burden
  • Also see https://www.mediawiki.org/wiki/Phabricator/Code
• Andre: bug wrangler (quality of all bugs)
• Strine has ideas on expanding advanced search options
• TPG should probably get an update on phragile
• TPG wants to use the API. Who do we talk to for more info?

• Types of Projects: https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Type_of_project

I'm making final change notes here:

https://docs.google.com/a/wikimedia.org/spreadsheets/d/1pSjTK4_Ups92pvEADkPv8pAg002UrymaixiL6Xg-lrk/edit?usp=sharing

Once these changes are complete, I will write out a table in this ticket to record what has been changed.

I feel like I have completed our last round of notes:
https://etherpad.wikimedia.org/p/proposed_edits_on_phab_wiki_pages

I have also noted all the changes here:
https://docs.google.com/spreadsheets/d/1pSjTK4_Ups92pvEADkPv8pAg002UrymaixiL6Xg-lrk/edit#gid=0

I think this is pretty much done. I'm adding a separate "move pages" task to the backlog: https://phabricator.wikimedia.org/T109718

This task is resolved but https://www.mediawiki.org/wiki/Team_Practices_Group/Phabricator_tips still says

NOTE: This page is a sandbox. Once the content is developed enough to be usable, it will be copied, merged, folded, or migrated over to one or more of the existing WMF Phabricator documentation pages

So one of that is wrong. Should that line be removed from the wikipage and the wikipage should have some "outdated / only for historical reasons" banner on top?

I'd like to avoid people looking at several pages for the same info and even more people having to update several pages for the same info, as software functionality evolves.

@DStrine is in the best position to decide. My guess/hope is that all the contents of the tips page have now been incorporated in the main docs, and that this page can either be marked as deprecated/archive, or perhaps cleared and changed to a redirect.

What would happen to the sub pages if this page was deleted? Is that an option?

I think a redirect would be better, in case anyone has it bookmarked.

@ksmith and I worked it out. the page has been cleared out and redirects to the /help page.

Thank you!