djtide
Re:Ask HN: Why hasn't anyone made a mobile app for Phabricator?
on Saturday September 10, 2016 @12:11PM (#12469808)
Phabricator is built by 2 people (I am the designer half of the team) so bandwidth for a mobile app is essentially nill. It is designed & built fully responsive though, and light on the wire. You should be able to use the web version on your phone with no issues.
Re:Abandoning Gitflow and GitHub in favour of Gerrit
on Wednesday April 06, 2016 @04:54PM (#11442012)
hopefully it's slightly less clunky today, just wrapped up the semi-annual refresh this past week. Still... we have our fair share of "-isms".
Re:Ask HN: How do you review code?
on Monday April 04, 2016 @10:42PM (#11427441)
Hey Phabricator dev here, would love to see you take a better look at Phabricator as well. I'm not sure that we really "do too much" as our product is guided mostly by the tenants of code quality and developer efficiency. Specifically we feel it better to have these tools all integrated so developers spend more time just building features. Some basic overview for code review would be:
Differential - Pre commit code review
Audit - Post commit code review
Arcanist - command line, patch emitting lint, unit tests (pre commit)
Herald - Custom "business rules" for notifications (cc me on all JS diffs)
Owners - Mark code territory
Harbormaster - Continuous integration
Macro - I mean, code review with memes!
And yes, you can uninstall any application you don't want like Maniphest or Countdown, or sadly even the meme generator.
Re:Write, Review, Merge, Publish: Phabricator Review Workflow
on Sunday February 28, 2016 @12:53PM (#11191612)
We have plans to support a pure git-based workflow. See https://secure.phabricator.com/T5000
Re:GitHub lock-in?
on Saturday February 20, 2016 @10:00PM (#11143091)
We don't taking building marketing pages seriously. But the software is solid, and we're a founding partner of HackerOne.
Re:GitHub lock-in?
on Saturday February 20, 2016 @09:57PM (#11143084)
Hard to say since every tool out there moves very fast and we're just building what we think our users want. Overall my personal opinion is the "pull request" model is flawed for businesses but great for open source. Phabricator doesn't serve two masters in that regard. This means we focus more on developer efficiency and code quality. Tools like arcanist are harder to convince people to adopt, but save me personally a few hours each week. (Arcanist does pre-commit lint, unit, and patch emitting). Other tools like Herald (business actions!) and Owners (claim you own code!) are also highly useful at scale.
Our lead dev posted some explanations on how we're different than other popular choices: https://secure.phabricator.com/phame/post/view/766/write_rev...
David Cramer also publish some thoughts on the pull request model: http://cramer.io/2014/05/03/on-pull-requests
Re:GitHub lock-in?
on Saturday February 20, 2016 @09:46PM (#11143052)
Not sure what you mean, I've always billed it as an internal tools platform since it's our intent to have it do everything you need. (bugs, repo, review, kanban, wiki, chat, etc)