That is also nice. However there’s also links in the forums to phabricator or external links.
That would be super cool.
https://phabricator.whonix.org/T941 for example trying to guess the forums URL: https://forums.whonix.org/t/lock_down_interpreters_/_compilers_(interpreter_lock)_(compiler_lock)
But might be different due to special characters, / and (. Even if the forums URL could be predicted I don’t see how T941 has any resemblance to the forums URL. Except…
If originally the forum topic is gets title T941.
Discourse will make this complicated:
rejects too short titles
does not allow all uppercase even T123456678901234567890 was rejected
This could be solved by reconfigure discourse if possible or using compliant topic titles instead.
T941 phabricator migrated ticket
But aren’t these horrible topic titels? Yes. But these can be renamed in a second step. Discourse internally creates reliable redirects. We’d have a double redirect but that is not so bad.
With that such a regex would be possible. Because there is a pattern here:
We can keep them Open, mark them as resolved, or mark them as will not fix. But lets get rid of review, since we are in the process of reviewing all this shit now
Currently there are 208 open issues on phabricator, and 84 open issues on discourse. Will be nice to start mowing through these and culling the backlog. Feeling excited!
Okay everything is mostly working, all data is formatting and everything has been setup on the app side. I tried to migrate a few topics though and am getting a 500 error from Discourse.
I am going to need some help on this one @Patrick as I can’t see logs. All I get is a 500 response with nothing useful. I imagine whatever I am doing will trigger a stack trace.
Let me know when you are available and we can slam this out
At some point it might be worth going through all the phabricator tickets tagged status_open_issue_todo and seeing if we want to close any of them, and then deciding which ones we want to actively work
@Patrick I can’t be the only person who doesn’t like this… Using the forum instead of something like self-hosted Gitlab, or even Github, sounds hacky and just rubs me off wrong…
Why not a self-hostable Gitlab instance? It’s relatively low-maintanice, and isn’t going anywhere soon… Or even just Github; 0-maintaince, etc.
Not sure though… but all I am sure about is this is a unwise move.
The reason we got in this predicament was self hosting. Phabricator was self hosted, then deprecated and left Patrick with a lot of tech debt maintenance hosting some hacked together php and keeping it alive.
I have no problem with github issues, am strongly against self-hosting a gitlab, and think it is important to remember that the linux kernel still does fine with just email.