Re: Inactive mailing lists
On Friday, 28 April 2023 09:12:46 PDT Volker Krause wrote: > - kde-scm-interest: this was used for coordinating the migration to Git, > something that is long done. Since then, kde-scm-interest has become the place to ask for help using the tool for other projects. There were posts by third parties in 2017, 2019 and 2020, which did get answered. One post from June 2022 did not get an answer and was the last post on the mailing list until Joseph's last week. That said, I don't think we should keep the list. All the knowledge we once had about the tool we wrote and used is long gone. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel DCAI Cloud Engineering
Re: Extending the license policy to include Apache-2.0
On Wednesday, 22 September 2021 03:57:37 PDT Jonathan Riddell wrote: > I think I'd be against adding it to the policy, the aim of the policy has > always been to keep it simple which licence to use so ensure code and be > swapped around within and outwith KDE with minimal worry about different > licences. Apache 2 doesn't add any useful use case to our licences that > isn't already covered by another one, it's just a bit more explicit about > the intended uses. If we add it, I recommend we add instead "Apache2 OR GPL-2.0-or-later". It can't be Apache 2 only. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel DPG Cloud Engineering
Re: Extending the license policy to include Apache-2.0
On Friday, 17 September 2021 08:41:08 PDT Andreas Cord-Landwehr wrote: > Yet no, it is not orthogonal IMHO, because our license list strives for > compatibility between the licenses in our code base. If we would say that > the GPL-2.0-only files are legacy/policy violation/or just deprecated, then > I find it hard to say that we disallow Apache 2 while allowing e.g. > BSD-2-Clause. My main argument would be that Apache 2 is fully compatible > with GPL-3.0 (at least in the regard when being integrated with GPL-3.0 > code) and in my understanding it falls into the license policy section > about "if it helps with compatibility". I'm not arguing that. I actually agree with you: it is a good licence and chosen by many projects. I meant OpenSSL 3's licence choice is an orthogonal problem. Code that is GPLv2-only today will not become compatible with OpenSSL 3 just because we add a new option. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel DPG Cloud Engineering
Re: Extending the license policy to include Apache-2.0
On Thursday, 16 September 2021 10:58:55 PDT Andreas Cord-Landwehr wrote: > Hi, now with the very recent release of openssl 3.0 [1], I think we have to > eventually face the question what to do in this regard. But the not too > small number of historic GPL-2.0-only files [2] yet is a problem. That's an orthogonal problem. To be clear: it is a problem for the GPL-2.0- only code, but it's irrelevant as to whether we accept Apache-2.0 content in KDE code. We already require at least GPLv3 and the v3 is compatible with Apache-2.0. So we already have a solution and all compliant code has no problem with OpenSSL 3.0. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel DPG Cloud Engineering
Re: Qt goes "commercial only! - what now?
On Thursday, 7 January 2021 08:52:12 -03 Mathias Homann wrote: > Am Donnerstag, 7. Januar 2021, 11:01:23 CET schrieb David Edmundson: > > From a user point of view, there will be no impact. > > are you sure? To me it sounds as if only commercial "licensees" will have > access to the latest sources and/or security fixes, which also won't get > backported anymore... Let me be very clear so there's no mistake: all security issues will be dealt with in all branches, to the extent that we are able to reproduce them and confirm them. We usually identify down to the point release where security issues apply and will continue to do so. All non-security fixes will be available in later branches, per Qt Project policy. Non-commercial users will simply not see them backported (and thus adjusted, if necessary) to the older versions. That unfortunately also means we won't know which commits will be selected for backporting. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel DPG Cloud Engineering
Re: Help with KDE PIM and Google Privacy Policies needed
On Thursday, 5 March 2020 23:20:51 PST Nicolás Alvarez wrote: > If I add my Google account to KDE PIM, it will sync my email and > calendar events with Akonadi. Third-party apps can then access my > email and calendar events via Akonadi. > If I add my Google account to iPhone, it will sync my calendar events > with the system calendar database. Third-party apps can then access my > calendar events via EventKit. > If I add my Google account to Mozilla Thunderbird, it will sync my > email with its database. Third-party addons running inside Thunderbird > can then access email content. > > Apple can give its million appstore apps access to Google calendar > data, and Mozilla can let addons access email data, but we can't? What > do they do differently? > > Also, Linux desktop systems are usually not sandboxed. [cut] Given that last, should those third-party plugins be considered third party at all? Those plugins are running in the user's set up, installed and configured by the user, using the same permission domain as Akonadi. Shouldn't therefore they be considered "first party" -- that is, the same party as Akonadi itself? -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel System Software Products
Re: Facebook Business verification
On Saturday, 22 June 2019 22:33:26 PDT Lydia Pintscher wrote: > > Has an open source project already undergone this process or experience > > with > > it? > > This is what the e.V. is there for for KDE. Do you want the KDE e.V. to > handle this for you? In this case please get in touch with the board at > kde-ev-bo...@kde.org. I think before the e.V. signs the Business Verification, the question is whether there's a solution for open source applications. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel System Software Products
Re: Shutdown of paste.kde.org
On Saturday, 2 February 2019 11:45:40 PST Ben Cooksley wrote: > Following the shutdown we will be erasing the database, so any pastes > not saved elsewhere before this time will be lost. > > Should anyone have any questions regarding this, please let us know. Hello Ben Can you create a redirect to the currently supported/recommended paste/snippet site from paste.kde.org? I'm not asking for the database of old pastes, jut a redirect to the main landing page for those who may have muscle memory of typing "paste.kde.org". -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center
Re: Anyone going to OSCON?
On Thursday, 28 June 2018 13:16:41 PDT Lydia Pintscher wrote: > Is anyone going to OSCON? We have the opportunity to take part in > OSI's 20th birthday celebrations there. If someone is going anyway > it'd be good to take up this offer. Let me know if you're going and we > can talk details. No, but I live in Portland. I don't have a lot of time available, but if there's something important I can try and help. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center
Re: Test your applications on Wayland
Em quarta-feira, 12 de outubro de 2016, às 07:47:44 CEST, Martin Graesslin escreveu: > Best is of course if Qt would release a 5.7.1, so that this cherry-picking > is no longer required. Most important is the first of those three patches > as without the applications are pretty much unusable. Should happen in the next couple of weeks, now that 5.6.2 is closed. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center
Re: We now have an Advisory Board
On quarta-feira, 28 de setembro de 2016 18:26:18 PDT Aleix Pol wrote: > > Do you know if the Linux Foundation was approached about sitting in the > > AB? If not, or if so and they didn't reply (instead of declining), do you > > want me to talk to them? > > > > I'll be in Berlin next week for LinuxCon and could facilitate a > > discussion. > > They haven't been contacted, but they should be at some point to see > if they'd be interested in becoming patrons, and join the Advisory > Board. > > Feel free to talk to them about the possibility and get them in touch > with the board (or with any of us if it feels more adequate). The LF is a non-profit. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center
Re: We now have an Advisory Board
On terça-feira, 27 de setembro de 2016 16:49:30 PDT Thomas Pfeiffer wrote: > in case you haven't read the Dot article [1] yet: > KDE now has an Advisory Board, consisting of KDE e.V.'s Patrons as well as > organizations using our software on a large scale (currently LiMux) and > other NGOs with visions/missions similar to ours. The list of members is on > the Advisory Board page [2]. Do you know if the Linux Foundation was approached about sitting in the AB? If not, or if so and they didn't reply (instead of declining), do you want me to talk to them? I'll be in Berlin next week for LinuxCon and could facilitate a discussion. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center
Re: [kde-community] Register for QtCon
On quinta-feira, 4 de agosto de 2016 14:38:55 PDT Kenny Duffus wrote: > On Thursday, 4 August 2016 14:57:37 BST Sebastian Kügler wrote: > > On donderdag 4 augustus 2016 10:07:53 CEST Lydia Pintscher wrote: > > > If you plan to come to QtCon and have not registered yet please do so > > > asap. On-site registration right at the event is highly discouraged > > > this year as it makes the organisation of the event considerably > > > harder for us. Please do register in advance at https://conf.qtcon.org > > > > Is this also necessary for speakers? > > Like every year at Akademy yes speakers need to register to attend Even keynote speakers. I remember once that Aaron was a keynote and had not registered... -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Changes to mailing list behaviour
On terça-feira, 2 de agosto de 2016 14:16:35 PDT Milian Wolff wrote: > Does this include the List-Id headers etc. used for filtering of mailing > list emails? I'll just unsubscribe from any and all mailing lists that no longer send a List-Id header. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Licensing question with header-only libraries
On Sunday 24 January 2016 16:12:39 Jonathan Riddell wrote: > inline functions and templates (ten or fewer lines in length), The restriction pretty much sets header-only libraries of any value out of luck for this compliance. C code usually has small functions and templates. Modern C++ code is usually template-heavy, with hundreds or thousands of lines of code. Or more. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Licensing question with header-only libraries
On Sunday 24 January 2016 10:15:37 Ivan Čukić wrote: > I have never seen a project under LGPL+exception, that is the reason I > wrote GPL+exception. You may have heard of one. It's called Qt. From 2009 to 2016, it's been licensed as LGPLv2.1 + exception. http://code.qt.io/cgit/qt/qtbase.git/tree/LGPL_EXCEPTION.txt?h=5.6 -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Official KDE mirror on github
On Wednesday 16 September 2015 13:57:37 David Edmundson wrote: > I am great. > > https://github.com/kde is now ours. Awesome! You are indeed great! -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Trademark clause in the Manifesto
On Tuesday 28 July 2015 09:37:40 Boudewijn Rempt wrote: I don't think it says that, but I also don't think that it can work like this. If I disappear or disband the Krita Foundation (which owns the trademark), then how would this transfer be implemented? It's probably something that will be specific for each situation, but as it is, I'm totally unsure how this is supposed to work in practice. Another aspect is to consider the difference between a registered trademark and a non-registered one. Registered trademarks ® are regulated Intellectual Property, for which one pays a fee and has rights and duties. It can only be ceded through a proper contract. I'm not sure a verbal contract or the manifesto would serve, here. A non-registered trademark ™ is just anything you claim as an identifying mark. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Closing the kde-core-devel mailing list
On Wednesday 27 August 2014 07:51:54 Laszlo Papp wrote: My suggestion: use qt-inter...@qt-project.org for supporting people who want to just use KF5, without developing it. I would understand that suggestion if the kde frameworks became official Qt 5 add-ons, although even then one could say to have modularized lists rather than a catch-all list where the relevance to your interest might be X % or lower. I think it is ok not to have a catch-all mailing list for everything that may end up in inqclude, i.e. qt libraries. It's not going to become official, as KF5 will not use Gerrit and will not adopt the Qt CLA. However, I don't see a problem answering questions about KF5, Qxt, Qwt and other Qt-based libraries in qt-interest. In fact, I encourage it because it increases the Qt ecosystem and attractiveness. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Closing the kde-core-devel mailing list
On Tuesday 26 August 2014 15:28:09 Aaron J. Seigo wrote: Simple frameworks support list for random people who are not involved with KDE in any way and don't care about development (of any kind) inside of the community, but are just looking for support and possibly willing to offer support too, Yes, that's what kde-devel is supposed to be for. If we take away the review board email, much of the traffic is exactly that. My suggestion: use qt-inter...@qt-project.org for supporting people who want to just use KF5, without developing it. That would leave kde-devel for what it's been used for the past 15 years: discussing development of applications that are tightly integrated with KDE's desktop environment (i.e., Plasma desktop). -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Closing the kde-core-devel mailing list
On Tuesday 26 August 2014 22:24:24 Eike Hein wrote: My 2 cents: KDE is a the name of a community that makes a whole bunch of things, chiefly among them right now: * A set of libraries/frameworks that complement Qt and help with building applications and workspaces that run nicely on a variety of systems (and within a variety of work- spaces, in case of the applications). * A set of workspaces, taking advantage of the above. * A set of applications that integrate well with the above thanks to the prowess of those frameworks, but also inte- grate well with other workspaces. It follows from this that kde-devel (= KDE development) is a bad name for discussing development of applications that are tightly integrated with Plasma, for two reasons: On a blue-sky situation, yes. My point is that the kde-devel mailing list has 15+ years of history. When k- c-d was created and split the development of kdelibs, what remained in kde- devel was general help about using the KDE libraries to write KDE applications that integrated with the KDE desktop. So yeah, let's please not make a write apps for Plasma mailing list. It doesn't fit what KDE is today - and that's a good thing, because our ambitions have become grander and our means to accomplish them have, too. I'm not asking we encourage that. But I am saying that: * we need a place for discussion to happen if it happens (it will) * no one but KDE developers will use the kde-devel mailing list -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Closing the kde-core-devel mailing list
On Monday 04 August 2014 20:36:44 Vishesh Handa wrote: Hello people Random Idea: How about we close the k-c-d mailing list? It's main purpose used to be to discuss kdelibs changes, but now since we have kde-frameworks, the mailing list seems less useful. We already have kde-devel for other generic kde stuff. How about the opposite? Close the frameworks list and move that discussion back here, where it belongs. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
