TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Phacility is winding down, Phabricator no longer actively maintained

269 点作者 carwyn将近 4 年前

34 条评论

nine_k将近 4 年前
To clarify: this applies not just to phabricator-dot-com, but Phabricator the software: <a href="https:&#x2F;&#x2F;github.com&#x2F;phacility&#x2F;phabricator&#x2F;commit&#x2F;9ceb66453501d461800617b9fb2d4af4ba2c9514" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;phacility&#x2F;phabricator&#x2F;commit&#x2F;9ceb66453501...</a><p>This is unexpected. Many companies, among them as well-resourced as Facebook, use Phabricator. I wonder if it will be forked soon by some party interested in keeping it around. OTOH it looks like none such party exists, because the public sources have not been updated literally for years. Maybe everyone interested just runs their private fork :(<p>Phabricator should be reasonably easy to self-host anyway.
评论 #27328692 未加载
评论 #27329004 未加载
评论 #27328732 未加载
评论 #27328822 未加载
ferdowsi将近 4 年前
Whoa. Really, really disappointed about this. The Phabricator approach to reviews and merges was incredibly impactful on a previous team. It encouraged discipline and an informative main branch that was always linked to reviews, and free of commits like &quot;fixing lint errors&quot; and &quot;actually fix lint errors, for real&quot;. <a href="https:&#x2F;&#x2F;secure.phabricator.com&#x2F;book&#x2F;phabflavor&#x2F;article&#x2F;recommendations_on_revision_control&#x2F;" rel="nofollow">https:&#x2F;&#x2F;secure.phabricator.com&#x2F;book&#x2F;phabflavor&#x2F;article&#x2F;recom...</a><p>The task management system isn&#x27;t bad either, considering how weak Github&#x27;s is and how bloated JIRA is.
评论 #27329932 未加载
bogota将近 4 年前
I got to meet evan once when i was in SF and he was awesome to hang out with im curious what he is going to be up to next. Phabricator was one of a few pieces of software that actually brought me joy when using. I will always miss the diff review process now that my current company is moving from phabricator to github and i’ll be unlikely to ever use it at a company again with this update.<p>Thanks Evan for all the work you have put in over the years. Some of my biggest learnings as an engineer have been from reading and interacting with you on the phabricator secure server and reading your code when extending phab for companies.
20after4将近 4 年前
Phabricator has been a huge part of my career. Having spent the past 11ish years maintaining phabricator installs this really hit me hard. Fwiw phabricator is very stable and maintainable code. I would be happy to work with anyone who is interested in collaborating on a community maintained fork.
评论 #27331353 未加载
评论 #27335585 未加载
评论 #27332098 未加载
saurik将近 4 年前
Phabricator had seemed to be the only good product in this space when I had looked; what are people even using instead? (I guess they just put up with GitHub :&#x2F;.)
评论 #27328640 未加载
评论 #27328974 未加载
评论 #27332256 未加载
评论 #27329655 未加载
评论 #27328765 未加载
评论 #27329534 未加载
franciscop将近 4 年前
Contrary to the other comments in this thread, I&#x27;ve had a bad experience with Phabricator. With other solutions like Github, you can commit or create a PR straight on the website easily. This makes things like fixing typos in the README a joy, where everyone technical or not can participate.<p>Github is also well known and has issues, PRs and a CI all integrated into one, while with Phabricator each of these are either a self-host Jenkins (again, friction) or in a totally different&#x2F;confusing location.<p>It&#x27;s sad to see a tech company that many liked go, but hopefully this means the higher ups will reconsider Phab usage in my company :)
评论 #27332505 未加载
kuba-orlik将近 4 年前
What I really like about Phabricator as a review tool:<p>* keyboard shortcuts to navigate through the changes<p>* ability to add a comment to multiple lines of code<p>* ability to suggest changes inline<p>* comments are saved as I type them, so an accidental tab close saves my work<p>* comments are submitted in batches when I choose to, not one-by-one after saving each one. Its&#x27;s sooo useful, because it often happens that I ask a question about some piece of code and upon further reading I find the answer, so I can delete the question before submitting all the comments and the author won&#x27;t be bothered by it<p>If anyone knows of a feview tool with similiar set of features, please please let me know :)<p>When it comes to task management in Phab, I like how the tasks can be arranged in a dependency tree. We have our &quot;todo&quot; view set up so it only shows tasks without dependencies and sorted by prioroty, so the work on the project self-organizes
评论 #27331907 未加载
评论 #27333032 未加载
评论 #27334439 未加载
评论 #27332568 未加载
abbe98将近 4 年前
I always had a good experience with Phabricator, especially its customization&#x2F;dashboards.<p>Wikimedia still uses it[1].<p>[1]: <a href="https:&#x2F;&#x2F;phabricator.wikimedia.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;phabricator.wikimedia.org&#x2F;</a>
评论 #27329225 未加载
kaendfinger将近 4 年前
I contributed to Phabricator a few times, and Evan was a pleasure to work with. I&#x27;m sorry to see it go but I hope for the best for Evan. I really hope this is a goodbye on to something great.<p>Phabricator will hold a great place in my heart as software written by a developer for developers that is well thought out, dog-fooded to the max, and fun.<p>My hope is that it can be well stewarded by a company into continuity. I wish I had the time to do so.<p>In short, thank you Evan and all those in the community for many years of wonderful software development.
twalla将近 4 年前
It&#x27;s interesting to see so many people with positive experiences with Phabricator - I work somewhere with a Phab install and onboarding new employees who&#x27;ve only ever used github&#x2F;gitlab and branching workflows incurs a _significant_ cost. That, coupled with conduit being frustrating to develop against and lots of nice open source tooling basically being unusable without heavy modification due to assuming you&#x27;re using a branching workflow has soured me on Phab. I&#x27;m hoping this can be used as additional justification to push us towards ... well... anything else. That being said, Herald is awesome and compared to basically any &quot;modern&quot; replacement, the UI is actually snappy and things don&#x27;t get moved every 6 months for no goddamn reason (thanks Atlassian)
carwyn将近 4 年前
Slightly more here: <a href="https:&#x2F;&#x2F;secure.phabricator.com&#x2F;w&#x2F;changelog&#x2F;2021.22&#x2F;" rel="nofollow">https:&#x2F;&#x2F;secure.phabricator.com&#x2F;w&#x2F;changelog&#x2F;2021.22&#x2F;</a><p>Shame, the code review was good and one of the few that supported task dependencies :(
01100011将近 4 年前
Too bad. Phabricator was a great tool for handling various aspects of a software project(SCM integration, task tracking, messaging, code reviews, etc). I used it on a couple of projects and it seemed to work very well.
wilsonthewhale将近 4 年前
As others have mentioned, this is a shame. I found the Phabricator review model much more flexible and easy to work with than GitHub and Github-clone workflows.<p>It&#x27;s basically the traditional ultra-scalable mailing-list + patches workflow, but with very nice tooling and UI on top.<p>I&#x27;m going to miss it when I leave FB some day.
评论 #27330252 未加载
thrower123将近 4 年前
I&#x27;ve always enjoyed the Phabricator landing page, because it looks like a joke.<p>&gt; Pre-Commit Code Review<p>&gt; Review others&#x27; code with Differential, because they can&#x27;t be trusted.<p>&gt; Shows code so you can look at it.<p>&gt; Leave helpful comments and anecdotes.<p>&gt; Challenge the intern&#x27;s test plan.<p>&gt; Gently place bad code back in the author&#x27;s queue.
评论 #27330006 未加载
评论 #27329203 未加载
geuis将近 4 年前
Phabricator is used at some very large companies like Pinterest. It’s easily the best general purpose tools of its kind I’ve used. I won’t be surprised if management gets picked up by someone soon.
Aeolun将近 4 年前
This post about shuttering operations is quite devoid of reasons. I can’t imagine customers would be happy about that.
评论 #27329969 未加载
aseipp将近 4 年前
Really sad. Phabricator is excellent and IMO unmatched by other tools, even today, and Evan&#x27;s sharp eye for design decisions was really inspiring to me. 10 years is a good ride, though.<p>Evan, if you&#x27;re reading this and I&#x27;m ever in San Francisco soon, I&#x27;ll have to buy you lunch!
andrewmcwatters将近 4 年前
Man, in my opinion, in software, things don&#x27;t really get started until after surviving for about 10 years or so. Everything else is fleeting.<p>Quite nice to see it saw 11 years, though.
ZuLuuuuuu将近 4 年前
Is there a summary of why this product is not maintained anymore? From time to time I would hear about Phabricator, but I didn&#x27;t know that the project was in trouble.
评论 #27329454 未加载
评论 #27328754 未加载
justinzollars将近 4 年前
I&#x27;m pretty sad about this. I hate Jira. Phabricator was pretty nice.
quadrifoliate将近 4 年前
Phabricator-the-software is a really good tool for code reviews and lightweight task management.<p>It&#x27;s used at my current workplace (self-hosted) for both. We aren&#x27;t big enough to effectively take over maintenance – but I hope someone does. It would be a shame for it to be replaced by 10 other tools that reimplement the same features poorly.
评论 #27343215 未加载
shaneos将近 4 年前
For you fans of Phabricator macros, you can still get your meme hit on GitHub using <a href="https:&#x2F;&#x2F;gitme.me" rel="nofollow">https:&#x2F;&#x2F;gitme.me</a> !
user5994461将近 4 年前
I find the announcement confusing. Is the company shutting down?<p>Existing instances will continue running &quot;indefinitely&quot;. How can a company be shutdown and promise to run forever at the same time?<p>How does this affect phabricator on premise and phabricator online?<p>The 1st of June is tomorrow, today is a week end. This is a zero day notice for users, including paying users. Hope you weren&#x27;t planning to start a new project on Monday. Ouch.
评论 #27333558 未加载
ofrzeta将近 4 年前
We&#x27;ve been using Phabricator for several years and just recently started to use Gitlab in parallel. One of the main reasons was Phabricator&#x27;s confusing and esoteric use of &quot;spaces&quot; for access control that made it hard to include external developers on projects. On the other hand the Phabricator GUI is much less confusing than Gitlab.
评论 #27331042 未加载
codeapprove将近 4 年前
That&#x27;s a shame, heard only good things about those tools.<p>Shameless but timely plug: I&#x27;m building a much better code review tool for teams on GitHub. Check out <a href="https:&#x2F;&#x2F;codeapprove.com" rel="nofollow">https:&#x2F;&#x2F;codeapprove.com</a> and if you&#x27;re interested to hear more just email me (sam at habosa dot com).
评论 #27328824 未加载
IshKebab将近 4 年前
I wonder if this will be good for Phabricator. The commercialisation &#x2F; support model made it basically impossible to contribute code to (or at least enough of a pain that only the most determined people would bother). If a community fork emerges we might see more contributions.
ChrisMarshallNY将近 4 年前
Not familiar with it, but their installation guide is one of the best I&#x27;ve ever seen.
thiht将近 4 年前
I had to use Phabricator a few years ago and I hated it. It&#x27;s way too hard to use for honestly not a lot of gain. Reviewing code was not enjoyable.<p>I like the simpler approach offered by Bitbucket&#x2F;GitHub&#x2F;Gitlab. Reviewing is easy and painless.
bubble0h7将近 4 年前
Well this is sad news to start the week with. I&#x27;d be interested in contributing to a community fork if one emerges. I don&#x27;t want to see this project die.<p>Thank you to everyone who has worked on it over the years!
jcrben将近 4 年前
Seems like there might be a business opportunity here
tychota将近 4 年前
I&#x27;ve mixed filling.<p>I&#x27;m sad, because:<p>- I started using Phabricator in 2012 and tried some contribution back then, when I was still learning. I learn PHP working on contribution.<p>- The product is really awesome and back then, the difference with GH and others was even more striking. Draft PRs years before GH, proper issue management with work board years before GH, a lot of automation (Herald) and an yet unmatched ability to customize the interface, and build extensions to the program. In peculiar, behind able to define custom lint and unit test and have them integrated to the UI is awesome. I&#x27;ve seen others good ideas come before its time, in peculiar with integrated CI&#x2F;CD, being able to see links between everything (issues, diffs, wikis, ect)<p>- The codebase is awesome. I mean, they build a fully modular system from nothing, just raw PHP. In my sense, they build one of the best PHP framework along the product. The architecture is nice, and they had really great ideas (overheating queries <a href="https:&#x2F;&#x2F;secure.phabricator.com&#x2F;T13133" rel="nofollow">https:&#x2F;&#x2F;secure.phabricator.com&#x2F;T13133</a>, EditEngine&#x2F;ApplicationEditor: <a href="https:&#x2F;&#x2F;secure.phabricator.com&#x2F;T9132" rel="nofollow">https:&#x2F;&#x2F;secure.phabricator.com&#x2F;T9132</a>). Bob, Chad, and Evan are awesome devs. They helped me improve and shaped me as a developers. They also created a fondation of craftmanship with stances like: &quot;Don&#x27;t create to much config, it is a sign of badly designed product&quot; and so on<p>- I learned a lot about infra deploying phabricator.<p>- They was a lot of humor back then: <a href="https:&#x2F;&#x2F;secure.phabricator.com&#x2F;T10000" rel="nofollow">https:&#x2F;&#x2F;secure.phabricator.com&#x2F;T10000</a>, <a href="https:&#x2F;&#x2F;secure.phabricator.com&#x2F;T10054#151066" rel="nofollow">https:&#x2F;&#x2F;secure.phabricator.com&#x2F;T10054#151066</a>, <a href="https:&#x2F;&#x2F;secure.phabricator.com&#x2F;T6389" rel="nofollow">https:&#x2F;&#x2F;secure.phabricator.com&#x2F;T6389</a><p>For all this, thanks Evan, and others. It was a nice adventure. I will really miss this...<p>... but for me that was expected, the contributions shrinked, the core team went from 3 to 1. External contribution was also more and more difficult and while I understand the reason (reviewing and maintaining is more expensive than doing all yourself), it build a model that only depend on the willingness of one man. Also lack of proper integration with Gitlab&#x2F;Github (Nuance <a href="https:&#x2F;&#x2F;secure.phabricator.com&#x2F;T12739" rel="nofollow">https:&#x2F;&#x2F;secure.phabricator.com&#x2F;T12739</a>), sticking to an old, pre React area JS framework called Javelin did make the end inevitable. I did see the contribution decrease overtime(see <a href="https:&#x2F;&#x2F;github.com&#x2F;phacility&#x2F;phabricator&#x2F;graphs&#x2F;contributors" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;phacility&#x2F;phabricator&#x2F;graphs&#x2F;contributors</a>). In the last years, Phabricator was just a ghost to me, sadly...<p>I hopes that Evan is well, and the end of adventure is not to bitter.<p>I think too much depends on Phabricator for it too end like that, and I&#x27;m looking forward to @20after4 or others to fork. Maybe it will have a second breath.<p>Anyway, so long and thanks for the fish !
评论 #27334636 未加载
evilelectron将近 4 年前
Sad news indeed :(
fooker将近 4 年前
Doesn&#x27;t GPL seem more palatable now?<p>All the big companies have their own private fork resulting in zero contributions to the main project.
评论 #27330516 未加载
smitty1e将近 4 年前
&quot;Phabricator is a LAMP (Linux, Apache, MySQL, PHP) application.&quot;
评论 #27328633 未加载