Re: i18n infrastructure for Grantlee templates

2011-01-20 Thread Albert Astals Cid
A Dijous, 20 de gener de 2011, Stephen Kelly va escriure: > Albert Astals Cid wrote: > > A Dijous, 20 de gener de 2011, Stephen Kelly va escriure: > >> Hi, > >> > >> I'm ready to release the next version of Grantlee, which is the first > >> version with i18n features. The aim is to mark strings as

Re: i18n infrastructure for Grantlee templates

2011-01-20 Thread Stephen Kelly
Albert Astals Cid wrote: > A Dijous, 20 de gener de 2011, Stephen Kelly va escriure: >> Hi, >> >> I'm ready to release the next version of Grantlee, which is the first >> version with i18n features. The aim is to mark strings as translatable >> inside the template files instead of in C++. > > Is

Re: i18n infrastructure for Grantlee templates

2011-01-20 Thread Albert Astals Cid
A Dijous, 20 de gener de 2011, Stephen Kelly va escriure: > Hi, > > I'm ready to release the next version of Grantlee, which is the first > version with i18n features. The aim is to mark strings as translatable > inside the template files instead of in C++. Is Grantlee used anywhere else than kjo

i18n infrastructure for Grantlee templates

2011-01-20 Thread Stephen Kelly
Hi, I'm ready to release the next version of Grantlee, which is the first version with i18n features. The aim is to mark strings as translatable inside the template files instead of in C++. Before I release it I'd like to make sure it can fit into the KDE i18n infrastructure. The test case fo

Re: KDE git docs for dummies ? WAS: Re: splitting up kdebase in git

2011-01-20 Thread Aaron J. Seigo
On Thursday, January 20, 2011, Ben Cooksley wrote: > Correct, it is Gerrit which is a more git based alternative to Reviewboard. > http://code.google.com/p/gerrit/ does it have benefits over reviewboard? having just toyed with a bit after lunch today, it seems like it's useful to drive the entire

Re: KDE git docs for dummies ? WAS: Re: splitting up kdebase in git

2011-01-20 Thread Ben Cooksley
2011/1/21 Alexander Neundorf : > On Thursday 20 January 2011, Aaron J. Seigo wrote: >> On Wednesday, January 19, 2011, Alexander Neundorf wrote: >> > http://community.kde.org/Sysadmin/GitKdeOrgManual looks quite ok for >> > somebody who knows how to use git for KDE, but not for me. >> > Can somebod

Re: Moving nepomuk-system-tray to kdereview

2011-01-20 Thread Artem Serebriyskiy
I planned to write a plasma aplet with same purpose that will use plugins. This idea is currently suspended and its necessity is questionable. On Thu, Jan 20, 2011 at 10:24 PM, Albert Astals Cid wrote: > A Dilluns, 17 de gener de 2011, Artem Serebriyskiy va escriure: > > Hi everyone, > > I wou

Re: Moving nepomuk-system-tray to kdereview

2011-01-20 Thread Albert Astals Cid
A Dijous, 20 de gener de 2011, Artem Serebriyskiy va escriure: > I planned to write a plasma aplet with same purpose that will use plugins. > This idea is currently suspended and its necessity is > > questionable. If you ever do you'll have rework your Messages.sh and/or make sure you load the n

Re: KDE git docs for dummies ? WAS: Re: splitting up kdebase in git

2011-01-20 Thread Andreas Pakulat
On 20.01.11 19:47:22, Alexander Neundorf wrote: > On Thursday 20 January 2011, Tom Albers wrote: > > - Original Message - > > > > > On Wed, Jan 19, 2011 at 03:33:30PM -0600, Ian Monroe wrote: > > > > There is no push/merge/branching policy for KDE. Different projects > > > > will likely do

Re: KDE git docs for dummies ? WAS: Re: splitting up kdebase in git

2011-01-20 Thread Parker Coates
2011/1/20 Alexander Neundorf: > As long as there is no policy defined, I simply try to push/merge to the > respective master ? > I also think that really most/all new KDE git repositories should use a common > workflow. I think this is a reasonable expectation for all repositories that are part of

Re: Moving nepomuk-system-tray to kdereview

2011-01-20 Thread Albert Astals Cid
A Dilluns, 17 de gener de 2011, Artem Serebriyskiy va escriure: > Hi everyone, > I would like to move Nepomuk-system-tray from playground to kdereview > Currently project is: > project > page ?jump=welcome> git: g...@git.kde.or

Re: KDE git docs for dummies ? WAS: Re: splitting up kdebase in git

