[HN Gopher] Phorge: Going Public
       ___________________________________________________________________
        
       Phorge: Going Public
        
       Author : RealStickman_
       Score  : 102 points
       Date   : 2022-09-17 19:54 UTC (3 hours ago)
        
 (HTM) web link (we.phorge.it)
 (TXT) w3m dump (we.phorge.it)
        
       | KerrAvon wrote:
       | I seem to be in the minority, but I found Phabricator to be a
       | very unpleasant code review experience. Because it doesn't speak
       | git natively, it would frequently just spew commits from an
       | arbitrary branch into PRs, for no apparent reason. And because
       | reviews weren't based on actual git branches, people could throw
       | patches that you couldn't actually build into it. Awful, awful
       | thing.
        
         | encryptluks2 wrote:
         | Is that different than JIRA? I always thought Phabricator was
         | just awesome as a JIRA alternative
        
           | cpeterso wrote:
           | Phabricator is a whole suite of integrated web-based software
           | development tools:
           | 
           | * Differential, a code review tool
           | 
           | * Diffusion, a repository browser
           | 
           | * Herald, a change monitoring tool
           | 
           | * Maniphest, a bug tracker
           | 
           | * Phriction, a wiki
        
         | bogota wrote:
         | You need to buy into the phab workflow which is diff based not
         | branch based. Once you accept that the experience is awesome.
         | For many people they don't understand git enough unfortunately
         | to appreciate the workflow not that it doesn't have its flaws
         | but it has worked amazingly on both large and small teams for
         | me
        
       | remote_phone wrote:
       | I loved Phabricator. It's the system that made the most sense to
       | me, with no real issues. I was shocked when I saw that no more
       | work was going to be done with it and I'm glad to see someone
       | pick it up!
        
       | yuan43 wrote:
       | So is this like an open source GitHub issues? What problem(s)
       | does it solve that can't be solved through GitHub?
        
         | encryptluks2 wrote:
         | I think you answered your own question but it does a lot more
         | than that. Did you check out the features page?
        
           | yuan43 wrote:
           | I'd like to hear from someone who has used it.
        
         | bsder wrote:
         | Given that Github is now owned by Microsoft who can pull your
         | identity or shut down your repository on a whim, being an open
         | source GitHub issues is plenty enough, no?
        
         | bogota wrote:
         | Having more than one option should be generally seen as a good
         | thing. I don't think an open source project needs to justify
         | its existence if you dont want to take the time to learn what
         | it actually does
        
       | ComputerGuru wrote:
       | It would have been nice to get some commitments from the bigger
       | Phabricator users before going public, so I could read this and
       | see oh projects x, y, and z are going to be using Phorge! But
       | maybe they wouldn't until they see what kind of project it's
       | going to turn out to be..
        
       | _mway wrote:
       | The "features of Phorge" link on https://phorge.it/ is broken: it
       | currently links to
       | https://we.phorge.it/book/phabricator/article/introduction/,
       | which is a 404 (looks like just a s/phabricator/phorge/ typo in
       | the URL).
       | 
       | Edit: actually looks several of the homepage links are broken.
        
       | skybrian wrote:
       | What is Phorge:
       | 
       | https://we.phorge.it/book/phorge/article/introduction/
        
         | mdaniel wrote:
         | And while I'm sure that documentation is handy for standing up
         | one's own Phorge, I find concrete examples to be more useful
         | 
         | Issues: https://we.phorge.it/T15034
         | 
         | Pull Request: https://we.phorge.it/D25015 (or the less
         | "Outlook-ish" view of show me the goods, _then_ I 'll know what
         | you're _talking_ about: https://we.phorge.it/D25015#toc )
         | 
         | CI: https://we.phorge.it/harbormaster/build/69/
         | 
         | and I guess a "stack overflow for teams" replacement:
         | https://we.phorge.it/Q14
        
         | Jabbles wrote:
         | "Facebook has 500+ fulltime engineers"
         | 
         | Technically true, but seems out of date...
        
       | dom96 wrote:
       | Brilliant to see this. I still miss Phabricator + Mercurial from
       | my time at Facebook, best code review experience ever.
        
       | dfee wrote:
       | Just take a look at that page.
       | 
       | Line height issues. Odd icons. Weird verbiage. Swapping 'ph' for
       | 'f'. A declaration the author is a 'User', with no projects, and
       | a "tada" token (whatever that is).
       | 
       | Phab users may feel right at home. Unfortunately.
       | 
       | Yes, my phab experience has been underwhelming and quite
       | confusing. Each piece functions nominally, but is a miserable
       | cacophony of integration. I hope the leaders of this project take
       | some creative liberties with the vision and organization. It's
       | needed - lest a full restart of this thinking take the reins.
        
       | goodoldneon wrote:
       | Good stuff! I miss Phab's task trees and stacked diffs
        
       | ferdowsi wrote:
       | Exciting stuff! Phabricator was one of the better project/dev
       | management systems I've interacted with and I'm glad to see
       | developer energy behind maintaining and improving it!
        
       ___________________________________________________________________
       (page generated 2022-09-17 23:00 UTC)