[teampractices] Project management tools review: Regressions/tradeoffs; migration

[Quim Gil]

On Tuesday, March 25, 2014, Andre Klapper
<aklapper at wikimedia.org<javascript:_e(%7B%7D,'cvml','aklapper at wikimedia.org');>>
wrote:
>
> User/reporter experience is to further discuss if we continue to want
> users to be able to report issues directly into the tool.
> If we don't want, we'd need to discuss with CLs how to support other
> feedback channels properly for the community.
>

Is there a reason to change the current workflow in Bugzilla, where any
registered user can create new reports (now tasks) and also comment on
existing reports/tasks?

What are the options when it comes to permissions to edit tasks in
Phabricator? This relates to the discussion about who decides the
prioritization of a task. Also, Bugzilla's "Comment #0" is now part of the
task and is editable (yay!), and there might be reasons to protect that.

All in all it looks like we could set a wiki-like approach: everything is
editable by default, edit wars or equivalents to vandalism might lead to
protection levels. (I haven't checked Phabricator's documentation and I
have no idea how feasible this is now.)


I obviously still need to do more homework by reading docs and playing
> more, but for example:
> * Can we set up Phabricator *by default* to allow read access to tickets
> ("Visible to: Public (No Login Required)")?
>

This is a must. We can't start populating Village Pumps, mailing lists,
etc, with URLs that require signing in to be accessed at all.


-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wikimedia.org/pipermail/teampractices/attachments/20140325/370f5f37/attachment.html>