Re: [announcement] Telegram bridging to be retired Wed. 20 Sept. | 5 to-dos

Dear All, Sorry for being a pain in the neck about this, but the more I read the plan to migrate, the less it seems a plan at all. It just boils down to a deadline. There is no contingency, nobody has considered what the people who use Telegram to interact with us want, nobody has opened any ki

[announcement] Telegram bridging to be retired Wed. 20 Sept. | 5 to-dos

Hello KDE community, apologies for cross-posting! The time has finally come: both Telegram <-> Matrix bridges will be shut down in 4 weeks on *Wednesday 20 September*. Let's start the co-ordination process now so everything goes as smoothly as possible. For all KDE contributors: please read

Downtime Announcement: Transactional Email Infrastructure

Hi all, We've been informed by one of our hosting providers that they need to schedule some downtime in order to allow for a server move. This will take place this coming Monday, from approximately 4pm UTC for up to 4 hours. As a result, transactional email services will be unavailable during th

Re: Downtime announcement: www.kde.org

[sending again from right address since my gmail address is not subscribed to somee lists] Hello, On Mon, Nov 05, 2018 at 11:02:43PM +1300, Ben Cooksley wrote: > > In order to allow for hardware maintenance, one of our physical > > hardware hosts will need to be shutdown for a few hours on Monday

Re: Downtime announcement: www.kde.org

Hello everyone, On Mon, Nov 05, 2018 at 11:02:43PM +1300, Ben Cooksley wrote: > > In order to allow for hardware maintenance, one of our physical > > hardware hosts will need to be shutdown for a few hours on Monday. > > This downtime will commence around 9:30am UTC and may take several > > hours.

Re: Downtime announcement: www.kde.org

On Sat, Nov 3, 2018 at 7:50 AM Ben Cooksley wrote: > > Hi all, Hi all, > > In order to allow for hardware maintenance, one of our physical > hardware hosts will need to be shutdown for a few hours on Monday. > This downtime will commence around 9:30am UTC and may take several > hours. > > During

Downtime announcement: www.kde.org

Hi all, In order to allow for hardware maintenance, one of our physical hardware hosts will need to be shutdown for a few hours on Monday. This downtime will commence around 9:30am UTC and may take several hours. During this time a number of sites will be inaccessible, including: - www.kde.org -

Re: announcement: plymouth-kcm in kdereview

On 5 January 2017 at 15:03, Marco Martin wrote: > On Thursday 05 January 2017 12:30:38 Jonathan Riddell wrote: >> It should rather follow Plasma practice and set these in the top cmake file >> set(PROJECT_VERSION "5.8.90") >> set(PROJECT_VERSION_MAJOR 5) >> >> and use PROJECT_VERSION > > would thi

Re: announcement: plymouth-kcm in kdereview

On Thursday 05 January 2017 12:30:38 Jonathan Riddell wrote: > It should rather follow Plasma practice and set these in the top cmake file > set(PROJECT_VERSION "5.8.90") > set(PROJECT_VERSION_MAJOR 5) > > and use PROJECT_VERSION would this number be automagically updated one this gets into works

Re: announcement: plymouth-kcm in kdereview

Jonathan Riddell ha scritto: > On Thu, Dec 29, 2016 at 12:58:10PM +0100, Marco Martin wrote: >> Hi all, >> announcing a new KCM module to change the plymouth splash screen >> The repository is named plymouth-kcm and is headed for kdereview now. >> its final resting place would be the workspace area

Re: announcement: plymouth-kcm in kdereview

On Thu, Dec 29, 2016 at 12:58:10PM +0100, Marco Martin wrote: > Hi all, > announcing a new KCM module to change the plymouth splash screen > The repository is named plymouth-kcm and is headed for kdereview now. > its final resting place would be the workspace area, to be released in sync > with th

Re: announcement: plymouth-kcm in kdereview

El dijous, 29 de desembre de 2016, a les 12:58:10 CET, Marco Martin va escriure: > Hi all, > announcing a new KCM module to change the plymouth splash screen > The repository is named plymouth-kcm and is headed for kdereview now. > its final resting place would be the workspace area, to be release

