See-Also: https://circleci.com/ideas/?idea=CCI-I-430
See-Also: https://discuss.circleci.com/t/webhook-support-removed-from-documentation-still-supported/19984

The actual evidence about webhooks is a little spotty and it's possible that they "work" and are just undocumented and not officially supported. It's possible that CircleCI just needs a nudge to actually document/support them.

Pushing the requireCapabilities() change out one more week since I had some stuff crop up early this week and it didn't get a chance to soak.

We haven't seen any PHP7 issues in ~6 months and the last few have been very minor things with edge cases like error handling behavior, so I think we can safely call this resolved.

I'm going to push this out to next week since D19586 probably has a few minor issues with it and it's close to the release cut. It adds a lot of new policy checks which weren't explicit before, so I'd guess it may cause a few improper policy errors on things which are actually allowed. I caught a bunch of them (like "Mute Thread") but probably didn't get every single one.

ugh, zucchini

I'm happy to bring either change upstream if you want to do the legwork. We could also move them to a wiki page or something. No option here feels particularly good to me.

install_ubuntu.sh seems to be completely broken for modern Ubuntu. I don't mind updating it, but I think we discussed dumping it completely?

One possible approach for this is:

We appear to have survived this.

This is entering some kind of closed beta shortly, I'll follow up in T12904 for actual feature improvements to the Support application.

Notes for myself about billing:

There are debian and ubuntu packages for arcanist:

• https://packages.ubuntu.com/zesty/arcanist
• https://packages.debian.org/stretch/arcanist

although popcon data (66) suggests that the debian one is not in wide use.

yes

Does this work without using arc and just normal git commit?

Slightest of issues with the repository indexing mentioned above:

luca:~/phabricator$ ./bin/search index --type repository --force
Usage Exception: Type "repository" matches multiple indexable objects. Use a more specific string. Matching object types are: PhabricatorRepository, PhabricatorRepositoryCommit.
luca:~/phabricator$

In case anyone is still looking for a Trac Wiki -> Phabricator Phriction importer, we have an ugly but mainly functional script I pasted here: P2056. Code blocks are not always converted correctly, but for us that script was enough.

@nemobis - um, you've ever been in enterprise software dependent business? I do consulting for companies that pay thousands euro per year per single solution (having 5-10 is norm) and within that they get sometimes as much as "3 free support ticket" or "50 free support tickets and 3 voting points for features". I personally developed some back-end solution to deal with one problem that started happening in version 4 of one software and got fixed after ~6 years. In version 10. why? because "this problem impacted only 17% of our customers and can be fixed manually. to have fix developed specially for you, pay us ~20x as much as you pay per yer per licence". And that.is.considered.normal.

I feel like there's just some kind of bizarre disconnect:

Well, it is worded very playfully and not very serious corporate business-like.

@nemobis: when customers pay (for example) Atlassian for Atlassian Premier Support, what value/right/expectation do you believe they're getting out of that which we aren't also offering above?

We're planning on selling enterprise support contracts, like those you can purchase from other self-hosting providers like GitHub, Gitlab, and Atlassian. You are not donating money to Phacility.

Indeed I'm not confused about that. That's why I pointed out that giving money in return for no right/expectation to anything, AKA donating, is usually something done towards non-profit entities with certain requirements, not for-profit entities.

We're an evil, for profit company. I'm not sure what's confusing about that.

Sorry, I'm unable to answer your question because I have no idea how you could compare development support to hosting services, or equity to donations.

This looks more like donating than like buying a service. That's ok; but there are established methods to manage such things, usually involving a non-profit entity which accepts members and where members get some voting/decision-making privilege above some threshold of contribution (but you could also call it a donor council or a sponsorship with benefits).

@nemobis, can you walk me through the major differences you see between the proposal above and the support plans offered by other vendors like GitHub, GitLab, and Atlassian so I can make things more clear?

If I read this correctly, people would pay a certain amount regularly without any certainty or reasonable expectation to have any of the fixes or support they care about. Instead they'll need to rely on the resident haruspex to assess what they're embarking on.

phabricator trading cards ftw.

We might eventually support a trade/resale market -- one advantage is that we could give contributors something with slightly more valuable than stickers/flair/badges, but less complicated for us than doing fulfillment on schwag or dealing with taxes for actual money.

I was fully expecting a black market for mana points to be available.

I think that @epriestley just made capitalism and socialism obsolete by re-imagining everything in terms of Mana points. You sir, have won the internet.

Not at all! You can just buy an extremely expensive personal support plan and continue controlling 100% of the roadmap based on personal whim!

Ugh, so I have to come up with reasonable arguments now instead of just paying for features?

I've just removed mentions from Consulting, but that should eventually be updated when this is formally available.

This has been live for nearly two weeks without anything apparently exploding so we don't have any further acton planned upstream (although see T12450 for some followups). If you do run into issues, feel free to file new tasks describing them.

T12531: Unable to upload file: failed to read 4583864320 bytes after offset 0 discusses one side effect of these changes, it should be fixed in HEAD of master and stable now.

Is there a syntax to close audits? Something like "Fixes: <commit-hash>"?

I haven't seen more of this and there's no planned action on our end, so I'm going to presume we've weathered the storm.