Re: KDE licence policy update
Am Freitag, 10. Februar 2017, 18:43:38 CET schrieb Adriaan de Groot: > This point is listed under "All new source code and related data files ..." > and? there's an additional point 12, "Documentation started before 2016 can > be licensed under ..." which would seem to be exactly what you're asking > for What is the definition of "Documentation" in the license policy draft? "Documentation" = each single docbook, i.e 160 single docbooks for digikam or "Documentation" = all docbooks pulled in via entities in index.docbook of an application ? Please clarify, thanks. -- Burkhard Lück
Re: KDE licence policy update
Am Freitag, 10. Februar 2017, 14:54:52 CET schrieb Jonathan Riddell: > I'd like to get back to my proposed update of the KDE licence policy > > https://community.kde.org/Policies/Licensing_Policy/Draft > > I got some comments from Matija Šuklje which I incorporated and it now > includes a handy changelog. > > -Note that Qt is LGPL 3 not 2.1 > -Code copied from Qt can be GPL 3 as well as GPL 2, check comparible > with your code > -Allow AGPL for web apps > -Encourage AGPL for web apps > -Allow icons to be CC-BY-SA 4 > -Allow media files to be CC-BY-SA 4 and no longer allow CC-BY-SA 3 > -Note CC-BY-SA 4 is LGPL 3 compatible > -Documentation to be CC-BY-SA 4 > -MIT text now one of the more standard variants (modern style with > sublicence) -Links to SPDX licences > > The main change is for docs and other non-code files to become > CC-BY-SA 4. This allows it to be converted to code (it's one-way > compatible with LGPL 3) and allows us to share with other popular > sources such as wikipedia. CC-BY-SA 4 is also better maintained, > better understood and internationally recognised than the old FDL > licence. > I fail to understand why FDL is dropped for Documentation, content on userbase is still dual licensed (CC_BY-SA 3.0 and FDL 1.2) and even the Licensing_Policy/Draft content itself is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2 -- Burkhard Lück
Re: Please move project task tracking to Phabricator
Am Montag, 7. November 2016, 11:56:14 CET schrieb Harald Sitter: > On Sun, Nov 6, 2016 at 8:45 PM, Burkhard Lück <lu...@hube-lueck.de> wrote: > > Am Donnerstag, 3. November 2016, 10:43:56 CET schrieb Harald Sitter: > >> For everyone reading this: IF you want your open todos migrated from > >> todo.kde.org to a phabricator workboard drop me a mail and I'll work > >> with Ben to get you sorted. > > > > Please move the open tasks for Localisation from > > https://todo.kde.org/?controller=board=show_id=22 to > > https://phabricator.kde.org/project/profile/164/ > > Done > > Do note that I only migrated into one column, so you'll need to create > the workboard columns as you'd like them and move the items as you see > fit, manually. > > (the old todo board continues to be open until either you or a > sysadmin closes or deletes it). > Thanks you -- Burkhard Lück
Re: Please move project task tracking to Phabricator
Am Donnerstag, 3. November 2016, 10:43:56 CET schrieb Harald Sitter: > For everyone reading this: IF you want your open todos migrated from > todo.kde.org to a phabricator workboard drop me a mail and I'll work > with Ben to get you sorted. Please move the open tasks for Localisation from https://todo.kde.org/?controller=board=show_id=22 to https://phabricator.kde.org/project/profile/164/ Thanks -- Burkhard Lück
Re: Creating a map of KDE contributors?
Am Dienstag, 20. September 2016, 11:49:43 CEST schrieb Jonathan Riddell: > Gnome already do this > https://wiki.gnome.org/GnomeWorldWide > > and I have vauge memories of KDE doing it in the past too, or maybe I dreamt > that > http://web.archive.org/web/20051221060246/http://worldwide.kde.org/pics/ fullmap.jpeg -- Burkhard Lück
Re: [kde-community] Cervisia?
Am Sonntag, 5. Juni 2016, 14:22:45 CEST schrieb Nicolás Alvarez:
> > El 5 jun 2016, a las 09:08, Martin Koller <kol...@aon.at> escribió:
> >> On Sunday 05 June 2016 09:14:42 Burkhard Lück wrote:
> >>
> >> Some i18n issues:
> >>
> >> It is a QApplication so you have to add the translators tab manually with
> >> aboutData.setTranslator
> >
> > ok. what shall I write there (names, emails ?)
> >
> > Isn't that a limited approach to name the translators in the sourcecode,
> > since every new translation added will need a source change ?
>
> No; you use something like i18n("TRANSLATOR NAME") (I don't remember the
> exact string), so that the name comes from the translation itself.
aboutData.setTranslator(i18nc("NAME OF TRANSLATORS", "Your names"),
i18nc("EMAIL OF TRANSLATORS", "Your emails"));
but not necessary here as Albert pointed out.
Thanks
--
Burkhard Lück
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Cervisia?
Am Sonntag, 5. Juni 2016, 14:08:39 CEST schrieb Martin Koller:
> On Sunday 05 June 2016 09:14:42 Burkhard Lück wrote:
> > Am Samstag, 4. Juni 2016, 22:45:49 CEST schrieb Martin Koller:
> > > On Friday 16 October 2015 06:53:19 Jeremy Whiting wrote:
> > > > Awesome! Keep it up. Porting to Qt5/KF5 can happen on a branch and be
> > > > done a small bit at a time if you like. There are also some scripts in
> > > > kdesdk/kde-dev-scripts/kf5 that can help with the trivial changes.
> > > > Most are executed like find -iname *.cpp | xargs scriptname, but if
> > > > not they will say in a comment at the top of the script how to execute
> > > > them.
> > > >
> > > > On Thu, Oct 15, 2015 at 8:02 PM, Martin Koller <kol...@aon.at> wrote:
> > > > > On Thursday 15 October 2015 15:49:32 Jeremy Whiting wrote:
> > > > >> Michael, Martin,
> > > > >>
> > > > >> Any progress on the cervisia front? Is there anything I can do to
> > > > >> help?
> > > > >
> > > > > yes, a lot of progress!
> > > > > We have already ported away from Qt3/KDE3 support classes.
> > > > > This is already in master and I'm testing it by using it on a daily
> > > > > basis.
> > > > >
> > > > > The next step would now be to start the port to KF5 - this has not
> > > > > been
> > > > > started yet.
> > >
> > > Just for your information: I have now completed the KF5 port and master
> > > now
> > > holds this version
> >
> > So you want Scripty to track master to trunk_kf5 and Applications/16.04 to
> > l10n stable, right?
>
> Ermm. don't understand.
>
You want this:
http://commits.kde.org/sysadmin/repo-metadata/
c2645d1fd170b50e5ff249c3844120dbfdac863a
> > Some i18n issues:
> >
> > It is a QApplication so you have to add the translators tab manually with
> > aboutData.setTranslator
>
> ok. what shall I write there (names, emails ?)
>
Nothing, false alarm
> Isn't that a limited approach to name the translators in the sourcecode,
> since every new translation added will need a source change ?
>
> > no setApplicationDomain("cervisia"), so no translations of KXmlGui (.rc)
> > files and KConfigXT (.kcfg) files, see
> > https://api.kde.org/frameworks/ki18n/html/ prg_guide.html
>
> What I have in the cmake file is
> add_definitions(-DTRANSLATION_DOMAIN="cervisia")
> Is that not enough ?
>
> Note that cervisia is also built as a KPart.
>
Yes you need add_definitions(-DTRANSLATION_DOMAIN="cervisia") for that,
> I put now
> KLocalizedString::setApplicationDomain("cervisia");
> in kdemain()
Now cervisia is fully translated, but has an outdated and untranslatable man
page, I'll file an RR for that issue.
--
Burkhard Lück
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Cervisia?
Am Samstag, 4. Juni 2016, 22:45:49 CEST schrieb Martin Koller:
> On Friday 16 October 2015 06:53:19 Jeremy Whiting wrote:
> > Awesome! Keep it up. Porting to Qt5/KF5 can happen on a branch and be
> > done a small bit at a time if you like. There are also some scripts in
> > kdesdk/kde-dev-scripts/kf5 that can help with the trivial changes.
> > Most are executed like find -iname *.cpp | xargs scriptname, but if
> > not they will say in a comment at the top of the script how to execute
> > them.
> >
> > On Thu, Oct 15, 2015 at 8:02 PM, Martin Koller <kol...@aon.at> wrote:
> > > On Thursday 15 October 2015 15:49:32 Jeremy Whiting wrote:
> > >> Michael, Martin,
> > >>
> > >> Any progress on the cervisia front? Is there anything I can do to help?
> > >
> > > yes, a lot of progress!
> > > We have already ported away from Qt3/KDE3 support classes.
> > > This is already in master and I'm testing it by using it on a daily
> > > basis.
> > >
> > > The next step would now be to start the port to KF5 - this has not been
> > > started yet.
> Just for your information: I have now completed the KF5 port and master now
> holds this version
So you want Scripty to track master to trunk_kf5 and Applications/16.04 to
l10n stable, right?
Some i18n issues:
It is a QApplication so you have to add the translators tab manually with
aboutData.setTranslator
no setApplicationDomain("cervisia"), so no translations of KXmlGui (.rc) files
and KConfigXT (.kcfg) files, see https://api.kde.org/frameworks/ki18n/html/
prg_guide.html
Thanks
--
Burkhard Lück
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Translating the KDE manifesto
Am Donnerstag, 19. Dezember 2013, 23:02:56 schrieb Albert Astals Cid: El Dijous, 19 de desembre de 2013, a les 21:49:10, Martin Graesslin va escriure: On Thursday 19 December 2013 20:05:38 Albert Astals Cid wrote: El Dijous, 19 de desembre de 2013, a les 09:05:22, Martin Graesslin va escriure: On Wednesday 18 December 2013 23:50:03 Eike Hein wrote: Translations are always a bit 'risky' of course but I think in the spirit of inclusiveness and internationality they're a great idea. I'm very unsure whether translation is a good idea at all. It's too easy to change the meaning and just think about how carefully we worded everything to make the meaning quite clear. It's possible that a certain wording will get a different meaning in another language just because it's not possible to translate correctly. So overall from me a -1 for translations. If we want to do translations it has to be clear, that: * it's a translation which is not binding. The English version of the manifesto matters * we have very strong requirements on who is allowed to translate and a very strict peer review process for the translated document. Any reason why the manifesto translations should be more strict than say the 4.12 announcement? I cannot judge the quality of the translations, given that the release announcements are not translated to any language I speak. But just a small point for the quality of translations: all German IT channels reported that 4.11 is the last release, because we wrote latest which is very close to letzte (German for last). And that's the fault of our translators? No. $ grep -c letzte l10n-kde4/de/messages/www/www_www.po 0 -- Burkhard Lück ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] KBibTeX
Am Dienstag, 12. November 2013, 22:57:49 schrieb Thomas Fischer: Hello Dominik, In case you have not already a KDE contributor account, you can request one by following http://techbase.kde.org/Contribute/Get_a_Contributor_Account You'll need a KDE identity, but it's all described there. Check. Then, you go to https://sysadmin.kde.org/tickets/ and ask the KDE SysAdmins to create a new git repository. You'll get instructions how to proceed then and how to push all your data. In progress. When KBibTeX is pushed into the kde git repos please drop a note to kde-i18n- d...@kde.org so we can sort out all i18n issues (e. g. moving/renaming existing catalogs around) and integrate KBibTeX into KDE's i18n aka Scripty's workflow. Thanks. -- Burkhard Lück ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
