Talk:Project management tools/Review/Options

Other criteria
Possible other criteria : guillom 11:56, 24 February 2014 (UTC)
 * Cost: difficult to assess. Hosted tools for which we pay a fee are easy, but self-hosted tools that we need to maintain also have a cost. Tools scattered across the Wikimultiverse also have a cost.
 * Programming language: For FOSS tools, the language(s) they use will influence our ability to fix / tweak / expand functionality to serve our needs.


 * I've added the languages I could figure out. guillom 13:20, 24 February 2014 (UTC)

Scrumbugz
This one has all of the outward appearances of a poor choice. It's difficult to evaluate the user interface based on the website, and the project hasn't seen a commit in four months. I somehow doubt that's because they're "done". :-) Does anyone find this option at all interesting? -- RobLa-WMF (talk) 16:31, 4 March 2014 (UTC)

GitHub
While I've expressed interest in Phabricator for having enjoyed working with it in the past, I didn't realize that GitHub covered our needs in terms of continuous integration, etc. With that in mind, and since working with GitHub on open source projects has always been a pleasant experience, I think that GitHub has an undeniable advantage: we would have more 3rd-party contributions on GitHub than we would with any solution we host ourselves.--GDubuc (WMF) (talk) 08:49, 4 March 2014 (UTC)
 * Operations is not likely to be excited about deploying to the prod cluster from a repository that is not entirely under our control. I talked to GitHub a couple of years ago about auditability of their hosting and was told that the SaaS hosted version did not support security audits. They recommended their "Enterprise" product which is a VM image that is hosted internally by an implementing organization. GitHub being non-free (libre) seems like a large drawback. When we find things that don't work well for us there (when, not if), we will be at the mercy of the GitHub team to correct the problems. --BDavis (WMF) (talk) 15:58, 4 March 2014 (UTC)

I think GitHub should be out of scope for this conversation. It doesn't really address the project management issue, and its issue tracker requires a non-WMF account. It *might* be ok to ask our developers to sign up for an account on an outside service, but asking site readers and editors to sign up for a GitHub account to file a bug is a non-starter. Whether we use it for repo management is a separate conversation (probably still not likely, but a more interesting conversation nonetheless). -- RobLa-WMF (talk) 16:19, 4 March 2014 (UTC)

Phabricator
I think that in terms of FOSS solution, this is as good as it gets at the moment. I'd lean towards Phabricator over GitLab because the foundation has much more PHP expertise than Rails. After all the foundation could have improved gerrit to make it more tolerable, but didn't, probably because of unfamiliarity with Java. We would definitely have to contribute code to Phabricator, because some features in beta need improvement, but their team is very helpful and responsive to contributions. Taken as-is, though, it's definitely much more basic and rougher around the edges than GitHub for some features.--GDubuc (WMF) (talk) 09:00, 4 March 2014 (UTC)
 * +1 to this. After seeing how far Phabricator has come in the past couple of years, I'm pretty excited about it.  Regardless of whether we migrate to it for repo management, it would seem to work well as an issue tracker.  The project management tools are still a bit basic, but seem to be heading in the right direction, and I think we can realistically expect that they will be solid in a year or two (especially if we help them along).  Of the FOSS options out there, this seems the most viable. -- RobLa-WMF (talk) 16:10, 4 March 2014 (UTC)