bsp
Very Active Member
- Joined
- Dec 2, 2006
- Messages
- 314
This discussion is all theory, anyway. It has not even been decided _if_ a P2 will be developed and what hardware such a hypothetical successor will contain, right ?
You cannot go wrong with chosing hardware that has FOSS drivers for every aspect of it. The merits of that should be clear to everyone.
However, if e.g. a FOSS GPU driver of such a hardware would be inferior to the closed source version, I for one would use the CS driver until the open one has matured.
If a P2 was designed with such openess in mind, getting a RYF certificate (or not) can be discussed after development is done.
The FSF could then be approached and details could be discussed. If there actually are any unbearable restrictions a RYF certificate would impose on the project, the FSF could either ease up and happily add the P2 to its - currently not very long - list of RYF platforms, or not do that and we would invent our own certificate (what about ROFL - Respects Our Freedom and Liberty).
You cannot go wrong with chosing hardware that has FOSS drivers for every aspect of it. The merits of that should be clear to everyone.
However, if e.g. a FOSS GPU driver of such a hardware would be inferior to the closed source version, I for one would use the CS driver until the open one has matured.
If a P2 was designed with such openess in mind, getting a RYF certificate (or not) can be discussed after development is done.
The FSF could then be approached and details could be discussed. If there actually are any unbearable restrictions a RYF certificate would impose on the project, the FSF could either ease up and happily add the P2 to its - currently not very long - list of RYF platforms, or not do that and we would invent our own certificate (what about ROFL - Respects Our Freedom and Liberty).
Last edited by a moderator: