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

2014-03-28 Thread Matthew Flaschen
On 03/25/2014 12:14 PM, Andre Klapper wrote: User/reporter experience is to further discuss if we continue to want users to be able to report issues directly into the tool. Yes, I think this is required. That's the best way to get teams aware of issues (not saying I expect all users use bugtr

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

2014-03-28 Thread Matthew Flaschen
On 03/25/2014 06:31 PM, Quim Gil wrote: 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. Yes, we should think about whether this should be limited to project team members (something li

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

2014-03-28 Thread Matthew Flaschen
On 03/26/2014 01:36 AM, sankarshan wrote: Do you use keywords on the current instance of the Bugzilla? If so, how do you utilize keywords? Do you also have a definition of what each keywords signifies (eg. something similar to )? I think this is

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

2014-03-28 Thread Matthew Flaschen
On 03/25/2014 06:58 PM, Shahyar Ghobadpour wrote: Phabricator supports anonymous user access. The problem is in fact that the login page becomes the "home page" when you aren't logged in. Case in point, the Fedora Project using Phabricator with a direct link to maniphest: https://phab.qadevel.clo

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

2014-03-28 Thread Steven Walling
On Fri, Mar 28, 2014 at 7:05 PM, Luis Villa wrote: > I think the most important principle for a BTS is "it must be useful for > the developers". All other principles are subordinate. I really deeply agree with this. A bug tracker is really just a fancy to-do list for software development. The

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

2014-03-28 Thread Luis Villa
On Fri, Mar 28, 2014 at 3:42 PM, Quim Gil wrote: > > > On Friday, March 28, 2014, Luis Villa wrote: > >> >> Bugzilla/future bug tracking system, first and foremost, has to serve the >> developers by helping them figure out what to work on next. Old bugs can >> make the BTS less effective at that

[teampractices] Discussing Phabricator in Phabricator

2014-03-28 Thread Quim Gil
Here is a proposal: https://www.mediawiki.org/wiki/Talk:Requests_for_comment/Project_management_tools_review#A_Phabricator_project_to_plan_the_potential_migration_to_Phabricator Let´s discuss the PM tools RfC in the RfC, but let's start documenting all the questions and potential plans specific t

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

2014-03-28 Thread Steven Walling
On Fri, Mar 28, 2014 at 3:42 PM, Quim Gil wrote: > Have you been in a free software community where old bugs were WONTFIXed > en masse? Because Andre and me have, and at least for me it wasn't funny. I'm pretty sure no one is suggesting we do that. At least, that's not what I was proposing. -

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

2014-03-28 Thread Quim Gil
On Friday, March 28, 2014, Luis Villa wrote: > > Bugzilla/future bug tracking system, first and foremost, has to serve the > developers by helping them figure out what to work on next. Old bugs can > make the BTS less effective at that goal, by cluttering developer queries. > Have you been in a

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

2014-03-28 Thread Luis Villa
On Wed, Mar 26, 2014 at 3:34 PM, Bryan Davis wrote: > > A giant bug triage and resolve party does sound generally useful > however. It sounds exhausting as well. :) Bugzilla/future bug tracking system, first and foremost, has to serve the developers by helping them figure out what to work on ne

Re: [teampractices] [Wikitech-l] IRC Office Hour on Project Management Tools Review: Friday 28th, 17:00UTC

2014-03-28 Thread Guillaume Paumier
A quick reminder: This will take place in 30 minutes in #wikimedia-office . If all goes well, we'll even have Phabricator's lead developer around to help answer questions :) On Mon, Mar 24, 2014 at 6:53 PM, Andre Klapper wrote: > Hi, > > Guillaume and I will be hosting an IRC office hour > on Mar