Re: Google Summer of Code 2016 - C# bindings for Qt

2016-03-03 Thread Joao Matos
Hi Sebastian and the rest of the KDE community, I'd like to propose to mentor Dimitar but I have no idea what the policy of the KDE project is regarding the possibility of allowing mentors external to the community. I believe I am the best person to mentor Dimitar due to a couple of factors: - S

Re: Google Summer of Code 2016 - C# bindings for Qt

2016-03-03 Thread Sebastian Kügler
Hi Joao, On Thursday, March 03, 2016 19:36:05 Joao Matos wrote: > Hi Sebastian and the rest of the KDE community, > > I'd like to propose to mentor Dimitar but I have no idea what the policy of > the KDE project > is regarding the possibility of allowing mentors external to the community. > > I be

Re:

2016-03-03 Thread Friedrich W. H. Kossebau
Hi Alex, Am Donnerstag, 3. März 2016, 20:13:59 CET schrieb Alex Mourtziapis: > Hi, > > Sorry for spamming... > I wanted to ask if there's a possible way to work on Krita repo without > messing with the whole Calligra Suite. > (my connection is not that good as you can imagine, it ll take a lotta

Re:

2016-03-03 Thread Aleix Pol
On Thu, Mar 3, 2016 at 7:13 PM, Alex Mourtziapis wrote: > Hi, > > Sorry for spamming... > I wanted to ask if there's a possible way to work on Krita repo without > messing with the whole Calligra Suite. > (my connection is not that good as you can imagine, it ll take a lotta of > hours just > to

[no subject]

2016-03-03 Thread Alex Mourtziapis
Hi, Sorry for spamming... I wanted to ask if there's a possible way to work on Krita repo without messing with the whole Calligra Suite. (my connection is not that good as you can imagine, it ll take a lotta of hours just to get the suite) ᐧ

Re: Google Summer of Code 2016 - C# bindings for Qt

2016-03-03 Thread Sebastian Kügler
On Thursday, March 03, 2016 06:20:49 PM Arno Rehn wrote: > having worked with Dimitar before, I'd recommend to accept QtSharp as a > project under the KDE umbrella for this year's gsoc (if that's possible). > Dimitar has done some good work on Qyoto and SMOKE in the past. I think > C# and Qt are

Re: Google Summer of Code 2016 - C# bindings for Qt

2016-03-03 Thread Arno Rehn
Hey everyone, having worked with Dimitar before, I'd recommend to accept QtSharp as a project under the KDE umbrella for this year's gsoc (if that's possible). Dimitar has done some good work on Qyoto and SMOKE in the past. I think C# and Qt are a good fit, so I fully support creating bindings

Re: GSOC-2016

2016-03-03 Thread Myriam Schweingruber
Hi Abhimanyu, How about addressing this to the project mailing list instead of the more general KDE development one? KDE is a community of several dozen projects, not just one project, so please use the correct target. Finding the correct mailing list is certainly something an aspiring developer s

Fwd: [kde] Getting Started

2016-03-03 Thread Myriam Schweingruber
Forwarding to the KDE development ML, as it is more suitable there than in the KDE support ML, targeted at end users. Note that most KDE projects have a specific mailing list as well. Valeriu: you should explore the various projects that came up with suggestions, choose one and then get to know th

Re: Review Request 127178: Added writer plugin support

2016-03-03 Thread Varun Joshi
> On March 1, 2016, 11:03 a.m., Pinak Ahuja wrote: > > autotests/taglibwritertest.cpp, line 53 > > > > > > The test needs to be fixed. What exactly are the wierd moc errors you > > are getting? Lets find out why

Re:

2016-03-03 Thread Alex Mourtziapis
On 2 March 2016 at 01:40, Aleix Pol wrote: > On Tue, Mar 1, 2016 at 11:08 PM, Alex Mourtziapis < > alex.mourtzia...@gmail.com> wrote: > >> >> Hey, >> >> >>My name is Alex and I am third-year student. >> >> I just went through your ideas list at [1], some of them really >> triggered my interest bu

Re: Review Request 127178: Added writer plugin support

2016-03-03 Thread Pinak Ahuja
> On March 1, 2016, 11:03 a.m., Pinak Ahuja wrote: > > autotests/taglibwritertest.cpp, line 53 > > > > > > The test needs to be fixed. What exactly are the wierd moc errors you > > are getting? Lets find out why