5 ms·

Phabricator is a great alternative, by the way. Really stable and has the best code review interface / workflow I've ever used.

by lima 10y ago

ommunist 10y ago
+1 for phabricator
cookiesboxcar 10y ago
I really want to love phabricator, but the local install for a new team is so painful... any thoughts about how to make that better?
- collyw 10y ago
  Everyone is talking about installing these services. Don't they have a central hosted server like Gihub?
- Karunamon 10y ago
  I have this problem too. It's not hard to set up, there are just so many tiny pieces that need to be run by hand that it's going to take a human well over an hour to read through the docs and get it right. Someone made a Saltstack state[1] that I've used and had some success with - installing and configuring Salt from zero and using this config is still faster than installing Phabricator by hand. [1]: https://github.com/bougie/salt-phabricator-formula https://github.com/bougie/salt-phabricator-formula
  - lima 10y ago
    It's actually much easier to setup and operate than GitLab with its massive dependencies. Also a lot faster.
    - Karunamon 10y ago
      Gitlab is unfortunately a pig, in the large and bloated sense of the term. Which is really sad! I love the app, it looks better than Phabricator and does so much more, but then I can throw Phabricator on the same droplet I use for plenty of other stuff with resources to spare for $5/month, where Gitlab would require a dedicated $10 instance just due to memory usage alone. Guess I'm just not the target audience :(
      - brodock 10y ago
        You can use gitlab.com for free... don't need to install it in your own box.
    - jobvandervoort 10y ago
      Setting up GitLab can be done through our repositories quite easily nowadays. It boils down to: apt-get install gitlab-ce
    - cookiesboxcar 10y ago
      I'm talking specifically about the client tool arcanist, which IMO is the real benefit of Phabricator
- segmondy 10y ago
  Package it as a docker container.
cm3 10y ago
If only phab didn't insist on squashing a patchset into a phabricator-commit, losing the carefully created history of a branch. Cumulative mega-patches are of little use when bisecting or trying to understand how a change works by being able to follow the steps to reach the final diff. A good commit history with separate commit messages explaining the diffs goes much further in allowing someone else to understand a change than any code comment could. This is also why merge commits are useful, because they allow you to group the commits for a feature branch and not miss any of the commits involved. Phabricator could easily include their metadata in a merge commit, instead of collapsing the branch into one mega-commit. I know some people love a flat history without merge commits, but those lose a lot of info available with a graph/tree visible when there are no forward merges.
- lima 10y ago
  You can disable the squashing. It's a common complaint. https://secure.phabricator.com/book/phabricator/article/arcanist_new_project/#history-mutability https://secure.phabricator.com/book/phabricator/article/arca... > Phabricator could easily include their metadata in a merge commit And this is what happens :-)
  - cm3 10y ago
    Thanks for the link. As arcanist is the php-based client to speak to Phab, does this mean it's a user setting only and is fully respected by Phab, meaning it's something set on first publishing of a diff and kept in that setting? Is this also possible when submitting a diff via the web interface? What's funny is that mutability didn't exist for Mercurial support because when it was written Mercurial had no official mutability feature. And I can only suppose mutability being default for git support is because of Facebook's dev style. It's wrong to assume that those who want merge commits for the final merge onto master do not rebase locally before sending a pull request. Rebase is a standard tool for working on your branch (aka patch set aka patch queue) and it's normal to rewrite it upon each revision of the branch sent for review. Does phab support multiple revisions of a branch in one diff or does it require separate diff tickets? This is something that Gerrit got right, allowing one to see the diff between revisions of a branch (patchset).
tedmiston 10y ago
Have not used them, but I really appreciate how their copy is written to appeal to devs. Ex: Customizable Task Management Plan features, track bugs, and award tokens. Maniphest lets you customize input forms, use custom fields, and has a rich API. Keeps track of lots of bugs. You can assign them to people. Maybe you could fix them, eventually. (optional) Build unique task forms for every department. For example, look at this feature in Phabricator itself: T6526 - Business Rules As your company scales, keep track of activity with Herald, which notifies you when things you care about happen (like a specific file being changed). Write business rules. Everyone loves business rules. Keep an eye on suspicious new hires. Warns you about plotting and scheming. Build triggers on tasks, commits, revisions, and more.

