Spam detection software, running on the system "mx.qt-project.org",
has identified this incoming email as possible spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: It's obviously a bad decision made by people who don't
understand
what they're dealing with. It reminds me of this presentation from one of
the ownCloud/nextCloud founders explaining how venture capit [...]
Content analysis details: (5.0 points, 4.6 required)
pts rule name description
---- ---------------------- --------------------------------------------------
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was
blocked. See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information.
[URIs: qt-project.org]
3.3 RCVD_IN_SBL_CSS RBL: Received via a relay in Spamhaus SBL-CSS
[166.175.56.93 listed in zen.spamhaus.org]
0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60%
[score: 0.4999]
0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
provider (be.0[at]gmx.com)
0.0 RCVD_IN_MSPIKE_H4 RBL: Very Good reputation (+4)
[212.227.17.20 listed in wl.mailspike.net]
0.0 HTML_MESSAGE BODY: HTML included in message
0.1 PLING_QUERY Subject has exclamation mark and question mark
0.0 RCVD_IN_MSPIKE_WL Mailspike good senders
1.0 FREEMAIL_REPLY From and body contain different freemails
-0.3 NICE_REPLY_A Looks like a legit reply (A)
The original message was not completely plain text, and may be unsafe to
open with some email clients; in particular, it may contain a virus,
or confirm that your address can receive spam. If you wish to view
it, it may be safer to save it to a file and open it with an editor.
--- Begin Message ---
It's obviously a bad decision made by people who don't understand what
they're dealing with. It reminds me of this presentation from one of the
ownCloud/nextCloud founders explaining how venture capitalists destroyed
ownCloud, particularly around 8 minutes 30 seconds:
https://media.libreplanet.org/u/libreplanet/m/why-i-forked-my-own-project-and-my-own-company-31c3/
The Qt Company has set up a conflict between the community interest and
the company's interest and created an unstable situation. Hopefully the
Qt company doesn't make any more hostile changes like this or it may
very well go the way of ownCloud. It is clear at this point that talking
to them is pointless. That has been done already. The people making the
decisions have demonstrated that they do not care. The only thing that
might change their mind is making this silly decision irrelevant by
maintaining a community LTS fork.
On 1/7/21 12:41 PM, Ilya Diallo wrote:
Le jeu. 7 janv. 2021 à 18:30, Benjamin TERRIER <b.terr...@gmail.com
<mailto:b.terr...@gmail.com>> a écrit :
So basically for open source users the support of Qt 5.15 has
stopped 9 months before a usable version should be available.
Totally agree, but that point has already been made in the dev mailing
list.
So we can assume that Tuuka is fully aware of that problem. In that
context his "it's business as usual" response could be translated to
"la-la-la can't hear you".
Dropping the LTS for open source users would not have been an
issue this big if you had done it for any other version.
But doing it for 5.15, the last Qt 5 version is the worst timing.
If anything Qt 5.15 should have had an extended support time
It's the worst timing unless the purpose is to push (drag ?) users to
the commercial license - in that case the timing is perfect.
It's a business decision, time will tell if it's a good one or not.
Ilya.
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
--- End Message ---
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
