Hi all, I'd also like to say a big thank you for all the work you have put into Qt 3D. It is a great graphics API and is getting better with each release. I would be more than happy to be a co-maintainer of Qt 3D Render and will also help out with Qt 3D Core and the other modules.
I agree with Laszlo that it is a good idea to sync up on the future of Qt 3D and the Qt graphics stack. We need a clear vision of what the scope of Qt 3D should be and how we should handle existing and new features that fall both inside and outside of this scope. As we add support for more backends, we also need to decide on how much of the underlying graphics API, such as OpenGL flags, should be abstracted away. The transition to Qt 6 is a good opportunity to make some changes in this area. It will be great to have a unified 2D-3D engine that can run on top of the different graphics backends and be a flexible foundation for both Qt Quick's Scene Graph, Qt 3D Studio, and other modules like Qt Charts and Qt Data Visualization. Cheers, Svenn-Arne On 14. sep. 2018 15:52, Laszlo Agocs wrote: > Hi guys, > > Thanks, Qt 3D is almost certainly going to be an important piece in Qt 6. > Once the dust settles and we have a clear view of the new maintainership > structure, we should definitely sync up on the state of things and plan a bit > ahead since there's plenty to be done and think about, especially with Qt 6 > and its potentially unified 2D-3D engines in mind. (renderer optimizations, > graphics API abstractions (RHI), shader graphs, some new features of course, > ...., fun times ahead :) ) > > Cheers, > Laszlo > > -----Original Message----- > From: Development <[email protected]> On > Behalf Of Lars Knoll > Sent: fredag 14. september 2018 14.50 > To: Tuukka Turunen <[email protected]> > Cc: Qt development mailing list <[email protected]>; Sean Harmer > <[email protected]> > Subject: Re: [Development] Qt 3D Maintainership > > Hi Sean, > > First of all thank you for all the great work on Qt 3D over the last years. > Qt 3D has become a very important part of Qt, and I believe that parts of it > will get a much more central role in our graphics stack when we move towards > Qt 6. > > I’ve been discussing a bit with the graphics team in Oslo, and I think the > idea of having Laszlo as a co-maintainer is good. I would also like to > propose that we have Svenn-Arne as the co-maintainer for the renderer > component. He’s been doing a lot of good work in that area over the last year. > > We’re also trying to find candidates to help with some of the other modules, > and I hope we’ll at least one more person we can nominate there next week. > > Cheers, > Lars > > >> On 14 Sep 2018, at 12:47, Tuukka Turunen <[email protected]> wrote: >> >> >> Hi Sean, >> >> Yes, Qt 3D certainly growing both in size and importance. Happily also the >> number of people working on it has been growing nicely. >> >> In addition to you and Paul, I believe we should be able to find 1-2 >> additional from developers of The Qt Company working on Qt 3D. >> >> Would it be possible to have someone from KDAB to maintain Qt 3D Extras? >> That is an area we have not touched that much. >> >> Yours, >> >> Tuukka >> >> On 14/09/2018, 13.29, "Development on behalf of Sean Harmer via >> Development" <[email protected] on >> behalf of [email protected]> wrote: >> >> Hi All, >> >> my time available for Qt 3D outside of work, has as of late, been >> reduced due to increased family commitments - the good kind, but time >> consuming nonetheless. >> >> Given how Qt 3D has grown from our simple experiments in making 3D >> possible with Qt to the highly-configurable, multi-module, data >> processing monster it is today I feel it is no longer possible, nor >> wise, for me to maintain alone. Additionally, it looks as if Qt 3D will >> form an important piece of the graphics stack for Qt 6. >> >> As such I would like to propose that we split the maintainership and I >> would propose that Laszlo Agocs becomes co-maintainer. I am still happy >> to co-maintain and I have plenty of ideas about improvements we can make >> both within the Qt5 and Qt 6 time frames. We have learned a lot whilst >> developing Qt 3D and I think we can make it even better for Qt 6. >> >> I would also suggest that we find maintainers or co-maintainers for the >> sub-modules. I would propose Paul Lemire as (co-)maintainer for the >> render module. I'm happy to keep driving the animation module and help >> with qt3dcore. Other nominations are of course welcome. >> >> Kind regards and have a great weekend, >> >> Sean >> _______________________________________________ >> Development mailing list >> [email protected] >> http://lists.qt-project.org/mailman/listinfo/development >> >> >> _______________________________________________ >> Development mailing list >> [email protected] >> http://lists.qt-project.org/mailman/listinfo/development > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
