@avivey that's an excellent observation.

That "don't sign a CLA" article should be titled "don't sign away your copyrights", to be more accurate and less click-bait-y. A CLA may ask you to sign away copyrights (which I feel makes the project non-open-source) ; It doesn't have to.

I'm pretty fine with DCO (which I already do every commit via the git commit -s command) — but I'd rather not sign a CLA. (I’m pretty undecided if I will sign phorge's CLA, but phorge is not commercial entity seeking to mongodb/terraform/elasticsearch-ize the software (read: make a profit from open source, then turn it into All Rights Reserved) so I might do so… after all these incidents I'm rather wary of it.)

Yeah, thad makes sense, I guess.

Suddenly, yesterday I was also talking in one of the kanban communities and I had to tell them that Phorge is a fork of the Phabricator, and not some kind of independent thing without a background. People don't quite understand this.

Good question.

Yeah, that might help (like specifically in the case of the Clone dialog) even though it wouldn't help with dialogs containing writable inputs. (E.g. on the repository page, click Flag For Later instead and press Shift+Tab and Escape.) A better fix would lie at https://we.phorge.it/source/phorge/browse/master/webroot/rsrc/externals/javelin/lib/Workflow.js$413 where either the getSpecialKey would need improvement itself to return true for these non-modifying keys, or it would need to be amended with a custom check in that regard. However, I don't know where that function comes from.

Probably something here should be expanded to check if the form contains at least a visible input without read-only

:p

I was responding to the previous comment which...

Our company uses the Phorge, and we use Keycloak as IAM. Keycloak is a very popular OAuth2/SAML provider now.

GitHub/Facebook is already supported as a Login/Registration providers.

In T15047#1308, @speck wrote:

Did that Phactory: Hosting Projects Here

I can reproduce this, on an hosted Subversion repository.

Yes will be great to see a SAML or Oauth support for external authorities like:

• Keycloak
• Entra ID
• Github
• Facebook
• WeChat / WeCom

Premising that we may want to rollback 328aee033fbd, probably this line is broken: