Trademark case studies - Revision history

SeanDaly: /* Sugar on a bootable USB stick as part of a Educational Suite */

2010-02-05T15:55:00Z

Sugar on a bootable USB stick as part of a Educational Suite

← Older revision		Revision as of 11:55, 5 February 2010
Line 158:		Line 158:

	examples: openSUSE-Edu-li-f-e or Fedora-12-i686-Live-Edu		examples: openSUSE-Edu-li-f-e or Fedora-12-i686-Live-Edu

			(Sean) that's "Sugar Labs", not "SugarLabs" ;-)
			A perfect candidate for the labeling program.
			If there's an idea to do advertising, let's talk - very few FOSS projects do any advertising, promotion, or end-user marketing.

	==== Should we approve this use of our trademark? ====		==== Should we approve this use of our trademark? ====

	~~Stuff goes here~~.		(Sean) Sure - we wish to encourage precisely this case.

	==== What should the policy be? ====		==== What should the policy be? ====

	~~More stuff goes here~~.		(Sean) The labeling program is designed to promote Sugar in a way easily recognizable by teachers, parents, education buyers, etc.

	=== Case Name Here===		=== Case Name Here===

SeanDaly: /* What should the policy be? */

2010-02-05T15:49:03Z

What should the policy be?

← Older revision		Revision as of 11:49, 5 February 2010
Line 41:		Line 41:

	A copy of the standard contract to be available from our trademark page		A copy of the standard contract to be available from our trademark page

			(Sean) No bot. As stated previously there needs to be contact, review, and approval for a term period.

	=== Sugar on a Stick with extra stuff ===		=== Sugar on a Stick with extra stuff ===

Joe Raftery: /* What should the policy be? */

2010-02-03T00:51:23Z

What should the policy be?

← Older revision		Revision as of 20:51, 2 February 2010
Line 33:		Line 33:
	==== What should the policy be? ====		==== What should the policy be? ====

	Approval by a trademark bot since you are using the software unchanged. Approval subject to you confirming you agree to our standard contract including ~~clasuses~~ related to :		Approval by a trademark bot since you are using the software unchanged. Approval subject to you confirming you agree to our standard contract including clauses related to :
	* expiry date		* expiry date
	* renewal		* renewal
Line 39:		Line 39:
	* revocation if you break the terms		* revocation if you break the terms
	* anything else?		* anything else?

			A copy of the standard contract to be available from our trademark page

	=== Sugar on a Stick with extra stuff ===		=== Sugar on a Stick with extra stuff ===

Joe Raftery: /* Sugar on a Stick */

2010-02-03T00:49:36Z

Sugar on a Stick

← Older revision		Revision as of 20:49, 2 February 2010
Line 33:		Line 33:
	==== What should the policy be? ====		==== What should the policy be? ====

	~~Is approval automatic or do we insist~~ you ~~tell us your real name and your address first~~. ~~Do we demand that~~ you ~~report back how many copies~~ you ~~sold and~~ to ~~who?~~		Approval by a trademark bot since you are using the software unchanged. Approval subject to you confirming you agree to our standard contract including clasuses related to :
			* expiry date
	~~(Sean) approval can't be automatic for several reasons I have outlined previously, but in particular because of periodicity,~~ renewal~~, and~~ revocation if ~~conditions not respected (e.g.~~ the stick turns out to have proprietary software on it instead of the official SL build). Another reason is support—we need to avoid scenario of sales which imply SL community support without our even knowing about it.		* renewal
			* language confirming no one gets a warranty from us
			* revocation if you break the terms
			* anything else?

	=== Sugar on a Stick with extra stuff ===		=== Sugar on a Stick with extra stuff ===

Joe Raftery: /* Used to label a computer with Sugar installed */

2010-02-03T00:45:40Z

Used to label a computer with Sugar installed

← Older revision		Revision as of 20: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 ===

Walter at 16:09, 29 January 2010

2010-01-29T16:09:36Z

Walter at 16:02, 29 January 2010

2010-01-29T16:02:58Z

Show changes

Satellit at 12:46, 29 January 2010

2010-01-29T12:46:20Z

← Older revision		Revision as of 08:46, 29 January 2010
Line 144:		Line 144:
	=== sugar on a bootable USB stick as part of a Educational Suite ===		=== sugar on a bootable USB stick as part of a Educational Suite ===

	~~1.)~~Is inclusion of sugar (sugar-emulator) in a suite of educational software where the icon says "Sugar" on the desktop or in the menus an allowed use?		Is inclusion of sugar (sugar-emulator) in a suite of educational software where the icon says "Sugar" on the desktop or in the menus an allowed use?

	~~2.)~~ If same is accessed via gdm or other desktop switcher with "sugar" label?		If same is accessed via gdm or other desktop switcher with "sugar" label?

	~~3.)~~ How should such a stick be labeled and advertised?		How should such a stick be labeled and advertised?
	ie:		ie:
	-contains or Sugar-Desktop ?		-contains or Sugar-Desktop ?
Line 156:		Line 156:
	-XXXX-Sugar ?		-XXXX-Sugar ?

	~~4.)~~Can they use "SugarLabs" in label?		Can they use "SugarLabs" in label?


Line 163:		Line 163:
	==== Should we approve this use of our trademark? ====		==== Should we approve this use of our trademark? ====

			Stuff goes here.

			==== What should the policy be? ====

			More stuff goes here.

			=== Case Name Here===

			==== Should we approve this use of our trademark? ====
	Stuff goes here.		Stuff goes here.

