KDE's Phabricator instance should support Markdown instead of or alongside Remarkup

Brainstorm
1

KDE’s Phabricator instance should support Markdown, instead of, or alongside, Remarkup. One of many examples of why is that despite the undermentioned source markup generating its correlated content:

  1. ==== [`#278016`](https://phabricator.kde.org/T12308#278016) ====

  2. #278016

…the undermentioned:

> ==== [`#278016`](https://phabricator.kde.org/T12308#278016) ====
> 
> Dolphin still doesn't look anything like this and even that cyan border is still there. While I understand the need to redesign a major app, all the other QT apps look just as bad or worse. A lot of this is down to the theme engine.

…becomes:

Screenshot_20250318_163830
Screenshot_20250318_163830506×250 21 KB
[1]

…whereas the undermentioned:

> #### [`#278016`](https://phabricator.kde.org/T12308#278016)
> 
> Dolphin still doesn't look anything like this and even that cyan border is still there. While I understand the need to redesign a major app, all the other QT apps look just as bad or worse. A lot of this is down to the theme engine.

…becomes:

#278016

Dolphin still doesn’t look anything like this and even that cyan border is still there. While I understand the need to redesign a major app, all the other QT apps look just as bad or worse. A lot of this is down to the theme engine.

Myriad additional deficiencies exist.

  1. phabricator.kde.org/T12308#317140 ↩︎

2

My impression was that Phabricator is being phased out in favor of gitlab tasks.

If that is the case there might not be much work put into the old tool to be fair

1 Like
3

@krake, that would explain it. I’d presumed that they’d replace it with Phorge, considering that the undermentioned appear to remain:

If they did, I could send these grievances upstream, instead.