The KDE project which touches Localization [l10n] (and Internationalization [i18n])
Fri, Dec 6
Please see the results of my first attempt to use svn2git: https://cgit.kde.org/scratch/aspotashev/converted-scripty-v1.git/
Thu, Dec 5
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?
Wed, Dec 4
Hello, it's me again.
Tue, Dec 3
Mon, Dec 2
Sun, Dec 1
May be the original author is not following Phabricator. You can try and ping him in the bugs.kde.org report or by email.
Sat, Nov 30
We never got a proper explanation of what this does or how it works.
Fri, Nov 29
It has been more than a year. Should we close this and https://bugs.kde.org/show_bug.cgi?id=380007?
Wed, Nov 27
i can see this is a potential bugfix, but honestly, i'd just leave the kde4 branches die (unless this is blocking you heavily in some way)
Thu, Nov 21
Tue, Nov 19
I would like to add one more idea: https://kde.org/images/screenshots/ can be removed in favor of https://cdn.kde.org/screenshots/ that mirrors https://cgit.kde.org/websites/product-screenshots.git/
Sun, Nov 17
Well, this is a bug fix. Without this patch preparetips and svn-clean won't run unless you cloned the two mentioned repos manually.
In terms of /applications, that needs to remain separate because the generator relies on being able to add it's files to the contents of websites/kde-org-applications prior to it being uploaded.
Anyway, the real world process is not even the one you are describing. The point is here is not to fix this set of script: it's to throw it away in the long run and have it something more flexible. Hence a minimal amount of work should go into keeping this scripts alive. Each branch can live on its own own until it's unified.
What is the gain? This branch can stay as it.
@aacid Completely agree, it's the reason why I added a lot of information to https://community.kde.org/KDE.org/Local_Setup. Since there was only really outdated information until recently and I needed to figure the installation process alone. The documentation is not perfect but at least the main information are here.
I disagree with having magic setup unless there's clear instructions provided
With regards to kdeslides/ these should be shifted to share.kde.org, which means they do not require a Git repository.
Sat, Nov 16
As a counter-argument to this statement, I'm going to explain why */l10n-kf5*/ and */l10n-kde4/ are not real branches. Even though the various scripts/ directories are stored under branches/stable/ and trunk/ in SVN, they are not used as branches anymore.
You did not convince me, sorry.
And of course the kde4 branches won't need.any update: one is already gone, the other will be soon.
As I write initially:
- separate branches, as it's easier to adapt the current code;
- later we will transition all kf5 branches to use master, in a non disruptive way.
There is no reason for using multiple branches in scripty.git, it will only make usage and development harder:
My top-level plan is to
Fri, Nov 15
ok, i guess
Thu, Nov 14
Wed, Nov 13
Go for ti