announcement: plymouth-kcm in kdereview

Hi all, announcing a new KCM module to change the plymouth splash screen The repository is named plymouth-kcm and is headed for kdereview now. its final resting place would be the workspace area, to be released in sync with the rest of Plasma -- Marco Martin

Re: announcement: Kwave is in kdereview

El dijous, 10 de novembre de 2016, a les 6:07:14 CET, Thomas Eschenbacher va escriure: > Albert Astals Cid wrote: > > [...] > > >> TODO: make kwave available in bugtracking / bugs.kde.org > > > > I think this is crucial, if it does not use bugs.kde.org personally i > > think it does not fulfill

Re: announcement: Kwave is in kdereview

Albert Astals Cid wrote: [...] >> TODO: make kwave available in bugtracking / bugs.kde.org > > I think this is crucial, if it does not use bugs.kde.org personally i think > it > does not fulfill the Commitments of the manifesto Of course, I 100% agree! I already filed a sysadmin ticket for tha

Re: announcement: Kwave is in kdereview

Albert Astals Cid wrote: > [...] >> And the next question: are there any blocking points that prevent the >> application from going on to kdemultimedia? (any things that can not be >> handled by bugtracking?) > > That's a good question, i would expect [almost] everything we reported during > the

Re: announcement: Kwave is in kdereview

