[kde-community] Sunsetting of Infrastructure and the Phabricator migration

Alexander Potashev aspotashev at gmail.com
Fri Mar 18 07:45:00 GMT 2016

Hi Ben,

Please find my questions below.

2016-03-18 9:46 GMT+03:00 Ben Cooksley <bcooksley at kde.org>:
> The XML file upon which numerous utilities (including kdesrc-build)
> depend will continue to be made available. It will instead be
> generated by a Python script periodically, based on the contents of a
> Git repository.

How do we change i18n branches in this XML file after disabling

> I should also note that as a side affect of the Phabricator
> transition, scratch/clone repositories will to a certain extent cease
> to exist - everything will now be a mainline repository. As a

Do I get it right that it will be impossible to create a scratch
repository for a 30-minute task or for a proof-of-concept application
without asking the "majors"?

I think it's totally fine because there are many other Git hostings
where you can do quick-and-dirty development from scratch. And you can
move your repo to git.kde.org as soon as it matures. The main pros of
this approach would be a cleaner quickgit.kde.org page and of course
saving of disk space on servers.

Alexander Potashev

More information about the kde-core-devel mailing list