Why didn’t this project use one of the well known and (court) tested open source licenses but instead opted to use Yet Another New License that is not adhering to the Open Source Definition by the OSI? Muddying the waters this way isn’t really helpful from a community perspective, it only serves to help corporate lawyers and makes reuse of code in other projects a legal risk. Le sigh.
The interesting thing is how Heather Meeker carefully avoids mentioning the obvious approach that is perfectly compliant with laws and regulations around copyright and use: opt-in. If a new way of using information arises, asking for consent through opt-in is the obvious choice. But also the most costly one.
That's why the "forgiveness instead of permission" approach is seen as somehow heroic, when it actually simply is abuse.
So instead of having a few European companies offering DNS resolvers for the EU under documented rules, this article argues its better to leave this to a few US companies that have effectively zero rules to follow?
They don’t charge. You can donate or become a paying member of the association. Or not. Up to any User to decide. (I am a paying member since quite some time)
My little e-mail Server on an OVH VPS is happily sending and receiving e-Mails to/from the big ones without problems for my 20+ domains. Just a basic postfix/dovecot setup with letsencrypt certificates and SPF/DKIM/DMARC working the way it should. I described everything in a short blog series at https://jan.wildeboer.net/2022/08/Email-0-The-Journey-2022/ in case you are interested.
Without concrete examples of good v bad behaviour it’s a lonely call in the void, IMHO. Without a clear commitment to solid versioning, where it is clear what is considered ready and stable v WIP it also doesn’t really help. Good will on all sides depends on understanding and communicating. This is a task for all.
I’ve read the article 3 times now. I still fail to find the part where git broke. I also fail to find a concise explanation on what the solution is. I may need a beer to understand this.
The app update limits collected data to 14 days. While the storage limit is only defined by the memory capacity of your smartphone running the app. But to add insult to injury, in my case it silently deleted all data except for the last 9 days. I am furious.
Trademarks. Contracts. Egos. I was there when it all happened. When Oracle refused to transfer the trademarks to the Document Foundation. When loud voices on many sides shouted at each other. Leading to the current situation. My current position: Who cares. ODF and Libre Office's community managed to move forward. Let the ASF have their Open Office.
As a software maintainer/distributor, I don’t think we at Red Hat are the ones responsible to publish data sheets. That’s the job of the hardware manufacturer/vendor. When they decide to only offer it in non-public ways but allow us to help with getting the drivers upstream AND open source, it is a deal you might not like, but I, as a pragmatist can accept. We’re not the only Linux distributor working this way. Ubuntu/Canonical and SUSE don’t work that different from us on this. Again. You may not like it, and I understand that, but it has lead to making Linux a first class OS on Lenovo with an upstream first goal. I like it that way, even if it can become even better and more open.
> Even the modern Ts (professional series) don't have a CDROM drive anymore.
Missing a DVD drive I * might* be able to understand, but CD-ROM? That ship has sailed, latest with universal support for USB boot or booting via network, IMHO.
When firmware was stored in ROM/EEPROM, most FOSS folks had no problem with it. It was considered part of the hardware, so not that relevant. But when these were moved out of non-volatile memory (mostly for cost reasons), that changed the picture for some. While the result, after booting, is effectively the same. So no, I am not on the side that sees firmware blobs as something that MUST be made open. It would be good if it were, definitely. But it’s not a deal breaker for me, as long as the blobs are freely redistributable, for example via fwupd. Again, that’s my personal opinion.
No. I specifically said drivers, not firmware blobs. As long as these blobs are freely redistributable, I personally have no problems with them. I understand some people do and that is understandable, but I don’t subscribe to that. This started at a time where non-volatile memory for firmware became a cost factor and companies decided to save a few bucks on the BoM and upload the blob as part of the initialisation/boot process. Which is fine with me.
Most drivers are upstreamed anyways, nowadays. We get some early access and work with that, but the resulting code is always upstreamed and open source, so feel free to use that code at any time.
Oh, FTR, none of my laptops had nVidia graphics. Intel graphics has always been Good Enough(tm) for my use case (travelling evangelist who presents at conferences and wants enough oomph for some demos on the laptop itself with virtualisation and/or containers).
Nvidia graphics causing problems on laptops is a known issue that only Nvidia can fix by opening up more.
That relationship has become a lot better over the years. We get early access to new hardware, Lenovo did a lot to get fwupd integrated, etc.
No OEM preload necessary on the business line machines. RHEL/Fedora installs just fine OOTB. Some problems remain, especially with Thunderbolt (docking stations) but that’s not just Lenovos fault, IMHO.
Disclaimer: I am a Red Hatter. We get Thinkpads/Lenovos since years, we install RHEL (Red Hat Enterprise Linux) or Fedora on them. I started back a long time ago with a X31, after that a X40, an X220, a X230, X1 2nd gen and am now on a X1 carbon 7th gen. They have been rock solid for me, except the x220 which loved to bork the hard drive for unknown reasons every 4-6 months.
Lenovo has listened and acted on our requests in a very good way, the Linux support has become better and better over the years, IMHO and experience.
So no, this rant does notbresonate with me and my 16 years experience at all.
I‘ve had my share of flamewars with Jörg, as had many others. But it was always civilised and never went ad hominem. I will miss him. The few times we met in person, we had some good laughs about many things. Tough, but nice guy. Left too soon.
Kind of curious why the article didn't mention HPs PARISC architecture. IIRC, HP switched away from PARISC to Itanium at the time. I guess because they saw that managing your own architecture comes at a huge cost? I very well remember how Itanium was heavily promoted by HP to existing PARISC customers as the natural upgrade path and how they played down x86 as unreliable PC derived stuff that no-one should put in a datacenter ;)
Guy who claims to run systems in the hft space, responsible for millions of trades with high values, can’t be bothered to actually pay for support, relies on community and blames everyone but himself for being left alone with his mess. Not sorry.