+1000 to moving to Invent, I’m much more used to that workflow.

Trying out https://docs.python.org/3/library/2to3.html wouldn’t hurt

• https://cgit.kde.org/pology.git/ → https://commits.kde.org/pology

In D26776#597800, @ltoscano wrote:

Thanks! Do you think it would be possible to split the tox part (requirements, setup.py) from the partial porting (almost all changes under pology/) ?

The current HIG suggest a progress bar for these scenarios (https://hig.kde.org/components/assistance/progress.html), but I’m not sure where that would go in Lokalize, and it would definitely require more complex changes.

Maybe KMessageWidget within the main UI component (the view of the source and target strings) would make sense…

Notice that, while the code is in a view, the action is triggered from an application-wide menu.

In D25771#572906, @broulik wrote:

I don't know what the UI looks like or what workflow it serves but judging from the fact it's a QDockWidget I assume a KMessageWidget inside the dock would be more fitting than a free-floating notification?

Please, push a commit to fix the headers. See https://binary-factory.kde.org/job/Website_hig-kde-org/157/console

It has been more than a year. Should we close this and https://bugs.kde.org/show_bug.cgi?id=380007?

Can someone else land the patch? I don’t think I have the required permissions.

https://invent.kde.org/websites/hig-kde-org/merge_requests/49

Should I request push access until we finish the migration, or should I use Phabricator differentials?

Marking as resolved since the redirection will be handled at D25120

@ognarb Will you take care of the redirection?