[Development] Svar: Changes to Freenode's IRC

Andy Shaw andy.shaw at qt.io
Thu May 20 07:44:14 CEST 2021

I can’t speak for QtCentre as that is not something the Qt Project has any control over at all. But forum.qt.io is using NodeBB which is an OpenSource project, so unless I am missing something then it is free software.


Fra: Development <development-bounces at qt-project.org> på vegne av Jason H <jhihn at gmx.com>
Dato: onsdag, 19. mai 2021 kl. 18:24
Til: Lisandro Damián Nicanor Pérez Meyer <perezmeyer at gmail.com>
Kopi: development <development at qt-project.org>
Emne: Re: [Development] Changes to Freenode's IRC
> Hi!
> On Wed, 19 May 2021 at 12:30, Jason H <jhihn at gmx.com> wrote:
> >
> > Aren't all the kids these days moving to Discord?
> Discord is not free software, so it does not align well with a free
> software project.

QtCentre is not free software
forum.qt.io is not free software

What is the point of having alignment on the license of the service with the project license? Shouldn't the service be able to pick the best (for various definitions of "best") software for providing the service? Open Source servers may still require onerous terms of service to be used, the underlying code license implementing the service is a separate matter. I would say that as long as there is openly available clients for users to use, the license isn't as important as the terms of use for the service itself. (I'm sure Stallman would still disagree though) I'm open to preferring open services, but I just think the terms are more important than the license of the code base implementing the service, for me anyway.

I often wonder if Qt is still qualifies as "free software" under the new management? (Stopping LTS for OpenSource users in the middle of a LTS series really shattered my trust in Digia, if you can't tell)

Development mailing list
Development at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20210520/d0115c02/attachment.html>

More information about the Development mailing list