fixed capability

In D25850#22726, @valerio.bozzolan wrote:

What happens to already-existing URLs? Maybe nice to mention in the test plan

Fix my local unit test config

In D25844#22553, @valerio.bozzolan wrote:

I hope you won't send me a lawyer

do you really think I could afford one

this unfortunately caused T15963: LDAP over TLS is broken :/

Works on my machine!

I'm mostly a Debian person (so I'm not aware of CentOS specifics) but my understanding is that CentOS 7 shipped with PHP 5.4 and has newer versions available via alternative repositories (not sure if official or not), while CentOS 8 (and Rocky Linux 8, if that matters) had PHP 7.2 by default and shipped a few years back. Is there a reason we're not basing our PHP support on latest distro releases (plus something like a year or two for a transition buffer), especially if newer PHP versions are available for older distro versions available as backports? I don't think requiring PHP / distro upgrades every few years is unreasonable.

In D25014#624, @MacFan4000 wrote:

Could a member of Blessed Committers please land this? I can't do it my self (no write access) and I would appreciate it.

I prefer IRC but don't have any issues with having Matrix bridged there, but I would prefer to not have separate unbridged channels to reduce fragmentation of the already-small community.

I was initially planning to use Phorge for upstream maintenance and project governance and using individual projects for apps (Maniphest, for example). If Phorge is about the software, where are you planning to put project governance?

Thanks. We might want to add Trusted Contributors create/edit policies on projects too, but otherwise I think that should be everything to get us started.

In T15001#26, @Matthew wrote:

Okay, I have set up the projects, spaces, forms, and other policies with one exception:

I think that's good to get us going. Who would be able to manage membership of the blessed_commiters / security groups? Admins?