El dimecres, 9 de novembre de 2016, a les 19:51:33 CET, Thomas Eschenbacher va escriure: > Albert Astals Cid wrote: > > [...] > > > >> And the next question: are there any blocking points that prevent the > >> application from going on to kdemultimedia? (any things that can not be > >> handled by

Re: announcement: Kwave is in kdereview

Albert Astals Cid wrote: [...] >> QCommandLineParser: option not defined: "author" >> QCommandLineParser: option not defined: "license" >> QCommandLineParser: option not defined: "desktopfile" >> >> and I have no clue why... >> Could anyone give me a hint where that comes from and what I am suppose

Re: announcement: Kwave is in kdereview / recording

Albert Astals Cid wrote: [...] > Pressed File->record and i got > >http://i.imgur.com/DUhCvVA.png > > I guess that's probably because that user doesn't have enough > permissions to use some of the sound stuff that is neede, but a nicer > error dialog would be really

Re: announcement: Kwave is in kdereview

Albert Astals Cid wrote: [...] >>> These warnings look like nice to fix >>> kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties >>> of Q*Application: no instance (yet) existing. kf5.kcoreaddons.kaboutdata: >>> QCoreApplication::organizationDomain "kde.org" is out-of-sync wit

Re: announcement: Kwave is in kdereview / recording / memory leak

Albert Astals Cid wrote: [...] >>> Pressed File->record and i got >>> >>>http://i.imgur.com/DUhCvVA.png >>> >>> I guess that's probably because that user doesn't have enough >>> permissions to use some of the sound stuff that is neede, but a nicer >>> error dialog would be really appreciated.

Re: announcement: Kwave is in kdereview

El dijous, 27 d’octubre de 2016, a les 21:48:40 CEST, Thomas Eschenbacher va escriure: > Albert Astals Cid wrote: > > [...] > > >>> These warnings look like nice to fix > >>> kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent > >>> properties > >>> of Q*Application: no instance (yet

Re: announcement: Kwave is in kdereview / recording / memory leak

El dijous, 27 d’octubre de 2016, a les 21:10:35 CEST, Thomas Eschenbacher va escriure: > Albert Astals Cid wrote: > > [...] > > >>> Pressed File->record and i got > >>> > >>>http://i.imgur.com/DUhCvVA.png > >>> > >>> I guess that's probably because that user doesn't have enough > >>> permi

Re: announcement: Kwave is in kdereview

Albert Astals Cid wrote: > El dimecres, 12 d’octubre de 2016, a les 7:15:31 CEST, Thomas Eschenbacher va > escriure: > [...] >> BTW: how should we handle these findings during review phase: is it ok >> four you to handle/discuss them here on the mailing list, or shall we >> use some bug tracking

[Announcement] FOSDEM Desktops DevRoom 2017 CfP

Hello, Here is the Call for Participation for the Desktops DevRoom 2017 -8<-- FOSDEM is one of the largest (5,000+ hackers!) gatherings of Free Software contributors in the world and happens each February in Brussels (Belgium, Europe). Once again, one of the tracks wil

Re: announcement: Kwave is in kdereview / _(...) macro

On 17.10.2016 23:30, Jan Kundrát wrote: > On úterý 11. října 2016 21:41:09 CEST, Thomas Eschenbacher wrote: >> the _(...) macro has nothing to do with i18n > > Isn't that a bit confusing? Underscore is used by gettext to mean the > *opposite* from what Kwave uses it for. really? I have never see

Re: announcement: Kwave is in kdereview

El dilluns, 24 d’octubre de 2016, a les 6:29:46 CEST, Thomas Eschenbacher va escriure: > Albert Astals Cid wrote: > > El dimecres, 12 d’octubre de 2016, a les 7:15:31 CEST, Thomas Eschenbacher > > va escriure: > > [...] > > > >> BTW: how should we handle these findings during review phase: is it

Re: announcement: Kwave is in kdereview

El dijous, 13 d’octubre de 2016, a les 6:37:18 CEST, Thomas Eschenbacher va escriure: > Albert Astals Cid wrote: > > [...] > > These warnings look like nice to fix > > kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties > > of Q*Application: no instance (yet) existing. kf5.k

Re: announcement: Kwave is in kdereview

El dimecres, 12 d’octubre de 2016, a les 7:15:31 CEST, Thomas Eschenbacher va escriure: > On 09.10.2016 15:21, Burkhard Lück wrote: > > [...] > > I have three untranslated strings in the GUI of the main window in the > > fully translated locale x-test + de: > > > > the menu item "Record" > > > >

Re: announcement: Kwave is in kdereview

On úterý 11. října 2016 21:41:09 CEST, Thomas Eschenbacher wrote: the _(...) macro has nothing to do with i18n Isn't that a bit confusing? Underscore is used by gettext to mean the *opposite* from what Kwave uses it for. It is also a reserved identifier in C++. Inventing non-standard idioms w

Re: announcement: Kwave is in kdereview

David Faure wrote: > [...] >>> main.cpp shouldn't use I18N_NOOP anymore in KF5. You should create the >>> QCoreApplication instance first, then create the KAboutData using i18n(), >>> then create the QCommandLineParser, also using i18n() > [...] OK, that seems to be a misunderstanding. You only ta

Re: announcement: Kwave is in kdereview

On jeudi 13 octobre 2016 06:37:18 PDT Thomas Eschenbacher wrote: > > kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties > > of Q*Application: no instance (yet) existing. > > I am not aware of doing anything wrong in that place. I told you already what you are doing wrong i

Re: announcement: Kwave is in kdereview

On mardi 11 octobre 2016 21:41:09 PDT Thomas Eschenbacher wrote: > David Faure wrote: > > [...] > > As a user, I definitely vote for kwave going to kdemultimedia. > > As a developer that means I have to review it ;-) > > yes, I vote for kdemultimedia too. Forget about extragear... I meant, as a u

Re: announcement: Kwave is in kdereview

Albert Astals Cid wrote: > [...] > These warnings look like nice to fix > kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties of > Q*Application: no instance (yet) existing. > kf5.kcoreaddons.kaboutdata: QCoreApplication::organizationDomain "kde.org" is > out-of-sync with

Re: announcement: Kwave is in kdereview

On 09.10.2016 15:21, Burkhard Lück wrote: > [...] > I have three untranslated strings in the GUI of the main window in the fully > translated locale x-test + de: > > the menu item "Record" > > "Record" + "Enter Command" in the Settings menu thanks for the hint, you are right. These strings are

Re: announcement: Kwave is in kdereview

David Faure wrote: > [...] > As a user, I definitely vote for kwave going to kdemultimedia. > As a developer that means I have to review it ;-) yes, I vote for kdemultimedia too. Forget about extragear... > CMakeLists.txt: > * I think you can remove the RPATH settings section, ECM takes care of