2011-01-20 Thread Alexander Neundorf
On Thursday 20 January 2011, Aaron J. Seigo wrote: > On Wednesday, January 19, 2011, Alexander Neundorf wrote: > > http://community.kde.org/Sysadmin/GitKdeOrgManual looks quite ok for > > somebody who knows how to use git for KDE, but not for me. > > Can somebody please add a simple step-by-step ho

Re: KDE git docs for dummies ? WAS: Re: splitting up kdebase in git

2011-01-20 Thread Alexander Neundorf
On Thursday 20 January 2011, Tom Albers wrote: > - Original Message - > > > On Wed, Jan 19, 2011 at 03:33:30PM -0600, Ian Monroe wrote: > > > There is no push/merge/branching policy for KDE. Different projects > > > will likely do their own thing. For the time being its just the > > > SVN-s

Re: [PATCH] Re: KDE 4.6.0: go or no go?

2011-01-20 Thread Sebastian Trüg
On 01/20/2011 03:18 PM, Sebastian Trüg wrote: > This patch does in no way solve the issue. Let me give some detail here: I only did see the disabling of Strigi which makes no sense. I am fine with disabling the KRunner plugin for now. But AFAIK this only is a problem in combination with Akonadi. I

Re: [PATCH] Re: KDE 4.6.0: go or no go?

2011-01-20 Thread Ian Monroe
On Thu, Jan 20, 2011 at 08:18, Sebastian Trüg wrote: > This patch does in no way solve the issue. I'm not sure what the release team is supposed to do with this statement. What do you think of 246678 and the 4.6.0 release? Ian

Re: [PATCH] Re: KDE 4.6.0: go or no go?

2011-01-20 Thread Sebastian Trüg
This patch does in no way solve the issue. On 01/20/2011 02:00 PM, Dirk Mueller wrote: > On Wednesday 19 January 2011, Dirk Mueller wrote: > >> so the general consensus seems to be against slipping the schedule and >> inserting a RC3. >> >> This means that we need to solve bug 246678. Given that

[PATCH] Re: KDE 4.6.0: go or no go?

2011-01-20 Thread Dirk Mueller
On Wednesday 19 January 2011, Dirk Mueller wrote: > so the general consensus seems to be against slipping the schedule and > inserting a RC3. > > This means that we need to solve bug 246678. Given that there seems to be > no fix in sight (no comment in the last 14 days), can we mitigate it. is >

Re: KDE git docs for dummies ? WAS: Re: splitting up kdebase in git

2011-01-20 Thread Aaron J. Seigo
On Thursday, January 20, 2011, Aaron J. Seigo wrote: > On Wednesday, January 19, 2011, Alexander Neundorf wrote: > > http://community.kde.org/Sysadmin/GitKdeOrgManual looks quite ok for > > somebody who knows how to use git for KDE, but not for me. > > Can somebody please add a simple step-by-step

Re: KDE git docs for dummies ? WAS: Re: splitting up kdebase in git

2011-01-20 Thread Aaron J. Seigo
On Wednesday, January 19, 2011, Alexander Neundorf wrote: > http://community.kde.org/Sysadmin/GitKdeOrgManual looks quite ok for > somebody who knows how to use git for KDE, but not for me. > Can somebody please add a simple step-by-step howto, what I have to do with > identity.kde.org, projects.kd

Re: KDE git docs for dummies ? WAS: Re: splitting up kdebase in git

2011-01-20 Thread Aaron J. Seigo
On Thursday, January 20, 2011, Oswald Buddenhagen wrote: > On Wed, Jan 19, 2011 at 03:33:30PM -0600, Ian Monroe wrote: > > There is no push/merge/branching policy for KDE. Different projects > > will likely do their own thing. For the time being its just the > > SVN-style development translated to

Re: KDE git docs for dummies ? WAS: Re: splitting up kdebase in git

2011-01-20 Thread Tom Albers
- Original Message - > On Wed, Jan 19, 2011 at 03:33:30PM -0600, Ian Monroe wrote: > > There is no push/merge/branching policy for KDE. Different projects > > will likely do their own thing. For the time being its just the > > SVN-style development translated to Git. > > > words like "unwis

Re: KDE git docs for dummies ? WAS: Re: splitting up kdebase in git

2011-01-20 Thread Oswald Buddenhagen
On Wed, Jan 19, 2011 at 03:33:30PM -0600, Ian Monroe wrote: > There is no push/merge/branching policy for KDE. Different projects > will likely do their own thing. For the time being its just the > SVN-style development translated to Git. > words like "unwise", "stupid" and "utterly braindead" com