For everyone who isn't in the know - this "Changing the repo is a software change" should be written as RESTRICTING the repo to ban certain types of software in the name of 'Freedom'.
For the umpteenth time, this is not true.
There is no restriction on what can be hosted in a repository whatsoever to be eligible for the RYF certification.
The
restrictions in software are in what OPT can ship on the device and what they can advertise as core features of the device. Applying for the RYF certification will not require any changes to the repo in any way. No bans, no shaming, no restrictions. It is a HARDWARE certification, not a software certification. The software requirements are only extended to what is required to make the hardware function. The Pandora is a GPU driver away from being able to apply for certification right now. If we were somehow able to ditch the binary blob that runs our graphics we would have a RYF device, complete with repo exactly as it is.
Anytime someone claims to be promoting freedom by stating their required 'restrictions' makes my skin crawl.
The absolute freedom to both parties, seller and purchaser, is diamentrally opposite. When we aquire hardware we are at the limits of the vendor, when we extend that freedom we get (hopefully) (or restrict it, alter through extending it), to the user, we are providing freedom, that the user couldnt have without us giving up the freedom to restrict that user through nonfree drivers. If the user so wishes, one can make or install a proprietary driver at will. Proprietary solutions, by extention, provide less freedom since they dont respect the freedoms of free software. And that is still from the users point of view. See posts by
WizardStan 1 and
2 plus
wb 1
By your logic the most free is when the vendor pulls out all the stops to really divert from free as in freedom software.
I dont think firmware is part of the spec (from my understanding) unless it has the ability to spy on the user. Will have to check that.
To be compliant then, the www.pandora.org web site would have to remove all of the emulated games shown in the animation/advertisment (not free even if the emulators are). Any way you slice the 'restrictions on advertising' it is a restriction on freedom of speech.
Why is running a romdump with free software emulators not permitted in whatever context you are referring to , i fail to see exactly how.
Even if you make that point, (
and you dont) it isnt detrimental to freedom of speech, it would be in tune with whatever the certification is. Because that isnt mandatory, nor permanent. And that is down to, choice.
Those games being shown in the emulators, on the device's home page, are non-free software. Emulation of old game consoles is a primary purpose of this device. Although RYF would allow you to show the emulator's welcome/pick screens, actually showing games in action on the device would be against their rules.
What old game consoles dont have FOSS games? I cant think of any. Its demos and those games that really exhibit the emulator performance for the older stuff. Nothing you say in terms of RYF cert. is really function specific, just as much as the pandora isnt a DS emulator device, (for obvious nintendo reasons) There are free DS emus btw, segwaying us into where your 8:47PM post is continues:
To be compliant then, the Pandora would need to ship without a link/repo that includes non-free software for which there is no 'free' version. There goes DS emulation.
Again, wrong cert. You could use that to document how it works. I suppose it has other uses too, with homebrew DS programs/games, though they arent recognizable. It could possibly make sense to document wine with proprietary apps too since the foss stuff is mostly ported, and its easier to tell you arent cheating. Lets for the case of the arguement say you want to show reactOS in a world where no FOSS windows stuff exists, then you have to show non-free apps.
'No bans' - how do you figure if you ban advertising non-free capabilities?
'No shaming' - Bull. That is the entire basis of operation for the FSF/RYF system - shame companies into doing something outside of their best interest.
Hardware that
Respects Your Freedom is actually a system that promotes hardware that
respects your freedom, the two are not the same.
It is a current trend for political and action organizations to name themselves using terminology that is the exact opposite of what they're really about. Calling something, 'Respects Your Freedom,' then requiring limiting free speech and choice - what a sham.
This is irony at its finest.
Advertising non-free software as a primary device purpose is verboten.
Could you clarify, or at least link to what you are referring to?
The only modern SoC that I'm aware of that has a decent GPU built in that will likely have real FOSS driver support is the Z3770. What did you have in mind? It would be rather ironic if the most 'Free' SoC was from Intel, wouldn't it?
What is ironic about it, intel has to my knowledge free drivers across the board, except for the powerVR stuff.
For everyone who isn't in the know - this "Changing the repo is a software change" should be written as RESTRICTING the repo to ban certain types of software in the name of 'Freedom'. Real freedom is respecting other's rights to do/use things that you don't approve of.
The problem isnt what I write, its that
you dont read it,
God Ginrai:
Changing the repo is a software change. Respecting peoples freedom and having a unison way of separating it, providing source packages make sense. It is benefit for the purpose of benefit. Explain to me how the current one is better before you side with not changing it.
neither the post i was answering, (
nor the context in reference to an understanding of how it is
two different certifications.) You seem to not even be able to grasp that concept.
Free drivers is also a software change, to the point of ability. And thats something thats important to have in the back of ones head when selecting drivers. If you do it wrong, you are shooting yourself in the foot down the road. It makes less sense to go with proprietary stuff, since it gives more freedom to have choices.
So we get 'more choice' by submitting to a quasi-religious mandate that restricts potential options to a small set of options that are acceptable to a 3rd party's dogma. Ummm. No.
You failed to notice i was talking about driver availability (either through source, writing with documentation, or reverse engineering fully.) In any event, you were also wrong. Notice i had reasoning, you didnt.
If you quote something, or make a reference to something, make sure to have read and understood it.
You are shunning the thread topic in disregarding the distinction between two certifications, and continue to spread FUD.