Right, i will prepare a Merge Request

Reviewing the logs I see the following typo:

LANGUAGES=en es fr nl uk_UA ca de it zh_CH pt_PT

Hi Ben,

As all work as expected, this file can be closed now.

Hi all,

Ok, i seen the problem.

I have now unprotected that Sysadmin ticket.

Hum, i don't have the right to access on T16059...

Sorry, wrong copy-and-paste: T16059

Hi Luigi,
T16036 ??? are you sure ?..

Please leave them there for now. See T16036.

Hi all,

Done with this commit https://invent.kde.org/documentation/digikam-doc/commit/22dfc978e6442ef34a0b5bea8a03fa4f2fc79634

The ticket can't be closed just yet: the new documentation is stated to be CC BY SA 4.0 but the text is mostly the same as the old one, which is GFDL 1.2. Unless a proper relicensing is documented, where all contributors agree (or have already agreed though FLA and or https://invent.kde.org/sdk/kde-dev-scripts/-/blob/master/relicensecheck.pl), the license must stay GFDL 1.2.

Yes, this is just the nature of the readthedocs theme. Not only Kdenlive all documentations using it, look like this.

That behaviour is governed by the Sphinx theme - you can see the exact same thing happening with Kdenlive.
Krita appears to be using a customised theme hence why they don't have the issue.

Hi all,

Hi all,

That will be due to the first run not being done - i've now done that.

The job https://binary-factory.kde.org/view/Websites/job/Website_docs-digikam-org/ is not triggered anymore automatically when a commit is done in git/master.

Hi Ben,

Hi all,

Thanks Luigi for the feedback. So i need to complete first the conversion and merge back sphinx branch to master, before to check the translations workflow.

In T16036#285444, @cgilles wrote:

Hi Luigi,

Hi all,

Hi Albert,

Same - if you start from the StaticMessages.sh script from the other repositories, it should be fine.

Personally i know 0 about how that works, but if you're doing the same as the two other places, i don't see why it wouldn't work.

The infrastructure of digiKam handbook is under migrating from DocBook to RestructuredText/Sphinx. It miss the i18n to enable.
I plan to complete the manual conversion before Christmas, as we have a group of people ready to work on ported documentation to create missing entry in the documentation.

Hi Ben,

Hi Julius,

ID 38 enable for stats.kde.org :

I've provisioned ID "38" for that now.

The commented Matomo tracking code need to be re-enabled. A new ID must be used (actually it's 34 for KDenlive);

Hi Ben,

The Binary Factory job to build the site has now been provisioned: https://binary-factory.kde.org/job/Website_docs-digikam-org/1/console
It fails however, likely because Digikam is not mirroring the format that Kdenlive and Krita have chosen. You need to match how they have their setup i'm afraid.

Hi Ben,

I start to back-port KDenlive implementations:

Thanks Ben. I will backport and configure KDenlive files in "sphinx" branch from digiKam documentation repository.

The system has flexibility as to the branch that we use.

Ok, Must i use master or a devel branch in git repository ?

As stated previously, the initial work for Sphinx to be able to run must be in place within the repository first before anything from a Sysadmin perspective can be actioned.

Hi Ben,

Thanks Julius for this excellent feedback. Now i know how to start with the migration.

Hi Gilles,

Hi Wolthera,