Work related to Phorge, the organization that develops Phorge (the software).
Details
Nov 2 2024
Oct 31 2024
Oct 18 2024
Oct 9 2024
If I were starting today I would probably design the back-end APIs first, then make the web interface derive from those APIs, such that web requests and api requests are not really any different, at least with regard to enforcing access controls.
Oct 8 2024
Sep 17 2024
Sep 16 2024
Sep 5 2024
Sep 4 2024
Sep 3 2024
Aug 31 2024
It seems to me that in general more information should be added to the main page: screenshots, main features, as is usually done in other large projects.
Supporting PHP 8.4 (currently planned for 2024-11-21) will require PHP syntax introduced in PHP 7.1 per T15935.
Aug 28 2024
Aug 24 2024
Also related: T15025
Aug 15 2024
Aug 11 2024
Aug 10 2024
Well, I doubt we can dig more than this.
Aug 9 2024
Aug 7 2024
Jul 31 2024
I do not understand this thing more than this. Help welcome.
Jul 30 2024
Jun 15 2024
I have this look on Windows for
a { outline-style: auto; }
Last Chrome | Last Firefox |
Jun 14 2024
May 21 2024
@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.
May 20 2024
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.)
May 15 2024
May 10 2024
Apr 29 2024
Apr 28 2024
Yeah, thad makes sense, I guess.