Earlier quoted context omitted.
Add Mozilla, Mercurial and LLVM to the list.
And Wikimedia.
Phacility is winding down, Phabricator no longer actively maintained
101–110 of 147 posts
Re: Phacility is winding down, Phabricator no longer actively maintained
#102What I really like about Phabricator as a review tool: * keyboard shortcuts to navigate through the changes * ability to add a comment to multiple lines of code * ability to suggest changes inline * comments are saved as I type them, so an accidental tab close saves my work * comments are submitted in batches when I choose to, not one-by-one after saving each one. Its's sooo useful, because it often happens that I as…
[1]I mainly am not a fan of the PR model, GH’s performance if often terrible, availability like a yo-yo, and the UI is not as good as it could be. I’m also not a fan of centralising a distributed tool with a load of vendor lock-in to boot. There are some odd things you can’t turn off (such as PRs) and the issue management is weak, so you have to use something over the top of it for project management such as ZenHub.
SourceHut is more up my street.
Re: Phacility is winding down, Phabricator no longer actively maintained
#103Phabricator 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.
Re: Phacility is winding down, Phabricator no longer actively maintained
#104Earlier quoted context omitted.
as an addon, I'd love to see more organizations try to tackle this problem without just lifting the flawed GitHub model.
I have no experience with phabricator but it sounds like sourcehut - are you familiar with that one?
Though I think the main selling point of Phabricator is its issue tracker (Maniphest). It is very, very, very nice. May be even the best in class. The company I'm working for switched to JIRA and we still miss Phabricator's.
Re: Phacility is winding down, Phabricator no longer actively maintained
#105Existing instances will continue running "indefinitely". How can a company be shutdown and promise to run forever at the same time?
How does this affect phabricator on premise and phabricator online?
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't planning to start a new project on Monday. Ouch.
Re: Phacility is winding down, Phabricator no longer actively maintained
#106Phabricator 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 :/.)
Re: Phacility is winding down, Phabricator no longer actively maintained
#107Re: Phacility is winding down, Phabricator no longer actively maintained
#108Contrary to the other comments in this thread, I'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. Github is also well known and has issues, PRs and a CI all integrated into one, while with Phabricator each of these are either…
Phabricator seems like it was the right choice for many large project, and I’m sad to see it go on their behalf. It won’t sadden me to never having to use it again though.
Re: Phacility is winding down, Phabricator no longer actively maintained
#109What I really like about Phabricator as a review tool: * keyboard shortcuts to navigate through the changes * ability to add a comment to multiple lines of code * ability to suggest changes inline * comments are saved as I type them, so an accidental tab close saves my work * comments are submitted in batches when I choose to, not one-by-one after saving each one. Its's sooo useful, because it often happens that I as…
Re: Phacility is winding down, Phabricator no longer actively maintained
#110Earlier quoted context omitted.
Point is the description is about as useful as describing a car as an cage with an engine and wheels. Yes it is correct. But it can be anything: - a car - a truck - a trailer with a power generator Phabricator was a (very) different take on the same class of tooling as GitLab: source code management, task management, code reviews etc integrated.
And if I ask "What the heck is a camry?", then that vague description is much better than nothing . > Phabricator was a (very) different take on the same class of tooling as GitLab: source code management, task management, code reviews etc integrated. Great. If you made that comment 11 hours ago then maybe some downvotes on smitty1e would have been justified. Instead it's "how dare you improve the situation somewhat…
It's not "better than nothing". It, itself, is nothing at best.