uentMQ Team
From: Ville Voutilainen
Sent: Wednesday, August 30, 2023 7:53 PM
To: Volker Hilsheimer
Cc: Alex Blasche ; team fluentmq
; development@qt-project.org
Subject: Re: [Development] QtFluentMQ
On Tue, 29 Aug 2023 at 13:28, Volker Hilsheimer via Development
wrote:
>
> +1 in general.
On Tue, 29 Aug 2023 at 13:28, Volker Hilsheimer via Development
wrote:
>
> +1 in general.
Likewise, +1 in general.
My additional two cents: I have participated in Qt-using projects that
did communications between vehicles and a back-end
using AMQP, and used AMQP between back-end microservices. A
l the environment for you and walk you through the CLI &
perf tooling.
Best regards,
QtFluentMQ Team
From: Volker Hilsheimer
Sent: Tuesday, August 29, 2023 12:26 PM
To: Alex Blasche
Cc: team fluentmq ; development@qt-project.org
Subject: Re: [Develo
On Tuesday, 29 August 2023 03:26:08 PDT Volker Hilsheimer via Development
wrote:
> However, gerrit users should be individual contributors rather than a team
> user that is shared by multiple people, and the responsible person needs to
> have a gerrit user account.
That also applies to Copyright:
pport the
> process/development.
>
> --
> Alex
>
>
>
> From: Development on behalf of team
> fluentmq
> Sent: Sunday, August 27, 2023 03:55
> To: Volker Hilsheimer; development@qt-project.org
> Subject: Re: [Develo
+1, as indicated before
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
: [Development] QtFluentMQ
Hello,
Thanks for welcoming the project everybody.
> AFAIR we haven't bike shedded over the commercial value of a new repository,
> the architecture of the code it shall hold, or its licensing before. I don't
> think we need to.
To be fair, while we
ground
Br
QtFluentMQ Team
From: Volker Hilsheimer
Sent: Saturday, August 26, 2023 11:34 AM
To: Ulf Hermann ; development@qt-project.org
Subject: Re: [Development] QtFluentMQ
> On 26 Aug 2023, at 10:09, Ulf Hermann via Development
> wrote:
>
> H
> On 26 Aug 2023, at 10:09, Ulf Hermann via Development
> wrote:
>
> Hi,
>
> The usual way to request a repository, playground or not, is a mail like this:
>
> https://lists.qt-project.org/pipermail/development/2022-August/042900.html
>
> If the request is not totally outlandish it's usually
Hi,
The usual way to request a repository, playground or not, is a mail like
this:
https://lists.qt-project.org/pipermail/development/2022-August/042900.html
If the request is not totally outlandish it's usually granted, possibly
after some bike shedding over the name and location.
AFAIR w
___________
From: team fluentmq
Sent: Saturday, August 26, 2023 2:38 AM
To: Vladimir Minenko
Cc: development@qt-project.org
Subject: Re: [Development] QtFluentMQ
Hello,
First of all, thanks for being supportive of the project.
>>I do not quite understand who exactly
#x27;d be ok to open the relevant part of our
sources already in the playground repo while you settle on the integration part
in which case, We'd say let's Hack On !
Br
From: Vladimir Minenko
Sent: Friday, August 25, 2023 9:17 AM
To: team fluentmq
On Friday, 25 August 2023 00:17:08 PDT Vladimir Minenko via Development wrote:
> Hello team fluentmq,
>
>
> > We would need you guys to confirm that you'd have the ressource model and
> > the benefit to integrate the module to the commercial offer
>
> I do not quite understand who exactly you e
Hello team fluentmq,
> We would need you guys to confirm that you'd have the ressource model and the
> benefit to integrate the module to the commercial offer
I do not quite understand who exactly you expect to confirm and what you mean
with "ressource model”.
Despite that, I also think the i
Hello,
>>If that is the ambition in the longer term, but you’d nevertheless want to
>>start developing the project as a Qt module, then a repository in the
>>playground/ namespace on our gerrit server can be a good start.
That's actually the status we've left the discussion at from the backlog.
Hello QtFluentMQ Team,
The project as you have described it sounds very cool and could be interesting
for many Qt users building distributed systems. So thanks for the work so far
and for reaching out!
As for providing a repository on our gerrit server for your project, and
perhaps moving it u
Hello,
I forgot to mention that we're looking forward to a qtlab repository creation
to migrate the Kafka soruces and developpe the AMQP support project as a Qt
module.
The design proposal is built around the bridge pattern which is a PIMPL tree.
We have people rooting for a plugin based arch
The "QtFluentMQ" project aims to create a user-friendly and versatile message
queue (MQ) client using the Qt 6 framework. This client seamlessly handles
communication with major MQ platforms. The first release would implement the
AMQP protocol thus supporting RabbitMQ, ActiveMQ, Apollo, IbmMQ, A
18 matches
Mail list logo
