Redirecting the discussion to the right list... Jarek
Public ________________________________________ From: Jaroslaw Kobus <jaroslaw.ko...@qt.io> Sent: Monday, June 30, 2025 7:30 AM To: Volker Hilsheimer Cc: Qt Development Subject: Re: Requesting a repository for Qt Tasking Hi Volker, the reason for qt/qttasking was that some classes are defined in QtTasking namespace, like "If", "Else", etc... So, it was just for consistency. But I'm fine to call the repo qt/qttasktree. I don't anticipate any non-TaskTree related additions there. Jarek ________________________________________ From: Volker Hilsheimer <volker.hilshei...@qt.io> Sent: Sunday, June 29, 2025 7:49 PM To: Jaroslaw Kobus Cc: Qt Development Subject: Re: Requesting a repository for Qt Tasking > On 25 Jun 2025, at 12:10, Jaroslaw Kobus <jaroslaw.ko...@qt.io> wrote: > > Hi All, > > I would like to request a new repository for TaskTree solution, which is used > for more than 2 years already inside QtCreator. > More info: https://wiki.qt.io/TaskTree > > Name of the repository: qt/qttasking > Description: Task tree is a generic framework for automatic management of > asynchronous tasks > Responsible person: Jarek Kobus > Gerrit user/email: jkobus / jaroslaw.ko...@qt.io > > Best regards > > Jarek Hey Jarek, Given the description being explicit about Task Tree, is there any particular reason why the repo wouldn’t be called “qt/qttasktree”? I.e. do you anticipate any classes and frameworks to be added in the future that are not directly part of the TaskTree framework, but still fit into the wider domain of task scheduling and management? Volker -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
