Another idea would be for some NodeJS libraries (like 'fs') to be ported to Qt. While some may cringe at that idea, they don't have to be in JS, just have the same API and similar function. Writing a bunch of classes for file IO is annoying.
> Sent: Wednesday, February 14, 2018 at 10:33 PM > From: "Jason H" <jh...@gmx.com> > To: "Frederik Gladhorn" <frederik.gladh...@qt.io> > Cc: qt-crea...@qt-project.org, interest@qt-project.org > Subject: Re: [Qt-creator] [Interest] [Development] Google Summer of Code > > I don't know how to use the suggestion template, but Qt needs a unified > approach to Notifications (Push on mobile, Desktop), if it is not already in > the works. > > > Sent: Tuesday, February 13, 2018 at 7:21 AM > > From: "Frederik Gladhorn" <frederik.gladh...@qt.io> > > To: interest@qt-project.org, qt-crea...@qt-project.org > > Subject: [Interest] [Development] Google Summer of Code > > > > Hi all, > > > > The Qt Project has been accepted as mentor organization for GSoC. Yay! > > https://summerofcode.withgoogle.com/organizations/5388456415461376/ > > > > We now should collect ideas for projects that students could work on, we > > started here: > > https://wiki.qt.io/Google_Summer_of_Code/2018/Project_Ideas > > > > For students it's a good idea to start talking to people in areas you are > > interested in already. We have not yet set the criteria for being accepted, > > but I imagine you should at least have pushed a change or two to Qt's > > codereview and have some C++ knowledge (or willingness to learn), depending > > on > > the task. > > http://wiki.qt.io/Qt_Contribution_Guidelines will help you getting started. > > > > Check out KDE's guidelines, many things apply to Qt (both for students and > > mentors): > > https://community.kde.org/GSoC > > > > I'd like to invite everyone to join #qt-gsoc on freenode. > > Ask questions about procedure in #qt-gsoc, programming questions then in > > #qt- > > labs on IRC/freenode. This mailing list is also a good place to discuss > > about > > potential work this summer. > > > > People that have been active in developing Qt can of course be mentors, let > > me > > know if you want to be part of the mentor team, signing up for mentoring is > > not a commitment yet. Note that you cannot be mentor and student at the > > same > > time. We will aim to have at least two mentors for each project and that > > mentoring does take time and commitment, it's not an easy task (not to > > discourage you, the more mentors we have, the better). > > > > The general overview page for Qt GSoC is here: > > https://wiki.qt.io/Google_Summer_of_Code/2018 > > > > Right now the organization page for GSoC shows "The Qt Company", which is a > > mistake we made when applying for the program. It of course should be the > > "Qt > > Project". > > > > This is the first time we'll participate in GSoC, so I don't expect us to > > get > > too many slots, we'll find out as we go, I do hope we'll have some great > > applications and get interesting things into Qt. > > > > Cheers, > > Frederik > > > > _______________________________________________ > > Development mailing list > > developm...@qt-project.org > > http://lists.qt-project.org/mailman/listinfo/development > > > > _______________________________________________ > > Interest mailing list > > Interest@qt-project.org > > http://lists.qt-project.org/mailman/listinfo/interest > > > _______________________________________________ > Qt-creator mailing list > qt-crea...@qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
