Phabricator
討論議程 agenda
People / Tasks / Projects
- filing task
- following tasks
- creating project
workboard
default backlog e.g. development project
Current using facebook + google drive + telegram + hackpad
Q1 - why not use meta
answer -
Andre: phabricator has tasks, it's like a page on media wiki. Project is like namespace. Also you can querry, and overview board. Nothing similar in media wiki.
Erica: no alternative in MediaWiki to collect and automatic categorize information. you can also use mediawiki, but if you switch to Phabricator, it will save manual work.
Q2 - a tool for working progress report
Answer -
Andre : Not currently. https://www.mediawiki.org/wiki/Phlogiston
Erica : visual editor team had some graph for the team.
Q3 - About i18n, we know this is important for a local chapter. I think we can help to translate. How and where can I to help the handle issue?
sry a little mistake. "help to handle the issue"
Answer -
Andre : Translation is possible, but it is rough and it does not use translatewiki.net. Our task is https://phabricator.wikimedia.org/T225 and the Phabricator maintainers (a different company) deal with that in https://secure.phabricator.com/T5267
What is currently possible is described in https://secure.phabricator.com/book/phabcontrib/article/internationalization/
Erica : It's annoying, but the people who needs to understand the whole interface, it's the project managers. Normal people who write the tasks only need the essential elements. You can create a simple task or advance task to demonstrate.
Question - slack and trello combination. Can this work
Answer -
Andre - IRC has a bug notification that you can receive. I am not aware of slack api, currently maybe not. But if you are interested that, I recommend you to the bug.
Erica - Only in phabricator now, not on Wikimedia sites, but if you really want, you can add notification by email. The only objection of trello is that it's different
Question - how about start a project of grant making in WMTW?
Answer -
Andre : if only 1 or 2 tasks, maybe not necessary. But if 10 to 20 tasks.
Erica : Try to create a test phabricator, play a bit with that https://phab-01.wmflabs.org/ it's like a sand box of phabricator. You can assign
Question - tags of project
Answer -
sprint tag is the past now.
test 版本的 phabricator https://phab-01.wmflabs.org/
一是Erica Litrenta ，義大利人，現在在維基媒體金會的社群互動部門的技術合作團隊擔任社群聯繫員[1]；另外一位是Andre Klapper ，也住在歐洲，現在Phabricator的總機先生，任何新的task進到phabricator幾乎都會看到他在執行標籤與triage的工作[2]。
下面這些參考資料是 Erica 之前發給我參考的，我今天下午看完後，會在hackpad簡短做個中文摘要，讓大家有點準備，如果有什麼想到的問題或者是發想的概念，也歡迎隨時提出喔！
會後建議
參考頁面
- 維基媒體部落格《 On our way to Phabricator 》 2014-06-10, Guillaume Paumier
- 正在建立 Phabricator 的 learning pattern ( T133268 ).
- MediaWiki上的參考手冊
- 為什麼要用 Phabricator來管理你的專案？ / Why use Phabricator for managing your project?
- 任務/ Tasks
- 任務的範疇 / Scope of tasks：一個任務應該是一項能夠讓單人能夠在一次iteration（大約兩週）就可以完成的工作，否則應該要用子任務（subtask）來細分，可以用epic來描述要花三個月以上的任務、release來描述要發佈新的版本
- 無效任務 / Invalid tasks：如果任務敘述無法針對其進行任何行動（例如：沒有結束可能的工作、使用說明、或是不具體的抱怨），就會被歸類為無效任務。
- 請用直白的語言、清楚定義行動、以及預期的結果 / Use plain language, define actions and expected results
- 指派任務 / Assigning tasks：分配給會做這個任務的人，不要派給自己如果知道自己不會在短期內做這件事情。
- 設定任務優先順序 / Setting task priorities
- 優先順序級別 / Priority levels
- 不要派給一個人太多高優先順序的任務 / Limiting high priority tasks assigned to a single person
- 將任務與計畫連結 / Associating tasks with projects
- 還無法進行的任務 / Tasks that cannot be worked on yet
- 任務結案 / Closing a task
- 參見 / See also：臭蟲回報循環
- 建立任務創建與編輯的客製化表單 / Creating custom forms for Task Creation and Editing
- 計畫 / Projects
- 計畫類型 / Types of Projects
- Component is the default option. A component corresponds to a distinct and recognizable piece of software/service. Creation must be documented. Icon+Color: Briefcase+Blue.
- Group (formerly Team) corresponds to an existing team. If you belong to a group that will manage several projects, then the first step is to create a Project for your group. Creation must be documented. Group Projects can be automatically added to (sub)component tasks by requesting a global Herald rule. Icon+Color: Group+Violet.
- Sprint is for sub-projects of a team being worked on in a certain time frame. Specify the start and end dates when requesting creation of a new Sprint Project. Icon+Color: Timeline+Green.
- Release is for sub-projects that belong to a specific deployment defined by a date or a (future) software version. Icon+Color: Release+Orange. See #"Tracking" Tasks below
- Goal can be used for Projects without a defined ending date but which can be definitely realistically be defined as finished at some point. Creation must be documented. Icon+Color: Goal+Orange.
- Tag is used as a cross-component keyword (like "accessibility"), a "never-ending" project. Tags must be proposed and discussed before being created. Icon+Color: Tag+Yellow
- Meta projects are used to tag code repositories with special behaviors and workflows. These behaviors are triggered by custom Herald rules. See task T128161. Icon+color: Tag+Grey.
- ACL projects are used to enforce policy restrictions, especially for Spaces. This type should be used instead of locking down normal projects such as Teams, so that anyone may still join and watch such Team projects without that giving them restricted access. Creation of such a project or a related Space must be proposed and discussed before being created. See T90491. Icon+Color: Policy+Red.
- Personal per-user Projects allow to track progress of personal tasks. They currently are a test only, see T555. Creation must be documented. Icon+Color: Accounting+Checkered.
- Umbrella Projects can be used for larger Projects that do not have a distinct code base and that consist of several (sub)components. Umbrella Projects can be automatically added to (sub)component tasks by requesting a global Herald rule. Creation must be documented. Icon+Color: Umbrella+Blue.
- The special Patch-For-Review project is automatically added to a task when a related patch in Gerrit links to that task.
- 母計畫、子計畫、以及里程碑 / Parent Projects, Sub-projects and Milestones
- 計畫的創建/重新命名/存檔 / Creating/renaming/Archiving projects
- 將計畫歸檔 Archiving a project：在Phabricator計畫是無法刪除的
- Boards
- Columns
- Typical uses of workboards
- Examples
- Tips for forcing multiple columns to fit in the window
- 4.3 Maintaining Boards
- 5 Implementing Common Practices in Phabricator
- WMUA has a few slides about using Phab: https://meta.wikimedia.org/w/index.php?title=File:WMUA._Growth_of_a_small_chapter_to_a_successful_one.pdf&page=32 ; you can see an example of Phab being used in a language which is not English at https://phabricator.wikimedia.org/project/view/1630/ ; WMSE is using it for the Wikispeech project among other things - https://phabricator.wikimedia.org/project/view/1978/ (one of the people working there followed my presentation in Berlin, project was founded after the event) ; WMDE is using it for several projects, and you can find them listed at https://phabricator.wikimedia.org/project/query/active/?after=1760 .