KDE CI: Frameworks » kdoctools » kf5-qt5 WindowsMSVCQt5.11 - Build # 12 - Fixed!

[CI System]

BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kdoctools/job/kf5-qt5%20WindowsMSVCQt5.11/12/
 Project:
kf5-qt5 WindowsMSVCQt5.11
 Date of build:
Wed, 31 Oct 2018 03:50:31 +
 Build duration:
7 min 2 sec and counting
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)

KDE CI: Frameworks » kdoctools » kf5-qt5 SUSEQt5.9 - Build # 47 - Fixed!

[CI System]

BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kdoctools/job/kf5-qt5%20SUSEQt5.9/47/
 Project:
kf5-qt5 SUSEQt5.9
 Date of build:
Wed, 31 Oct 2018 03:50:31 +
 Build duration:
1 min 13 sec and counting
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report100%
(1/1)83%
(5/6)83%
(5/6)70%
(345/490)51%
(147/287)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalssrc83%
(5/6)83%
(5/6)70%
(345/490)51%
(147/287)

KDE CI: Frameworks » kdoctools » kf5-qt5 SUSEQt5.10 - Build # 61 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kdoctools/job/kf5-qt5%20SUSEQt5.10/61/
 Project:
kf5-qt5 SUSEQt5.10
 Date of build:
Wed, 31 Oct 2018 03:50:31 +
 Build duration:
1 min 6 sec and counting
   JUnit Tests
  Name: (root) Failed: 1 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 3 test(s)Failed: TestSuite.kdoctools_install
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report100%
(1/1)67%
(4/6)67%
(4/6)68%
(335/490)48%
(138/287)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalssrc67%
(4/6)67%
(4/6)68%
(335/490)48%
(138/287)

KDE CI: Frameworks » kdoctools » kf5-qt5 SUSEQt5.9 - Build # 46 - Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kdoctools/job/kf5-qt5%20SUSEQt5.9/46/
 Project:
kf5-qt5 SUSEQt5.9
 Date of build:
Wed, 31 Oct 2018 03:39:36 +
 Build duration:
4 min 2 sec and counting
   JUnit Tests
  Name: (root) Failed: 1 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 3 test(s)Failed: TestSuite.kdoctools_install
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report100%
(1/1)67%
(4/6)67%
(4/6)66%
(324/490)44%
(127/287)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalssrc67%
(4/6)67%
(4/6)66%
(324/490)44%
(127/287)

KDE CI: Frameworks » kdoctools » kf5-qt5 WindowsMSVCQt5.11 - Build # 11 - Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kdoctools/job/kf5-qt5%20WindowsMSVCQt5.11/11/
 Project:
kf5-qt5 WindowsMSVCQt5.11
 Date of build:
Wed, 31 Oct 2018 03:39:36 +
 Build duration:
2 min 9 sec and counting
   JUnit Tests
  Name: (root) Failed: 1 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 2 test(s)Failed: TestSuite.kdoctools_install

KDE CI: Frameworks » kdoctools » kf5-qt5 SUSEQt5.10 - Build # 60 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kdoctools/job/kf5-qt5%20SUSEQt5.10/60/
 Project:
kf5-qt5 SUSEQt5.10
 Date of build:
Wed, 31 Oct 2018 03:39:36 +
 Build duration:
1 min 13 sec and counting
   JUnit Tests
  Name: (root) Failed: 1 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 3 test(s)Failed: TestSuite.kdoctools_install
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report100%
(1/1)67%
(4/6)67%
(4/6)66%
(324/490)44%
(127/287)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalssrc67%
(4/6)67%
(4/6)66%
(324/490)44%
(127/287)

KDE CI: Frameworks » baloo » kf5-qt5 SUSEQt5.9 - Build # 132 - Failure!

[CI System]

BUILD FAILURE
 Build URL
https://build.kde.org/job/Frameworks/job/baloo/job/kf5-qt5%20SUSEQt5.9/132/
 Project:
kf5-qt5 SUSEQt5.9
 Date of build:
Wed, 31 Oct 2018 00:39:34 +
 Build duration:
