I personally don’t care what is under the hood, because I don’t understand any of it, I am an elderly Gynecologist dabbling a little in Perl and (even less in) LaTeX.
But as a long time Open Source user (privately and in my practice) I share the annoyance about this reversal of policy by the Qters. But if there was a way to negotiate some form of Qt LTS support for LyX, I am sure it could be crowded. el — Sent from Dr Lisse’s iPad Mini 5 On 12 Apr 2020, 12:12 +0200, Jean-Marc Lasgouttes <lasgout...@lyx.org>, wrote: > > > Le 12 avril 2020 00:35:02 GMT+02:00, Dr Eberhard Lisse <nos...@lisse.na> a > écrit : > > In the sense, of "how much would the crowdfunding be?" > > As a free software project, I am not sure this is a path we want to take. > Since we do not distribute only binaries, it is our users who would need a > license. > > But only time will tell whether stability becomes a problem. We are not tied > to a particular version in general. > > JMarc > > > > > el > > > > On 2020-04-10 18:08 , Dr Eberhard Lisse wrote: > > > What license would the development team need? > > > > > > el > > > > > > On 2020-01-28 17:33 , Pavel Sanda wrote: > > > > Just FYI ( https://www.qt.io/blog/qt-offering-changes-2020 ): > > > > > > > > ... > > > > Long-term-supported (LTS) releases will become available to > > commercial licensees only > > > > ... > > > > Starting with Qt 5.15, long term support (LTS) will only be > > available to > > > > commercial customers. This means open-source users will receive > > patch-level > > > > releases of 5.15 until the next minor release will become available. > > .. We are > > > > making this change to encourage open-source users to quickly adopt > > new > > > > versions. This helps maximize the feedback we can get form the > > community and to > > > > emphasize the commercial support available to those with longer > > product life > > > > cycles that rely on a specific Qt version. > > > > > > >
-- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel