Changes

469 bytes removed ,  19:45, 2 February 2010
Line 17: Line 17:     
==== Should we approve this use of our trademark? ====
 
==== Should we approve this use of our trademark? ====
Do it like Microsoft—you can only put the '''CONTAINS SUGAR''' decal on the front if the computer meets our minimum specification. If it doesn't meet that specification then you can put '''contains Sugar operating system (R)''' in small print in the specification box on the back.
+
You should apply for a license for our label program. We will need to verify that there actually is Sugar running. License should be for one year with updated rider from applicant for renewal. We shouldn't charge for licensing, including by commercial entities.
 
  −
(Sean) No, neither of these—the company should apply for a license for our label program. We will need to verify that there actually is Sugar running. License should be for one year with updated rider from applicant for renewal. I don't think however we should charge for licensing, including by commercial entities.
      
==== How should the policy work to achieve this ====
 
==== How should the policy work to achieve this ====
   −
All uses of the decal need a contract.  For this case we can use a standard contract available for download as a pdf from our trademark info page.
+
All uses of the decal need a contract.  For an OEM like this case we would want to agree what you are including with our software and how you are using our trademark before we give permission.
 
  −
(Sean) I agree standard contract should be published and available. However, I am not sure we will want to offer identical conditions to all applicants, in particular OEMs.
      
=== Sugar on a Stick ===
 
=== Sugar on a Stick ===
28

edits