5 min 52 sec and counting
   CONSOLE OUTPUT
  [...truncated 345.62 KB...] auto error = QString("malformed property term (bad index): '%1' in '%2'\n").arg(prop).arg(arrAsPrintable()); ^In file included from /usr/include/qt5/QtCore/qcoreapplication.h:44, from /usr/include/qt5/QtCore/QCoreApplication:1, from /home/jenkins/workspace/Frameworks/baloo/kf5-qt5 SUSEQt5.9/src/tools/balooshow/main.cpp:21:/usr/include/qt5/QtCore/qstring.h:264:31: note: candidate: ���QString QString::arg(qlonglong, int, int, QChar) const��� Q_REQUIRED_RESULT QString arg(qlonglong a, int fieldwidth=0, int base=10,   ^~~/usr/include/qt5/QtCore/qstring.h:264:31: note:   no known conversion for argument 1 from ���QStringRef��� to ���qlonglong��� {aka ���long long int���}/usr/include/qt5/QtCore/qstring.h:266:31: note: candidate: ���QString QString::arg(qulonglong, int, int, QChar) const��� Q_REQUIRED_RESULT QString arg(qulonglong a, int fieldwidth=0, int base=10,   ^~~/usr/include/qt5/QtCore/qstring.h:266:31: note:   no known conversion for argument 1 from ���QStringRef��� to ���qulonglong��� {aka ���long long unsigned int���}/usr/include/qt5/QtCore/qstring.h:928:16: note: candidate: ���QString QString::arg(long int, int, int, QChar) const��� inline QString QString::arg(long a, int fieldWidth, int base, QChar fillChar) const^~~/usr/include/qt5/QtCore/qstring.h:928:16: note:   no known conversion for argument 1 from ���QStringRef��� to ���long int���/usr/include/qt5/QtCore/qstring.h:930:16: note: candidate: ���QString QString::arg(ulong, int, int, QChar) const��� inline QString QString::arg(ulong a, int fieldWidth, int base, QChar fillChar) const^~~/usr/include/qt5/QtCore/qstring.h:930:16: note:   no known conversion for argument 1 from ���QStringRef��� to ���ulong��� {aka ���long unsigned int���}/usr/include/qt5/QtCore/qstring.h:924:16: note: candidate: ���QString QString::arg(int, int, int, QChar) const��� inline QString QString::arg(int a, int fieldWidth, int base, QChar fillChar) const^~~/usr/include/qt5/QtCore/qstring.h:924:16: note:   no known conversion for argument 1 from ���QStringRef��� to ���int���/usr/include/qt5/QtCore/qstring.h:926:16: note: candidate: ���QString QString::arg(uint, int, int, QChar) const��� inline QString QString::arg(uint a, int fieldWidth, int base, QChar fillChar) const^~~/usr/include/qt5/QtCore/qstring.h:926:16: note:   no known conversion for argument 1 from ���QStringRef��� to ���uint��� {aka ���unsigned int���}/usr/include/qt5/QtCore/qstring.h:932:16: note: candidate: ���QString QString::arg(short int, int, int, QChar) const��� inline QString QString::arg(short a, int fieldWidth, int base, QChar fillChar) const^~~/usr/include/qt5/QtCore/qstring.h:932:16: note:   no known conversion for argument 1 from ���QStringRef��� to ���short int���/usr/include/qt5/QtCore/qstring.h:934:16: note: candidate: ���QString QString::arg(ushort, int, int, QChar) const��� inline QString QString::arg(ushort a, int fieldWidth, int base, QChar fillChar) const^~~/usr/include/qt5/QtCore/qstring.h:934:16: note:   no known conversion for argument 1 from ���QStringRef��� to ���ushort��� {aka ���short unsigned int���}/usr/include/qt5/QtCore/qstring.h:280:31: note: candidate: ���QString QString::arg(double, int, char, int, QChar) const��� Q_REQUIRED_RESULT QString arg(double a, int fieldWidth = 0, char fmt = 'g', int prec = -1,   ^~~/usr/include/qt5/QtCore/qstring.h:280:31: note:   no known conversion for argument 1 from ���QStringRef��� to ���double���/usr/include/qt5/QtCore/qstring.h:282:31: note: candidate: ���QString QString::arg(char, int, QChar) const��� Q_REQUIRED_RESULT QString arg(char a, int fieldWidth = 0,   ^~~/usr/include/qt5/QtCore/qstring.h:282:31: note:   no known conversion for argument 1 from ���QStringRef��� to ���char���/usr/include/qt5/QtCore/qstring.h:284:31: note: candidate: ���QString QString::arg(QChar, int, QChar) const��� Q_REQUIRED_RESULT QString arg(QChar a, int fieldWidth = 0,   ^~~/usr/include/qt5/QtCore/qstring.h:284:31: note:   no known conversion for argument 1 from ���QStringRef��� to ���QChar���/usr/include/qt5/QtCore/qstring.h:286:31: note: candidate: ���QString QString::arg(const QString&, int, QChar) const��� Q_REQUIRED_RESULT QString arg(const QString , int fieldWidth = 0,   

D15826: [Balooshow] Avoid out-of-bounds access when accessing corrupt db data

[Stefan Brüns]

This revision was automatically updated to reflect the committed changes.
Closed by commit R293:563dd3418b60: [Balooshow] Avoid out-of-bounds access when 
accessing corrupt db data (authored by bruns).

REPOSITORY
  R293 Baloo

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D15826?vs=44224=44524

REVISION DETAIL
  https://phabricator.kde.org/D15826

AFFECTED FILES
  src/tools/balooshow/main.cpp

To: bruns, #baloo, #frameworks, poboiko
Cc: anthonyfieroni, kde-frameworks-devel, ashaposhnikov, michaelh, astippich, 
spoorun, ngraham, bruns, abrahams

D16344: Do not try to fallback to "less secure" protocols

[Albert Astals Cid]

This revision was automatically updated to reflect the committed changes.
Closed by commit R241:e11d4d18f66a: Do not try to fallback to less 
secure protocols (authored by aacid).

CHANGED PRIOR TO COMMIT
  https://phabricator.kde.org/D16344?vs=43997=44509#toc

REPOSITORY
  R241 KIO

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D16344?vs=43997=44509

REVISION DETAIL
  https://phabricator.kde.org/D16344

AFFECTED FILES
  src/core/tcpslavebase.cpp

To: aacid, stikonas
Cc: jtamate, carewolf, dfaure, stikonas, kde-frameworks-devel, michaelh, 
ngraham, bruns

D16529: make libssh module default to the "new" libssh config by default

[Kai Uwe Broulik]

broulik accepted this revision.
This revision is now accepted and ready to land.

REPOSITORY
  R320 KIO Extras

BRANCH
  master

REVISION DETAIL
  https://phabricator.kde.org/D16529

To: sitter, broulik, asn
Cc: kde-frameworks-devel, kfm-devel, alexde, sourabhboss, feverfew, michaelh, 
spoorun, navarromorales, firef, ngraham, andrebarros, bruns, emmanuelp

Re: New contributor seeking guidance

[Andrew Crouthamel]

Thanks for wishing to get involved in KDE development!

We have the "junior-jobs" keyword in Bugzilla, which is a good place to start: 
https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED_status=CONFIRMED_status=ASSIGNED_status=REOPENED=junior-jobs%2C%20_type=allwords_id=1560073_format=advanced

The "usability" keyword is also a good option to look at, as a number of them 
are small jobs.

Feel free to respond back with any projects that catch your eye, and I'm sure 
we can help you out.

Andrew Crouthamel

‐‐‐ Original Message ‐‐‐
On Monday, October 29, 2018 9:15 AM, Remya Krishnan  
wrote:

> Hi all,
> I'm Remya, a CS sophomore and I would like to start contributing to KDE 
> projects. I'm a KDE user have been working on projects in C++/Qt for the past 
> few months. I would like to work towards beginner bugs. So, can anyone please 
> suggest me some beginner bugs to start with?
> With Regards,
> Remya Krishnan,
> [GitHub](https://github.com/krishremya)|[FOSS@Amrita](https://amfoss.in/accounts/165/)
> [Amrita University](https://www.amrita.edu/campus/amritapuri)

D16529: make libssh module default to the "new" libssh config by default

[Harald Sitter]

sitter created this revision.
sitter added reviewers: broulik, asn.
Herald added projects: Dolphin, Frameworks.
Herald added subscribers: kfm-devel, kde-frameworks-devel.
sitter requested review of this revision.

REVISION SUMMARY
  - rename module from LibSSH to libssh so casing is consistent with config
  - module now quietly attempts to find libssh by config and returns if found
  - if it was not found we'll fall back to manual lookup
  - adjust actual FOUND variable use for correct case
  - fix package case in properties set up (this is case sensitive)
  
  this is singularly necessary because the config file is not correctly
  packaged in ubuntu 18.04 (LTS)
  
  https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1800135/comments/2
  
  This reverts 3b1fd6bd8866da2dadd33705af53613236503efc 
.
  
  BUG: 400291

TEST PLAN
  builds in ubuntu docker container and with a system that has a proper config

REPOSITORY
  R320 KIO Extras

BRANCH
  master

REVISION DETAIL
  https://phabricator.kde.org/D16529

AFFECTED FILES
  CMakeLists.txt
  cmake/Findlibssh.cmake

To: sitter, broulik, asn
Cc: kde-frameworks-devel, kfm-devel, alexde, sourabhboss, feverfew, michaelh, 
spoorun, navarromorales, firef, ngraham, andrebarros, bruns, emmanuelp

Re: Getting Started With KDE

[Andrew Crouthamel]

Hi Alex,

Thanks for wishing to get involved in KDE development! It's good to hear you 
read through the Get Involved/Development page, that's a good start. As 
mentioned, we do have the Junior Jobs tag as a good start as well: 
https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED_status=CONFIRMED_status=ASSIGNED_status=REOPENED=junior-jobs%2C%20_type=allwords_id=1560073_format=advanced

The "usability" keyword is also a good option to look at, as a number of them 
are small jobs.

Although I'm a newbie to things, I would be glad to help you get your dev 
environment set up, and point you in the right direction, based on your 
interests. Feel free to respond back with any projects that catch your eye, and 
I'm sure we can help you out.

Andrew Crouthamel

‐‐‐ Original Message ‐‐‐
On Tuesday, October 30, 2018 2:14 AM, 王金鑫  wrote:

> Hello Pranam,
>
> Thanks for the response. I wish I could be a part of the Google Code-In but 
> unfortunately I am too old for this activities.
>
> Actually I am a first-year graduate student in Computer Science. But I 
> started learning Computer Science since the master. So I have only less than 
> one year experience with Computer Science and with programming. Thus I want 
> to find a project not too complicated and still having bugs to start with in 
> KDE. If you know such a project, please inform me. My prior experience was 
> mainly in C and python. And I know the basic of C++ and Java.
>
> I have read the development page thoroughly and it says I can email to 
> current developer to get some guidance. That drives me to send this email. If 
> anyone could give me some guidance to start, I would appreciate it.
>
> Thank you,
> Alex Wang
>
> Pranam Lashkari  于2018年10月29日周一 下午7:05写道：
>
>> Hello,
>> If you are a school student and 13-17 years old right now then there is a 
>> good opportunity for you as Google Code-In is on going right now. Take part 
>> in it if you are eligible. There are byte size tasks for students who want 
>> to get involved in open source.
>>
>> But if you are not eligible then have a look here
>> https://community.kde.org/Get_Involved/development
>>
>> Thank you,
>> Pranam Lashkari
>>
>> On Tue 30 Oct, 2018, 7:30 AM 王金鑫,  wrote:
>>
>>> To whom it may concern,
>>>
>>> Hello, I am a student new to KDE community. I want to get involved with KDE 
>>> development to hone my programming skills and make contribution to KDE. But 
>>> I don't know what work I can do and where do I start. Could anyone give me 
>>> some guidance? It would be better if we can discuss directly. Thank you all!
>>>
>>> Yours,
>>> Alex

D16523: [Extractor] Replace homegrown IO handler with QDataStream, catch HUP

[Stefan Brüns]

bruns marked an inline comment as done.
bruns added inline comments.

INLINE COMMENTS

> poboiko wrote in app.cpp:74
> I haven't work with `QDataStream` before, but shouldn't `m_inputStream >> 
> nIds` do the same? (and same below)
> And probably you should avoid magical constants (4, 8, etc) - better use 
> corresponding `sizeof`s

readRawData consumes N bytes, while operator>> consumes N + 
sizeof(serialization meta data).

I don't care to much for this code, as it is removed in the followup patch.

REPOSITORY
  R293 Baloo

REVISION DETAIL
  https://phabricator.kde.org/D16523

To: bruns, #baloo, #frameworks, ngraham, poboiko
Cc: lbeltrame, kde-frameworks-devel, ashaposhnikov, michaelh, astippich, 
spoorun, ngraham, bruns, abrahams

D16471: [RFC] Listen for added DBus interfaces instead of registered services

[Jan Grulich]

jgrulich added a comment.


  > This is RFC because:
  > 
  > I'm not sure whether it's guaranteed that InterfacesAdded is emitted on 
service registration as well or both connections are necessary
  
  I'm not sure about this either. I'll build it locally and try to use it for a 
while.
  
  > I don't know how it's possible to test this as org.kde.fakenetwork does not 
support the org.freedesktop.ObjectManager API
  
  The fakenetwork stuff supports or simulates only a small portion of NM dbus, 
we don't currently test secret agent at all.

REPOSITORY
  R282 NetworkManagerQt

REVISION DETAIL
  https://phabricator.kde.org/D16471

To: fvogt, #frameworks, jgrulich
Cc: kde-frameworks-devel, michaelh, ngraham, bruns

D16520: proper kwalletd dbus service file for the legacy name

[Stefan Brüns]

bruns added a comment.


  In D16520#350934 , @damjang wrote:
  
  > > but before doing this change the migration agent has to be changed.
  >
  > Can you expand on this what needs to be changed? I'd be happy to do it if 
it's in my capability
  
  
  There are two possibilities here:
  
  1. Scrap the migration agent completely, only manual wallet migration.
  2. Use execute + listen for NameOwnerChanged DBUS event instead of using the 
current **hackish** D-BUS activation
  
  Re 1., I would like to get  some feedback first -  #FreeBSD 
 is probably the last supported 
distribution still shipping KDE4, and only for 2 more months
  
  Pseudo-Code for 2:
  
kwallet4 = QStandardPaths::findExecutable("kwalletd");
if (kwallet4) {
QProcess process(kwallet4);
process.start();
// wait for 
DBusConnectionInterface::serviceRegistered("org.kde.kwalletd") signal
}

REPOSITORY
  R311 KWallet

REVISION DETAIL
  https://phabricator.kde.org/D16520

To: damjang, #frameworks, cfeck
Cc: bruns, apol, kde-frameworks-devel, michaelh, ngraham

D16523: [Extractor] Replace homegrown IO handler with QDataStream, catch HUP

[Stefan Brüns]

bruns added a comment.


  In D16523#350888 , @poboiko wrote:
  
  > That's nice! I'll test it a little.
  
  
  This step keeps binary compatibility with the current streaming format. The 
big cleanup happens in the next commit (D16524 
),

REPOSITORY
  R293 Baloo

REVISION DETAIL
  https://phabricator.kde.org/D16523

To: bruns, #baloo, #frameworks, ngraham, poboiko
Cc: lbeltrame, kde-frameworks-devel, ashaposhnikov, michaelh, astippich, 
spoorun, ngraham, bruns, abrahams

D15464: [server] Touch drag support

[David Edmundson]

davidedmundson accepted this revision.
This revision is now accepted and ready to land.

REPOSITORY
  R127 KWayland

BRANCH
  touchDrag

REVISION DETAIL
  https://phabricator.kde.org/D15464

To: romangg, #kwin, #frameworks, davidedmundson
Cc: davidedmundson, kde-frameworks-devel, michaelh, ngraham, bruns

D16520: proper kwalletd dbus service file for the legacy name

[Damjan Georgievski]

damjang added a comment.


  > but before doing this change the migration agent has to be changed.
  
  Can you expand on this what needs to be changed? I'd be happy to do it if 
it's in my capability

REPOSITORY
  R311 KWallet

REVISION DETAIL
  https://phabricator.kde.org/D16520

To: damjang, #frameworks, cfeck
Cc: bruns, apol, kde-frameworks-devel, michaelh, ngraham

D15826: [Balooshow] Avoid out-of-bounds access when accessing corrupt db data

[Igor Poboiko]

poboiko accepted this revision.
poboiko added a comment.
This revision is now accepted and ready to land.


  Yep, fine by me

REPOSITORY
  R293 Baloo

BRANCH
  oob2

REVISION DETAIL
  https://phabricator.kde.org/D15826

To: bruns, #baloo, #frameworks, poboiko
Cc: anthonyfieroni, kde-frameworks-devel, ashaposhnikov, michaelh, astippich, 
spoorun, ngraham, bruns, abrahams

D16416: z/OS CLIST file syntax highlighting

[Christoph Cullmann]

cullmann added a comment.


  Thanks for the needed info, will merge this.

REPOSITORY
  R216 Syntax Highlighting

REVISION DETAIL
  https://phabricator.kde.org/D16416

To: phily, #framework_syntax_highlighting, dhaumann, cullmann
Cc: cullmann, dhaumann, kwrite-devel, kde-frameworks-devel, michaelh, ngraham, 
bruns, demsking, sars

Re:Getting Started With KDE

[Ilya Bizyaev]

Hello Gregor,

I am not at all trying to put off a newcomer, but I firmly believe that using 
search engines can help one get involved in KDE development with ease.

If you find conflicting answers about getting involved in KDE, could you please 
report them? It's something we need to fix.

Best regards,
Ilya.

 On Вт, 30 окт 2018 11:56:14 +0300 codestr...@posteo.org wrote 

> Amazing what search engines can do these days!

This is ironic speech, isn't it? Such thing does not help to provide a warm 
welcome but rathers scares people off. Search engines can yield conflicting 
results and the question of the new guy is perfectly valid.

Maybe an apology could be issued... :-)

Gregor

 

Am 30.10.2018 09:39 schrieb Ilya Bizyaev:

Hello!

When working on open source projects, you shouldn't expect to always be guided 
by someone.

A quick Google search for "KDE get involved" gives me this awesome article: 
https://community.kde.org/Get_Involved

Then, assuming I need a simple task to start with, I google "KDE junior jobs", 
and get a link to https://community.kde.org/KDE/Junior_Jobs

Amazing what search engines can do these days!

Hope this helps.

Cheers,
Ilya.
 

 

 On Вт, 30 окт 2018 04:51:21 +0300  jinxi...@usc.edu wrote 

To whom it may concern,
 
Hello, I am a student new to KDE community. I want to get involved with KDE 
development to hone my programming skills and make contribution to KDE. But I 
don't know what work I can do and where do I start. Could anyone give me some 
guidance? It would be better if we can discuss directly. Thank you all!
 
Yours,
Alex

Re:Getting Started With KDE

[gregor.mi.sw]

 > Amazing what search engines can do these days!

This is ironic speech, isn't it? Such thing does not help to provide a
warm welcome but rathers scares people off. Search engines can yield
conflicting results and the question of the new guy is perfectly valid.

Maybe an apology could be issued... :-)

Gregor

Am 30.10.2018 09:39 schrieb Ilya Bizyaev: 

> Hello!
> 
> When working on open source projects, you shouldn't expect to always be 
> guided by someone.
> 
> A quick Google search for "KDE get involved" gives me this awesome article: 
> https://community.kde.org/Get_Involved
> 
> Then, assuming I need a simple task to start with, I google "KDE junior 
> jobs", and get a link to https://community.kde.org/KDE/Junior_Jobs
> 
> Amazing what search engines can do these days!
> 
> Hope this helps.
> 
> Cheers,
> Ilya.
> 
>  On Вт, 30 окт 2018 04:51:21 +0300 jinxi...@usc.edu wrote 
> 
>> To whom it may concern, 
>> 
>> Hello, I am a student new to KDE community. I want to get involved with KDE 
>> development to hone my programming skills and make contribution to KDE. But 
>> I don't know what work I can do and where do I start. Could anyone give me 
>> some guidance? It would be better if we can discuss directly. Thank you all! 
>> 
>> Yours, 
>> Alex
 

Re:Getting Started With KDE

[Ilya Bizyaev]

Hello!

When working on open source projects, you shouldn't expect to always be guided 
by someone.

A quick Google search for "KDE get involved" gives me this awesome article: 
https://community.kde.org/Get_Involved

Then, assuming I need a simple task to start with, I google "KDE junior jobs", 
and get a link to https://community.kde.org/KDE/Junior_Jobs

Amazing what search engines can do these days!

Hope this helps.

Cheers,
Ilya.


 On Вт, 30 окт 2018 04:51:21 +0300 jinxi...@usc.edu wrote 

To whom it may concern,

Hello, I am a student new to KDE community. I want to get involved with KDE 
development to hone my programming skills and make contribution to KDE. But I 
don't know what work I can do and where do I start. Could anyone give me some 
guidance? It would be better if we can discuss directly. Thank you all!

Yours,
Alex

Getting Started With KDE

[Jinxin Wang]

To whom it may concern,

Hello, I am a student new to KDE community. I want to get involved with KDE
development to hone my programming skills and make contribution to KDE. But
I don't know what work I can do and where do I start. Could anyone give me
some guidance? It would be better if we can discuss directly. Thank you all!

Yours,
Alex

New contributor seeking guidance

[Remya Krishnan]

Hi all,
I'm Remya, a CS sophomore and I would like to start contributing to KDE
projects. I'm a KDE user have been working on projects in C++/Qt for the
past few months. I would like to work towards beginner bugs. So, can anyone
please suggest me some beginner bugs to start with?
With Regards,
Remya Krishnan,
GitHub |FOSS@Amrita

Amrita University 

D16523: [Extractor] Replace homegrown IO handler with QDataStream, catch HUP

[Igor Poboiko]

poboiko added a comment.


  That's nice! I'll test it a little.

INLINE COMMENTS

> app.cpp:74
> +
> +memcpy(, buf, 4);
> +for (quint32 i = 0; i < nIds; i++) {

I haven't work with `QDataStream` before, but shouldn't `m_inputStream >> nIds` 
do the same? (and same below)
And probably you should avoid magical constants (4, 8, etc) - better use 
corresponding `sizeof`s

REPOSITORY
  R293 Baloo

REVISION DETAIL
  https://phabricator.kde.org/D16523

To: bruns, #baloo, #frameworks, ngraham, poboiko
Cc: lbeltrame, kde-frameworks-devel, ashaposhnikov, michaelh, astippich, 
spoorun, ngraham, bruns, abrahams

D15960: Don't check if file is directory based on mime-type

[Igor Poboiko]

poboiko edited the summary of this revision.

REPOSITORY
  R293 Baloo

REVISION DETAIL
  https://phabricator.kde.org/D15960

To: poboiko, #baloo, #frameworks, bruns
Cc: bruns, kde-frameworks-devel, ashaposhnikov, michaelh, astippich, spoorun, 
ngraham, abrahams

Re: Getting Started With KDE

[王金鑫]

Hello Pranam,

Thanks for the response. I wish I could be a part of the Google Code-In but
unfortunately I am too old for this activities.

Actually I am a first-year graduate student in Computer Science. But I
started learning Computer Science since the master. So I have only less
than one year experience with Computer Science and with programming. Thus I
want to find a project not too complicated and still having bugs to start
with in KDE. If you know such a project, please inform me. My prior
experience was mainly in C and python. And I know the basic of C++ and Java.

I have read the development page thoroughly and it says I can email to
current developer to get some guidance. That drives me to send this email.
If anyone could give me some guidance to start, I would appreciate it.

Thank you,
Alex Wang

Pranam Lashkari  于2018年10月29日周一 下午7:05写道：

> Hello,
> If you are a school student and 13-17 years old right now then there is a
> good opportunity for you as Google Code-In is on going right now. Take part
> in it if you are eligible. There are byte size tasks for students who want
> to get involved in open source.
>
> But if you are not eligible then have a look here
> https://community.kde.org/Get_Involved/development
>
> Thank you,
> Pranam Lashkari
>
>
> On Tue 30 Oct, 2018, 7:30 AM 王金鑫,  wrote:
>
>> To whom it may concern,
>>
>> Hello, I am a student new to KDE community. I want to get involved with
>> KDE development to hone my programming skills and make contribution to KDE.
>> But I don't know what work I can do and where do I start. Could anyone give
>> me some guidance? It would be better if we can discuss directly. Thank you
>> all!
>>
>> Yours,
>> Alex
>>
>

D16524: [Extractor] Use QDataStream serialization in place of cooked one

[Luca Beltrame]

lbeltrame accepted this revision.
This revision is now accepted and ready to land.

REPOSITORY
  R293 Baloo

BRANCH
  extractor

REVISION DETAIL
  https://phabricator.kde.org/D16524

To: bruns, #baloo, #frameworks, ngraham, poboiko, lbeltrame
Cc: kde-frameworks-devel, ashaposhnikov, michaelh, astippich, spoorun, ngraham, 
bruns, abrahams

D16523: [Extractor] Replace homegrown IO handler with QDataStream, catch HUP

[Luca Beltrame]

lbeltrame added a comment.


  In general (for my limited Baloo knowledge) this makes sense. You might want 
to add a few CCBUGs if you are aware of specific bugs this alleviates (@ngraham 
or someone from the bugsquad may help).

REPOSITORY
  R293 Baloo

REVISION DETAIL
  https://phabricator.kde.org/D16523

To: bruns, #baloo, #frameworks, ngraham, poboiko
Cc: lbeltrame, kde-frameworks-devel, ashaposhnikov, michaelh, astippich, 
spoorun, ngraham, bruns, abrahams