Re: TRANSLATION_DOMAIN not to be used for app code (was: Re: announcement: Kwave is in kdereview)

El dilluns, 10 d’octubre de 2016, a les 0:38:23 CEST, Friedrich W. H. Kossebau va escriure: > Am Sonntag, 9. Oktober 2016, 22:21:56 CEST schrieb Albert Astals Cid: > > El diumenge, 9 d’octubre de 2016, a les 18:05:29 CEST, Friedrich W. H. > > Kossebau va escriure: > > > Am Sonntag, 9. Oktober 201

Re: TRANSLATION_DOMAIN not to be used for app code (was: Re: announcement: Kwave is in kdereview)

El dilluns, 10 d’octubre de 2016, a les 0:38:23 CEST, Friedrich W. H. Kossebau va escriure: > Am Sonntag, 9. Oktober 2016, 22:21:56 CEST schrieb Albert Astals Cid: > > El diumenge, 9 d’octubre de 2016, a les 18:05:29 CEST, Friedrich W. H. > > Kossebau va escriure: > > > Am Sonntag, 9. Oktober 201

Re: announcement: Kwave is in kdereview

El dissabte, 8 d’octubre de 2016, a les 9:39:24 CEST, Thomas Eschenbacher va escriure: > Hello, > > according to > https://community.kde.org/Policies/Application_Lifecycle#Stage_2:_Stable > I hereby announce the move of Kwave to "kdereview", on it's way to > "kdemultimedia". These warnings look

TRANSLATION_DOMAIN not to be used for app code (was: Re: announcement: Kwave is in kdereview)

Am Sonntag, 9. Oktober 2016, 22:21:56 CEST schrieb Albert Astals Cid: > El diumenge, 9 d’octubre de 2016, a les 18:05:29 CEST, Friedrich W. H. Kossebau va escriure: > > Am Sonntag, 9. Oktober 2016, 17:44:02 CEST schrieb Albert Astals Cid: > > > El diumenge, 9 d’octubre de 2016, a les 11:44:16 CEST

Re: announcement: Kwave is in kdereview

El diumenge, 9 d’octubre de 2016, a les 18:05:29 CEST, Friedrich W. H. Kossebau va escriure: > Am Sonntag, 9. Oktober 2016, 17:44:02 CEST schrieb Albert Astals Cid: > > El diumenge, 9 d’octubre de 2016, a les 11:44:16 CEST, David > > > > Faure va escriure: > > > AFAIK KLocalizedString::setApplica

Re: announcement: Kwave is in kdereview

Am Sonntag, 9. Oktober 2016, 18:05:29 CEST schrieb Friedrich W. H. Kossebau: > What breaks exactly? https://api.kde.org/frameworks/ki18n/html/prg_guide.html#link_noncode: KXmlGui (.rc) files Since .rc files are interpreted at runtime, the translation domain connection is established simply by a

Re: announcement: Kwave is in kdereview

Am Sonntag, 9. Oktober 2016, 17:44:02 CEST schrieb Albert Astals Cid: > El diumenge, 9 d’octubre de 2016, a les 11:44:16 CEST, David > > Faure va escriure: > > AFAIK KLocalizedString::setApplicationDomain isn't > > necessary, you should > > > instead define the domain as a -D flag during compila

Re: announcement: Kwave is in kdereview

El diumenge, 9 d’octubre de 2016, a les 11:44:16 CEST, David Faure va escriure: > AFAIK KLocalizedString::setApplicationDomain isn't necessary, you should > instead define the domain as a -D flag during compilation, but I'm no expert > on that, check the wiki. Don't recomend the domain flag for

Re: announcement: Kwave is in kdereview

Am Samstag, 8. Oktober 2016, 09:39:24 CEST schrieb Thomas Eschenbacher: > Hello, > > according to > https://community.kde.org/Policies/Application_Lifecycle#Stage_2:_Stable > I hereby announce the move of Kwave to "kdereview", on it's way to > "kdemultimedia". > I have three untranslated strings

