Changes

Jump to navigation Jump to search
234 bytes added ,  12:15, 7 May 2010
m
Line 45: Line 45:  
                              
 
                              
 
DRAFT: 7 May 2010
 
DRAFT: 7 May 2010
 +
 +
We need to write this agreement due to legal reasons. Please don't feel like this policy is intended to keep you out! Our goal is to make Sugar a recognized name in learning, making clear trademark usage arrangements with partners and other FOSS projects. Please come talk with us if you have any questions whatsoever.
 +
 +
----------- agreement starts here -------------
    
The purpose of this policy is to ensure that the identity, provenance, and free and open-source nature of Sugar Labs<sup>®</sup> remain clear '''to the public. This is in keeping with''' our objective to spread the use of the Sugar Learning Platform while protecting our trademarks. It is our intention to be liberal and responsive in the enforcement of our trademarks: '''we want our Marks to be widely used to represent our learning mission to the public, but we also need to ensure clarity regarding the relationship between Sugar Labs and the individual or organization using our Marks in order to both protect Sugar Labs and the public.''' As part of our marketing effort to make Sugar better known, we have developed a label program with the objective of simplifying and streamlining permission to use Sugar Labs marks by projects and businesses. '''We encourage you to contact us at trademark at sugarlabs.org if you have any questions about this policy or the label program.''' Throughout this document, the word "Marks" refers to the Sugar Labs name and logo, individually or together. Note that Section 5 provides guidelines for other marks used by Sugar Labs. Sugar Labs is a member project of the Software Freedom Conservancy, which is the holder of the [http://tess2.uspto.gov/bin/showfield?f=doc&state=4006:qq173k.3.1 registered mark].
 
The purpose of this policy is to ensure that the identity, provenance, and free and open-source nature of Sugar Labs<sup>®</sup> remain clear '''to the public. This is in keeping with''' our objective to spread the use of the Sugar Learning Platform while protecting our trademarks. It is our intention to be liberal and responsive in the enforcement of our trademarks: '''we want our Marks to be widely used to represent our learning mission to the public, but we also need to ensure clarity regarding the relationship between Sugar Labs and the individual or organization using our Marks in order to both protect Sugar Labs and the public.''' As part of our marketing effort to make Sugar better known, we have developed a label program with the objective of simplifying and streamlining permission to use Sugar Labs marks by projects and businesses. '''We encourage you to contact us at trademark at sugarlabs.org if you have any questions about this policy or the label program.''' Throughout this document, the word "Marks" refers to the Sugar Labs name and logo, individually or together. Note that Section 5 provides guidelines for other marks used by Sugar Labs. Sugar Labs is a member project of the Software Freedom Conservancy, which is the holder of the [http://tess2.uspto.gov/bin/showfield?f=doc&state=4006:qq173k.3.1 registered mark].
Line 70: Line 74:  
:You may use the Sugar Labs Marks with prior written permission for the following purposes (subject to the other sections):
 
:You may use the Sugar Labs Marks with prior written permission for the following purposes (subject to the other sections):
   −
:If you are producing a new product which is based on Sugar Labs software but which has more substantial changes than those described in the previous paragraph, you may refer to your product as "derived from", "based on", or "a derivative of" a Sugar Labs mark.
+
:If you are producing a new product which is based on Sugar Labs software but which has more substantial changes than those described in the previous paragraph, we encourage you to participate in our label program, designed to help educators recognize your project as a good choice for learning.
    
:Please refer to our [[Sugar_Labs/Governance/Transactions#License_request|License Request]] procedure for details regarding obtaining a license to use the Sugar Marks.
 
:Please refer to our [[Sugar_Labs/Governance/Transactions#License_request|License Request]] procedure for details regarding obtaining a license to use the Sugar Marks.
Line 118: Line 122:  
:c.
 
:c.
   −
:Sugar Ready:
  −
::"Sugar Ready" may be used to refer to software certified by Sugar Labs to run on top of an official version of Sugar Labs, please [[#Contact information|contact us]] if you are interested in receiving a certification.
  −
 
  −
:d.
  −
 
   
:Sugar Learning Platform
 
:Sugar Learning Platform
 
::"Sugar Learning Platform" should be used to refer to the software created by Sugar Labs and should be used under the same guidelines as per Sections 2 and 3 of this policy.
 
::"Sugar Learning Platform" should be used to refer to the software created by Sugar Labs and should be used under the same guidelines as per Sections 2 and 3 of this policy.
 
    
 
    
:e.  
+
:d.  
 
+
     
 
:Sugar
 
:Sugar
 
::We sometimes use this term as a shortened way to refer to software and other things created by Sugar Labs. Please use this policy as guidance for use of these terms as well and [[#Contact information|contact us]] if you are uncertain.  
 
::We sometimes use this term as a shortened way to refer to software and other things created by Sugar Labs. Please use this policy as guidance for use of these terms as well and [[#Contact information|contact us]] if you are uncertain.  
   −
:f.
+
:e.
 
          
 
          
:local Sugar Lab:
+
:Local Sugar Lab:
 
::We have affiliated local and regional Sugar Labs that are referred to Sugar Labs <Region Name>, e.g., Sugar Labs Colombia. Sugar Labs is happy to designate local lab partners, so please [[#Contact information|contact us]] if you are interested in establishing a local Sugar Lab.
 
::We have affiliated local and regional Sugar Labs that are referred to Sugar Labs <Region Name>, e.g., Sugar Labs Colombia. Sugar Labs is happy to designate local lab partners, so please [[#Contact information|contact us]] if you are interested in establishing a local Sugar Lab.
    
6.
 
6.
   −
You may create and sell merchandise using the Sugar Labs name and logo without additional permission provided that you use only unmodified graphics from the logo page on the Sugar Labs website. Please [[#Contact information|contact us]] if you would like to sell any other merchandise containing Sugar Labs Marks. This section is subject to the provisions contained in Sections 2 and 3 of this policy.
+
You may create and sell merchandise using the Sugar Labs name and logo without additional permission provided that you use only unmodified graphics from the [[Marketing_Team/Logo|logo page on the Sugar Labs website.]] Please [[#Contact information|contact us]] if you would like to sell any other merchandise containing Sugar Labs Marks. This section is subject to the provisions contained in Sections 2 and 3 of this policy.
 
    
 
    
 
7.
 
7.
Line 158: Line 157:  
===Contact information===
 
===Contact information===
   −
If you have questions about using the Marks, or if you think you should be able to use the Marks for any purpose not allowed by this policy and would like permission for that use, please contact Sugar Labs by emailing [trademark@sugarlabs.org] '''or by writing to [[Sugar_Labs/Contacts#Mail|Sugar Labs c/o Software Freedom Conservancy, 1995 BROADWAY FL 17, NEW YORK NY 10023-5882 USA]].'''
+
If you have questions about using the Marks, or if you think you should be able to use the Marks for any purpose not allowed by this policy and would like permission for that use, or for more information concerning our label program, please contact Sugar Labs by emailing [trademark@sugarlabs.org] '''or by writing to [[Sugar_Labs/Contacts#Mail|Sugar Labs c/o Software Freedom Conservancy, 1995 BROADWAY FL 17, NEW YORK NY 10023-5882 USA]].'''
    
===Usage examples===
 
===Usage examples===
779

edits

Navigation menu