I'm glad to tell you I succeed in docker!
Maybe I changed some codes wrong before, so I delete the phorge folder in docker and copy a clean verion inside.

Did you manage to get the extension working?

Sure, that's a permission issue, I can see the pics now.

You still need the wikimedia extension at least for now. The screenshots just show how to change the subtype of a task and then shows the due date icon. I just changed the permissions on the attachments, maybe they work now?

By the way, if only have the patch can work, or should also install the Wikimedia extension?

Maybe the Ponder has some issue about file uploads, I can't see the file but only {F.......}, I guess is some screenshots.

@littleggghost: Yes after applying the patch to phorge master branch I can see the icon.

Yeah enjoy this feature! Already part of our glorious 2023 Week 32

Good by warning 😢

When you apply this patch on clean phorge master branch, did the calendar icon shows? Because mine not shows.
Maybe there needs some other patches?
Or I should wait your official repository upstream?
For sooner implementation, I want to know if I could try some more methods before wait.

confirmed, that warning makes no sense.

Hahah I guess I could have tested it first.

I think we already did - @valerio.bozzolan ?

I’m not very familiar with this area of code but this sounds appropriate

This looks correct to me:

Gotcha. Probably this is generating the attachment transactions but should be "ignored on no effects":

This feature is not complete also for Conpherence AFAIK

Let's visually mark this to attract people.

I've carefully read the diff :) Thanks

Totally agree. Thanks for any edit in the stub.

Have you digged Internet Archive to fix this? :)

In T15121#3880, @valerio.bozzolan wrote:

I don't think that the author should ever allow to re-license its work. [...] Normal volunteers do not accept that.

Go pohrge!

Clean up my local testing mess

Most phurl.io short URIs point to old upstream tasks. The two related patches make the code at least point directly to these tasks (to still be found on https://web.archive.org/ if secure.phabricator.com ever went down) as there's no direct content equivalent on phorge.it.

@valerio.bozzolan Are there any prehistoric traces that this extension has been successfully used in the past? :P

I tried with only merge this commit https://phabricator.wikimedia.org/rPHABae334e4589a0413c1eb8a9e8d993e553bfeff478
but still not work.

It's a Phacility server, managed at https://secure.phabricator.com/phurl/

I agree, badges seems like the right way to go. They are an underutilized feature really, IMO.

@littleggghost So it turns out that in order to enable this feature, there was a patch to Phabricator core. That patch isn't part of the wikimedia extension, and hasn't been merged into phorge.

I've looked down some of the links of this request, and it looks like the definition of "new user" should be install-specific, and open to interpretation.

When I search in

resources/celerity/map.php

I run this cmd in this docker container, with output:

root@f0d9837493f0:/var/www/phorge/phorge# ./bin/celerity map
Rebuilding 1 resource source(s).
Rebuilding resource source "phabricator" (CelerityPhabricatorResources)...
Found 113 binary resources.
Found 399 text resources.
Found 11 packages.
Writing map "resources/celerity/map.php".
Done.

Makes sense, thanks everyone. Let's decline for the time being.

@littleggghost one thing you might want to try is updating the celerity map. You may be missing the custom css rules to style the deadline appropriately. I’m not familiar enough with the phorge docker image to be able to tell you exactly how that is accomplished. With non-containerized phorge instances you would just run bin/celerity map from within the phorge root directory.

I changed my mind again. No need for edges (short story is, getting the "color" property from the edge is annoying).

In T15743#15855, @valerio.bozzolan wrote:

• https://github.com/xemlock/php-latex (PHP server side)

Interestingly, I just discovered Wikimedia has a pretty cool project to render math on the server side, by transpiling some js into php:

I went down a rabbit hole while trying to add unit tests for this. Our core remarkup unit tests are pretty thorough but they only seem to cover the "core" remarkup engine and syntax. When I added a new test case for this it would pass but always caused a different test case to fail in weird ways. I haven't yet figured out what part of the unit test or engine is stateful such that my unit test alters the state in a way that breaks a later test. If I change the order that tests run in, it just causes another different test case to fail.

Fix lint again

fix lint.

Added contrasting color calculation

There is also MathJax, a subset of LaTex that only covers the mathematical notation without the page layout functionality.

Unrelated note, but interestingly the contributor agreement chooser (https://contributoragreements.org/) is broken. I've already sent an email to their support.

I see that it depends on a NodeJS external script (server-side).

Interesting, I agree. Note that also #bbb is valid but I see that 6 is minimum characters.

Interesting. What's the use case you have in mind?

This is not yet tested.

fix lint error.