We run a vulnerability reporting program through HackerOne. Many reports we receive through this program are extremely valuable and this program is an important part of keeping Phabricator secure.
Administrators can now configure global default settings. Prose diffs have improved.
Differential works with any repository, self hosted, or hosted elsewhere.
Some early prototype High Availability features are now available for ambitious installs.
We've begun rolling out some design updates to detail pages in multiple applications.
Here is an advanced internet usage tip for extreme internet experts.
Almanac moved toward release.
Workboards got even fancier, and repository callsigns are now optional.
Users coming to Phabricator from other software (like GitHub or Gerrit) are sometimes tripped up by the sequencing of Phabricator's default review workflow in Differential.
Workboards got fancier.
Workboards now have some new features:
Subprojects and milestones are now available in the UI, but still rough.
In Phabricator, "Projects" are designed as a general purpose organization tool. We've made a number of small product and UI changes recently to reinforce this. These changes are primarily focused at new users, who sometimes find the behavior of projects confusing.
Projects shown in policy controls are now smarter, and will learn and remember the projects you select most frequently.
We've added an autocomplete feature to comments to make it easier to type usernames and project hashtags. Projects now have configurable menus and simpler rules around watching and subscribing.
After 2016 Week 4, we've added an autocomplete feature to make it easier to type usernames and project hashtags in comments. It looks like this:
Repositories now have unique (optional) short names, Amazon S3 integration has been updated.
After D15026 lands, we could really use some more cat facts to improve the product. Feel free to send revisions if you discover new facts about cats.
We're much closer to making callsigns optional on repositories; subprojects and milestones are creeping forward.
Subprojects and milestones have moved forward, but the UI is still unpolished and confusing.
ApplicationEditor has promoted to stable, search/indexing updates have landed, bin/lipsum got a little fancier, and subproject infrastructure is taking shape.
ApplicationEditor is now largely stable and new third-generation Conduit endpoints have taken shape. Subprojects are up next.
Owners has new owners.search and owners.edit endpoints in HEAD, which you can use to read and write paths. For example, you could use them to synchronize package definitions from an external source.
I recently participated in Stripe's CTF3, a programming challenge. This is the first time I've participated in Stripe's CTF, but I really enjoyed it. I thought the problems were very interesting and the technical aspects of the challenge were well executed.
As a potential new contributor to an open source project, it can be very frustrating to submit an issue or pull request on GitHub and never hear back from the maintainer. This article briefly discusses the problem and proposes a tool which might improve the state of the world by making it easier for contributors to estimate what level of response they'll get from a project before they begin work.
Here at Phacility, we're sort of big NFL fans. Sort of, in that one founder has season tickets for the 49ers already, two founders have season tickets at the new 49ers stadium for the 2014-2044 seasons, and Evan (founder three of three) has been known to say "Go local sports team!" when appropriate.
For many people, the value of code review is rather unclear. Since the value is not clear code review is often not done, skipped, or forgotten entirely in favor of more obviously important work items.