Re: announcement: Kwave is in kdereview

Burkhard Lück ha scritto: > Am Sonntag, 9. Oktober 2016, 11:44:16 CEST schrieb David Faure: >> AFAIK KLocalizedString::setApplicationDomain isn't necessary, you should? >> instead define the domain as a -D flag during compilation, but I'm no expert >> on? that, check the wiki. > > https://api.kde.

Re: announcement: Kwave is in kdereview

Am Sonntag, 9. Oktober 2016, 11:44:16 CEST schrieb David Faure: > AFAIK KLocalizedString::setApplicationDomain isn't necessary, you should? > instead define the domain as a -D flag during compilation, but I'm no expert > on? that, check the wiki. https://api.kde.org/frameworks/ki18n/html/prg_guide

Re: announcement: Kwave is in kdereview

On samedi 8 octobre 2016 09:39:24 CEST Thomas Eschenbacher wrote: > Hello, > > according to > https://community.kde.org/Policies/Application_Lifecycle#Stage_2:_Stable > I hereby announce the move of Kwave to "kdereview", on it's way to > "kdemultimedia". This is very good news. I have been a long

Re: announcement: Kwave is in kdereview

Thomas Eschenbacher ha scritto: > Hello, > > according to > https://community.kde.org/Policies/Application_Lifecycle#Stage_2:_Stable > I hereby announce the move of Kwave to "kdereview", on it's way to > "kdemultimedia". > > Kwave is a sound editor built on KF5 and exists since November 1998. I >

announcement: Kwave is in kdereview

Hello, according to https://community.kde.org/Policies/Application_Lifecycle#Stage_2:_Stable I hereby announce the move of Kwave to "kdereview", on it's way to "kdemultimedia". Kwave is a sound editor built on KF5 and exists since November 1998. I am the maintainer of that project since ~2000 and

Re: Downtime announcement: all mail infrastructure

On Wed, Feb 18, 2015 at 12:17 PM, Ben Cooksley wrote: > Hi everyone, Hi all, > > To allow sysadmin to migrate mail services to a replacement system > there will be some downtime for a few hours from 7pm UTC tomorrow > (Wednesday 18th February). > > Apologies for any inconvenience. This will affe

Downtime announcement: all mail infrastructure

Hi everyone, To allow sysadmin to migrate mail services to a replacement system there will be some downtime for a few hours from 7pm UTC tomorrow (Wednesday 18th February). Apologies for any inconvenience. This will affect both aliases and mailing lists, for all domains we handle. Thanks, Ben Co

Help with 4.11 announcement

Come on guys, help our promo guys filling some of the amazing stuff you've done. Cheers, Albert El Dissabte, 3 d'agost de 2013, a les 22:00:45, Jos Poortvliet va escriure: > Heya all, > > We're working on the announcement text here: > https://notes.kde.org/p/releas

announcement

Heya all, We're working on the announcement text here: https://notes.kde.org/p/release4.11 Feel free to add/correct stuff ;-) Hugs, Jos signature.asc Description: This is a digitally signed message part.

Re: [kde-promo] 4.11 Beta 1 release announcement

nshot. Screenshot guidelines below. > > Also someone should start leading the proper 4.11 announcement work. Virtually all of the content comes from technical people and groups. When he bowed out, Sebas said that what was needed for major releases was for someone to coordinate, making sure tha

4.11 Beta 1 release announcement

skills can [re]write the features in a nice way it'd be cool. And we probably need a screenshot. Also someone should start leading the proper 4.11 announcement work. Cheers, Albert - Who never signed up to do any kind of promo work

Announcement: qt-kde repo has been removed

Hi all, I just wanted to let you all know that the qt-kde git repository has been removed due to having not been updated in forever. In exchange, it has been migrated to be a mirror of the base Nokia Qt repository available from gitorious.org (available as 'qt' i.e. git://anongit.kde.org/qt).