Satellit: /* Name of case study */ sugar on a bootable USB stick as part of a Educational Suite

2010-01-29T12:38:57Z

Name of case study: sugar on a bootable USB stick as part of a Educational Suite

← Older revision		Revision as of 08:38, 29 January 2010
Line 142:		Line 142:


	=== ~~Name~~ of ~~case study~~ ===		=== sugar on a bootable USB stick as part of a Educational Suite ===

	~~Description~~ of ~~this case~~.		1.)Is inclusion of sugar (sugar-emulator) in a suite of educational software where the icon says "Sugar" on the desktop or in the menus an allowed use?

			2.) If same is accessed via gdm or other desktop switcher with "sugar" label?

			3.) How should such a stick be labeled and advertised?
			ie:
			-contains or Sugar-Desktop ?

			-with Sugar Educational Software ?

			-XXXX-Sugar ?

			4.)Can they use "SugarLabs" in label?


			examples: openSUSE-Edu-li-f-e or Fedora-12-i686-Live-Edu

	==== Should we approve this use of our trademark? ====		==== Should we approve this use of our trademark? ====

SeanDaly at 23:08, 28 January 2010

2010-01-28T23:08:52Z

← Older revision		Revision as of 19:08, 28 January 2010
Line 115:		Line 115:

	More stuff goes here.		More stuff goes here.

			=== $DISTRO ===

			(Sean) You like the Sugar on a Stick concept, but you prefer to use Ubuntu, or Debian, or openSUSE as the underlying distro on your liveUSB implementation instead of the current Fedora. You want to call it Sugar on a Cube and your visuals have sugar cubes with a USB connector poking out.

			==== Should we approve this use of our trademark? ====

			(Sean) No, because that will be too similar to Sugar on a Stick and will cause confusion (the essence of trademark is to avoid confusion). This is precisely why licensing cannot be "automatic". A different name will have to be chosen.

			==== What should the policy be? ====

			(Sean) This is a perfect candidate for the labelling program, once the name problem is sorted out. We wish to encourage this case!


			=== Intel Classmate partner OEM ===

			(Sean) I am one of Intel's 40+ local partners, assembling Classmate v2 machines in a country. The local government is considering purchasing 258,000 machines, but they are balking at the cost of Microsoft Windows licensing and proprietary kids' desktop licensing. I'd like to propose Sugar instead and call my machine "Sugar Babies".

			==== Should we approve this use of our trademark? ====

			(Sean) Considering the size of the potential order and the opportunity for Sugar, we will give careful consideration to your licensing application and may well make an exception to our usual rule of avoiding Sugar in the name of your product.

			==== What should the policy be? ====

			(Sean) A perfect candidate for the labelling program.


	=== Name of case study ===		=== Name of case study ===

← Older revision		Revision as of 12:09, 29 January 2010
Line 49:		Line 49:
	Yes—provided it is clear which is our software and which is by others.		Yes—provided it is clear which is our software and which is by others.

	(Sean) This can't be Sugar on a Stick, but it is a fine candidate for the ~~labelling~~ program.		(Sean) This can't be Sugar on a Stick, but it is a fine candidate for the labeling program.

	==== What should the policy be? ====		==== What should the policy be? ====
	You can call it Sugar if it is Sugar but you you must not put our name on stuff we didn't make.		You can call it Sugar if it is Sugar but you you must not put our name on stuff we didn't make.

	(Sean) The above is ambiguous, unfortunately. However, the ~~labelling~~ program should cover this case.		(Sean) The above is ambiguous, unfortunately. However, the labeling program should cover this case.

	=== Sugar on a Stick with modified stuff ===		=== Sugar on a Stick with modified stuff ===
Line 64:		Line 64:
	No. It isn't our version of the software.		No. It isn't our version of the software.

	(Sean) This can't be Sugar on a Stick, but could be a candidate for the ~~labelling~~ program.		(Sean) This can't be Sugar on a Stick, but could be a candidate for the labeling program.

	==== What should the policy be? ====		==== What should the policy be? ====
Line 99:		Line 99:
	More stuff goes here.		More stuff goes here.

	(Sean) complain to our MEPs that Eastern European beet sugar ~~roundtrips~~ through the Netherlands by truck to win EU subsidies, adding to pollution too.		(Sean) complain to our MEPs that Eastern European beet sugar round trips through the Netherlands by truck to win EU subsidies, adding to pollution too.

	=== Look and Feel ===		=== Look and Feel ===
Line 124:		Line 124:
	==== What should the policy be? ====		==== What should the policy be? ====

	(Sean) This is a perfect candidate for the ~~labelling~~ program, once the name problem is sorted out. We wish to encourage this case!		(Sean) This is a perfect candidate for the labeling program, once the name problem is sorted out. We wish to encourage this case!


	=== Intel Classmate partner OEM ===		=== Intel Classmate partner OEM ===
Line 137:		Line 136:
	==== What should the policy be? ====		==== What should the policy be? ====

	(Sean) A perfect candidate for the ~~labelling~~ program.		(Sean) A perfect candidate for the labeling program.


	=== Sugar on a bootable USB stick as part of a Educational Suite ===		=== Sugar on a bootable USB stick as part of a Educational Suite ===
Line 155:		Line 153:

	Can they use "SugarLabs" in label?		Can they use "SugarLabs" in label?


	examples: openSUSE-Edu-li-f-e or Fedora-12-i686-Live-Edu		examples: openSUSE-Edu-li-f-e or Fedora-12-i686-Live-Edu