Phabricator is a great alternative, by the way. Really stable and has the best code review interface / workflow I've ever used.

by lima 10y ago

Phabricator is a great alternative, by the way. Really stable and has the best code review interface / workflow I've ever used.

ommunist 10y ago

+1 for phabricator

cookiesboxcar 10y ago

I really want to love phabricator, but the local install for a new team is so painful... any thoughts about how to make that better?

collyw 10y ago
Everyone is talking about installing these services. Don't they have a central hosted server like Gihub?
Karunamon 10y ago
I have this problem too. It's not hard to set up, there are just so many tiny pieces that need to be run by hand that it's going to take a human well over an hour to read through the docs and get it right. Someone made a Saltstack state[1] that I've used and had some success with - installing and configuring Salt from zero and using this config is still faster than installing Phabricator by hand. [1]: https://github.com/bougie/salt-phabricator-formula https://github.com/bougie/salt-phabricator-formula
- lima 10y ago
  It's actually much easier to setup and operate than GitLab with its massive dependencies. Also a lot faster.
  - Karunamon 10y ago
    Gitlab is unfortunately a pig, in the large and bloated sense of the term. Which is really sad! I love the app, it looks better than Phabricator and does so much more, but then I can throw Phabricator on the same droplet I use for plenty of other stuff with resources to spare for $5/month, where Gitlab would require a dedicated $10 instance just due to memory usage alone. Guess I'm just not the target audience :(
    - brodock 10y ago
      You can use gitlab.com for free... don't need to install it in your own box.
  - jobvandervoort 10y ago
    Setting up GitLab can be done through our repositories quite easily nowadays. It boils down to: apt-get install gitlab-ce
  - cookiesboxcar 10y ago
    I'm talking specifically about the client tool arcanist, which IMO is the real benefit of Phabricator
segmondy 10y ago
Package it as a docker container.

cm3 10y ago

If only phab didn't insist on squashing a patchset into a phabricator-commit, losing the carefully created history of a branch. Cumulative mega-patches are of little use when bisecting or trying to understand how a change works by being able to follow the steps to reach the final diff. A good commit history with separate commit messages explaining the diffs goes much further in allowing someone else to understand a change than any code comment could. This is also why merge commits are useful, because they allow you to group the commits for a feature branch and not miss any of the commits involved. Phabricator could easily include their metadata in a merge commit, instead of collapsing the branch into one mega-commit. I know some people love a flat history without merge commits, but those lose a lot of info available with a graph/tree visible when there are no forward merges.

lima 10y ago
You can disable the squashing. It's a common complaint. https://secure.phabricator.com/book/phabricator/article/arcanist_new_project/#history-mutability https://secure.phabricator.com/book/phabricator/article/arca... > Phabricator could easily include their metadata in a merge commit And this is what happens :-)
- cm3 10y ago
  Thanks for the link. As arcanist is the php-based client to speak to Phab, does this mean it's a user setting only and is fully respected by Phab, meaning it's something set on first publishing of a diff and kept in that setting? Is this also possible when submitting a diff via the web interface? What's funny is that mutability didn't exist for Mercurial support because when it was written Mercurial had no official mutability feature. And I can only suppose mutability being default for git support is because of Facebook's dev style. It's wrong to assume that those who want merge commits for the final merge onto master do not rebase locally before sending a pull request. Rebase is a standard tool for working on your branch (aka patch set aka patch queue) and it's normal to rewrite it upon each revision of the branch sent for review. Does phab support multiple revisions of a branch in one diff or does it require separate diff tickets? This is something that Gerrit got right, allowing one to see the diff between revisions of a branch (patchset).

tedmiston 10y ago

Have not used them, but I really appreciate how their copy is written to appeal to devs. Ex: Customizable Task Management Plan features, track bugs, and award tokens. Maniphest lets you customize input forms, use custom fields, and has a rich API. Keeps track of lots of bugs. You can assign them to people. Maybe you could fix them, eventually. (optional) Build unique task forms for every department. For example, look at this feature in Phabricator itself: T6526 - Business Rules As your company scales, keep track of activity with Herald, which notifies you when things you care about happen (like a specific file being changed). Write business rules. Everyone loves business rules. Keep an eye on suspicious new hires. Warns you about plotting and scheming. Build triggers on tasks, commits, revisions, and more.