From Sugar Labs
Revision as of 11:15, 30 December 2009 by Cjb (talk | contribs) (small rewording)
Jump to navigation Jump to search

Sugar Labs association/organization conflated with Sugar software

2a & b, and elsewhere suggest that the full name of our product is 'Sugar Labs' rather than Sugar or some form of Sugar. Yes, 5e suggests that Sugar is short for Sugar Labs. This would be a new practice. Why conflate the terms?
Why not register Sugar as a mark for our software, and Sugar Labs for our association?
--FGrose 23:18, 7 July 2009 (UTC)

In paragraph 1, "(our trademark registration application for the logo is still pending)", is a separate statement, right? Sugar Labs is already registered, but the logos (colors and typeface) are pending registration, no? If so, this would be more clear as a separate sentence in the introduction, as it is currently too closely associated with the Sugar Labs name.
--FGrose 23:45, 7 July 2009 (UTC)
AFAIK, the logo is not registered. It seemed that the name "Sugar Labs" was enough. --Walter 00:00, 8 July 2009 (UTC)

Section 5a

It has been suggested that we certify distributions as "Sugar on a Stick". "Otherwise nothing stops anyone from creating a lousy version which hardly works and calls it Sugar on a Stick Peanut Butter release, etc."
Comments? --Walter 22:23, 7 July 2009 (UTC)
We have our hands full verifying and testing our own release. Our best defense is focusing on making the best release and so being able to market it as such. --FGrose 23:28, 7 July 2009 (UTC)
I agree. It adds yet another thing to worry about that can better be handled downstream. --Walter 23:34, 7 July 2009 (UTC)
This line of judgement needs revisiting. "our own release" means Strawberry? If SL lets anyone use "Sugar on a Stick", then it's probably giving up the rights to the trademark "Sugar on a Stick", right?

Sugar Labs/Legal/Logo and trademark policy

This older page needs updating. --FGrose 18:31, 4 September 2009 (UTC)

Sugar on a Stick Guidelines

I am herewith proposing the following changes to the section 5a. This has been derived from Fedora's trademark guidelines and might need to be adjusted to cover more cases, as listed in those guidelines. By referring to Sugar on a Stick, the following draft means the project located and hosted here.

  • You may use the term Sugar on a Stick whenever referring to the official Sugar on a Stick product and its releases, as well as when distributing unmodified copies of it.
    • However, this usage must not imply any endorsement by Sugar Labs or the Sugar on a Stick project, unless this is case and an appropriate agreement has been reached.
  • You may modify Sugar on a Stick and create remixes of it.
    • However, when distributing or selling this modified version, you must not call it Sugar on a Stick.
    • When not exposing the resulting product to the public, you may still call it Sugar on a Stick, though. A deployment might adjust Sugar on a Stick for its needs and still say it deployed Sugar on a Stick, as long as the modified version is not distributed publicly.

substantially unmodified

We discuss examples of "substantially unmodified" in Section 2 of the policy: "including but not limited to: the enabling or disabling of certain features by default, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches." But it would be instructive to give some examples of changes that would not qualify as substantially unmodified: including but not limited to adding of non-free drivers. (We need to build consensus around this issue.) --Walter 20:44, 18 December 2009 (UTC)

How to make modifications

There is a discussion here about making a systemic process for most trivial modifications. --Walter 20:44, 18 December 2009 (UTC)

Sugar Trademark Policy

DRAFT: 30 December 2009

The purpose of this policy is to protect the public, by ensuring that the identity, provenance, and open-source nature of Sugar Labs® remain clear. Throughout this document, the "Marks" refers to the Sugar Labs name and logo, individually or together. However, note that Section 5 provides guidelines for other marks that Sugar Labs uses. Sugar Labs is a member project of the Software Freedom Conservancy, which is the holder of the registered mark.

Guidelines for Using the Marks


The first or most prominent mention of the name should be immediately followed by a symbol for registered trademark: "®" or "(r)". For example: "Sugar Labs®" (our trademark registration application for the logo is still pending).

This requirement is waived in all contexts where such marks are not normally included: email, on-line discussion, non-graphical advertisements (when permitted), and academic papers. We encourage the use of the symbol whenever possible, but recognize that many non-commercial and informal uses will omit it.


You may use the Sugar Labs Marks without prior written permission for the following purposes (subject to the other sections):

To refer to the Sugar Labs software in substantially unmodified form "substantially unmodified" means built from the source code provided by the Sugar Labs project, possibly with minor modifications including but not limited to: the enabling or disabling of certain features by default, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches). All such minor modifications must be released under an approved license. (That should link to a page on our licensing philosophy that includes the license criteria:, Preapproved licenses:, and "for further questions, ask SLOBs to ask the SFC." from

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.
To identify Sugar Labs software as a distinct component of a software offering. For example, "MyDistro, sweetened by Sugar" or other "<product>, <joined with> Sugar" language would be a use that does not require explicit written permission.
To refer to the Sugar Labs project itself, its products, or its protocols.


You may use the Sugar Labs Marks as part of the name of a product designed to work with Sugar Labs, so long as the name as a whole (via its other components) clearly and unambiguously distinguishes the product from Sugar Labs software itself, and the general presentation of the product does not imply any official association or identity with Sugar Labs. Because it would be awkward to attach a trademark symbol to a portion of a larger name whose other portions might themselves be trademarked, the requirement to display the symbol is waived for this circumstance.


You may not use the Marks in the following ways:

In any way likely to cause confusion as to the identity of the Sugar Labs project, the provenance of its software, or the software's license (the Sugar Labs Marks should be secondary in advertising materials);
In any way that indicates a greater degree of association between you and the Sugar Labs project than actually exists;
In any way that implies a designated successor to Sugar Labs (e.g., "Sugar Labs++" is not permitted).
In a way that indicates that Sugar Labs favors one distribution, platform, product, etc. over another.(


Sugar Labs also uses the following other marks, which we may choose to register:

Sugar on a Stick:
You may produce and distribute Sugar Labs software on a USB key. and refer to it as "Sugar on a Stick". However, you are required encouraged to add a qualifying label to distinguish it from "Sugar on a Stick" other distributions. For example, the – that mark is currently associated with the Fedora GNU/Linux distribution. Different versions of Sugar on a Stick are indicated by a qualifying phrase, e.g., the "Sugar on a Stick v1 Strawberry" Release is based on Fedora 11. question: do we want to explicitly limit SoaS to a particular project/effort/group working on the Fedora variant, or does this clause broadly include any Fedora-based spins anyone might choose to start? Mchua 15:06, 30 December 2009 (UTC)
Sugar Labs Partner:
"Sugar Labs Partner" should only be used to refer to a person or entity that is officially affiliated with the Sugar Labs project. Sugar Labs is happy to designate partners, so please contact us if you are interested in becoming a Sugar Labs Partner.
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 us if you are interested in receiving a certification.
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.
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 us if you are uncertain.

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 us if you are interested in establishing a local Sugar Labs.


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 us if you would like to sell any other merchandise containing a Sugar Labs mark. This section is subject to the provisions contained in Sections 2 and 3 of this policy.


The Software Freedom Conservancy reserves the sole right to:

Determine compliance with this policy;
Modify this policy in ways consistent with its mission of protecting the public;
Grant exceptions to this policy, of any kind and for any reason whatsoever, other clauses notwithstanding.

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 [].