Just as long as you don't mention proprietary software in your advertising,
Exhibit 1:
"Companies awarded RYF certification for a given product, must not distribute any product-related materials with endorsements or badges to proprietary software, such as "Works with Windows" or "Made for Mac" badges, because these would give an appearance of legitimacy to those proprietary packages, and may make users think the product requires them.
However, we don't object to clear factual statements informing the user that the product also works with specific proprietary operating systems."
Exhibit 2:
"All the
product software must be free software. The product software includes all software that the seller includes in the product, or provides with the product, or recommends for use in conjunction with the product, or steers users towards installation in the product."
Inclusion of proprietary software in advertising the product is a recommendation for use of said software in conjunction with the product.
show it on your main web page,
Exhibit 2 again:
"All the
product software must be free software. The product software includes all software that the seller includes in the product, or provides with the product, or recommends for use in conjunction with the product,
or steers users towards installation in the product."
As
the web page is an advertising statement,
inclusion of proprietary software would construe a recommendation of use of said proprietary software with the product.
This would include emulated game ROMs. Game ROMs are proprietary software programs, not encumbered media formats.
display it on your packaging,
Exhibit 1 again:
"Companies awarded RYF certification for a given product, must not distribute any product-related materials with
endorsements or
badges to proprietary software, such as "Works with Windows" or "Made for Mac" badges, because these would give an appearance of legitimacy to those proprietary packages, and may make users think the product requires them. However,
we don't object to clear factual statements informing the user that the product also works with specific proprietary operating systems."
Exhibit 2 again:
"All the product software must be free software. The product software includes all software that the seller includes in the product, or provides with the product, or recommends for use in conjunction with the product, or
steers users towards installation in the product."
Exhibit 3:
"The seller must use FSF approved terminology for the FSF's activities and work, in all statements and publications relating to the product. This includes product packaging, and manuals, web pages, marketing materials, and interviews about the product."
Packaging is advertising. Advertising proprietary software in conjunction with the device is a recommendation. The FSF's restrictions on statements of recommendation are clear and include product packaging.
include it in the packaging (even as a drivers disk), and especially not on the device as an alternative.
You must reference the FSF/RYF on all materials,
Exhibit 3 again:
"The seller must
use FSF approved terminology for the FSF's activities and work, in all statements and publications relating to the product. This includes product packaging, and manuals, web pages, marketing materials, and interviews about the product."
So, if that doesn't cover all materials, then what does it leave out?
vet all advertising and packaging through the FSF
Exhibit 3 again:
"The seller must
use FSF approved terminology for the FSF's activities and work, in all statements and publications relating to the product. This includes product packaging, and manuals, web pages, marketing materials, and interviews about the product."
How do you expect to get FSF approval for the terminology used in the above without the FSF vetting the materials?
and agree to never say anything negative about the FSF,
Exhibit 3 again:
"The seller must
use FSF approved terminology for the FSF's activities and work, in all statements and publications relating to the product. This includes product packaging, and manuals, web pages, marketing materials, and interviews about the product."
I'm
quite certain that
if you are required to use, "FSF approved terminology for the FSF's activities and work" that
they would not allow negative statements about their own organization to pass their own vetting process.
Note that this includes interviews and even this web page - which may need to have my comments censored if the project were to join the FSF/RYF program.
join their organization using a closed source contract
Exhibit 4 from right at the top of the page, in bold:
"The following page outlines the general criteria for hardware products that bear the Respects Your Freedom hardware certification mark. However, each certified product carries with it contractual obligations that may differ from those listed on this page."
Note: "contractual obligations"
Note: "
may differ"
There is no public listing of active FSF/RYF contracts.
So -
clearly I'm delusional and making all of this up. It is all right there on the FSF/RYF web site and clearly stated.
Again,
FOSS = good.
FSF/RYF certification = bad.
It requires the project to give up far too many freedoms, particularly speech. Entirely not worth it.