the company has been pushing forward with its flagship phones for the betterment of the entire Android ecosystem, rather than just its own benefit
Pretty sure making it harder to install a custom ROM (potentially without GApps) on Pixel phones is mostly driven by its own benefit.
So not setting up a Discord in the first place is not an option because some people are so desperate to get feedback even though they are annoyed by feedback?
Who forces him to respond to such messages on Discord? He can just not engage with people of whom he thinks are idiots.
If he doesn’t want to engage with users at all, maybe not set up a Discord in the first place.
Normal people would just invite distribution packagers to develop fixes upstream.
To write a script that checks out upstream code and compiles it locally is not a distribution by a 3rd party. The code comes directly from Stenzek. That’s why he puts the Arch check there.
If that script happens to do a search and replace of archlinux with some random jibberish (so the check is no longer for archlinux), that’s still not a distribution of modified code because all code modifications happen locally.
AUR can. It’s just locally checking out the code from git and compiling it locally as well. I’m not a pro AUR maintainer but I’m not aware of a single AUR entry that ships software source code directly from AUR.
CC4.0 licenses work for code. The language was made generic and no longer talks about performing music on stage and such.
Better to use CC NC for non commercial works than to homebrew your own text. CC BY and CC BY SA are GPLv3 compatible.
True but there is a workaround: a patchset to a specific upstream git commit and local compilation. Pretty much what PKGBUILD already does. LAME was developed this way for years. It was a patchset to reference source code under a nonfree license.
I hope F-Droid comes to EGS. Tim Sweeny is a crusader for openness after all…
“What? People are doing things with my Apache project I don’t like!?”
Well, at least for the GPL https://www.gnu.org/licenses/gpl-faq.html exists, so there is no excuse because of incomprehensible legalese.
What was this “unpublished code”? Something committed to a public git repository where all the code is under GPL? You act as if redistribution of GPLed code was somehow illegal or at least immortal. It’s not. It’s the foundation of the whole idea behind open source.
If that “unpublished code” was stored only on his hard drive and a hacker obtained it illegally, that would be an entirely different topic but that’s completely outside the scope of upstream source code license. That would be an outright crime. Developers at AMD, for example, write Linux driver code for AMD hardware. Then before that code leaves AMD, AMD lawyers need to clear it before it gets published to the Linux Kernel Mailing List for review. Sometimes code is not cleared, so the developers need to rewrite it. As long as the code is behind closed doors, it’s not published (therefore the GPL does not yet apply) but as soon as it’s posted for review, it’s public GPL code and everybody can to everything to it as far as the GPL permits.
This is even spelled out in GNU’s official GPL FAQ. Edit: https://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic
And now it’s even worse. Great work.
The solution would be to file trademark and use trademark law to to grant use of the name only to packages that comply with certain mandates. That’s how Mozilla handles it. Source code license is the completely wrong approach for this thing.
An approach without tantrums would be to ask Linux packagers to handle packaging needs directly upstream at DuckStation and whenever a new release is made with a bit of scripting to file an automated update request for the packages. I would rope in Arch AUR, Debian Sid, a dedicated Ubuntu PPA, Fedora RPMFusion or a Fedora COPR, and Flathub this way.
Is there a specific interaction that made them angry?
Stenzek’s feeling got hurt when DuckStation was still proper open source software and people used the software fully in accordance with its license, i.e. they distributed modifications and not all permitted modifications were the most polished ones, so he felt that they give his name a bad reputation. Again: Stenzek released DuckStation under a license that explicitly allows this.
So he rage quit open source and released new DuckStation versions under a very restrictive “source available to look but not touch” license that’s so insanely restrictive, Linux distributions are not allowed to make their own packages. So they ship the old version that works just fine because PlayStation 1 emulation was figured out very long ago. Stenzek feels that they should not ship the old version (which they are fully entitled to) and instead make a special exception for his software alone to point their users to DuckStation’s website where instead of acquiring the emulator from their package manager (or “app store” in case you’re not familiar with that term), Linux users should take extra steps to manually download and install DuckStation.
And since users may not know about this rift, they may post bug reports and feature ideas to Stenzek, even though these bugs may have been long fixed by non-open source DuckStation.
Basically: Stenzek did not read the license he picked for his software and then got mad when people made use of provisions explicitly allowed by the license.
Ha! Yeah ok. And looks like its maintained.
It is but it’s also just a libretro plugin without any stand-alone GUI. That said, with the great strides projects like ES-DE brought in terms of usability atop of standard components make stand-alone GUIs more and more unnecessary.
Yeah im sure someone will fork and it will be named chickensation or whatever. Then we will move on.
That answer is at best only partially right.
The real answer is that Pixels were, until very recently, Google’s officially supported reference hardware in AOSP while everything else is a community port of some GPL compliance source code dump.
Community ROMs are Pixel first because Pixels just work.
It’ll change now that Google decided to no longer release Pixel adaptions directly as AOSP and the community will have to port that the same way as for any other vendor, especially if a vendor decides to maintain their adaptions in LineageOS.
That’s a problem with most ports. It’s a “new” game on Switch
There is no mandate by Nintendo that ports must cost 70 Euro, the 3rd parties simply follow the example set by Nintendo. They could sell it for 50 but chose not to.
People who have more than one gaming system have little reason to buy Switch versions of their games. Of the announced Switch 2 games, I already have MK World and looking forward to Metroid Prime 4. Everything else I’m looking forward to, I rather play on Steam Deck where deals are much better and I get stuff like cloud saves for free.
There will probably always be a manufacturer that looks at that niche.