User:DarrenHill/scratchpad/TrademarkFAQ - Revision history

DarrenHill at 16:21, 19 April 2020

2020-04-19T16:21:58Z

@@ Line 1: / Line 1: @@
 == References ==
 * Official Trademark Policy - https://kodi.wiki/view/Official:Trademark_Policy
@@ Line 164: / Line 162: @@
 In case of any question not covered by the reference documents above, please contact the Foundation board via our contact email address - contact@kodi.tv .

DarrenHill at 08:28, 25 January 2020

2020-01-25T08:28:32Z

← Older revision		Revision as of 08:28, 25 January 2020
Line 148:		Line 148:
	=== Example 3 ===		=== Example 3 ===

	Acceptable - I want to fork Kodi and add a new feature/fix. This version will then be distributed for testing purposes, and the modification submitted upstream to ~~github.com/xbmc~~ for possible PR inclusion into the core code.		Acceptable - I want to fork Kodi and add a new feature/fix. This version will then be distributed for testing purposes, and the modification submitted upstream to the official repo for possible PR inclusion into the core code.

	Not Acceptable - I want to fork Kodi and add a new feature/fix and then release that fork under the Kodi brand name. This feature/fix will only be included in this version and will not be submitted upstream via PR to the official Kodi repo.		Not Acceptable - I want to fork Kodi and add a new feature/fix and then release that fork under the Kodi brand name. This feature/fix will only be included in this version and will not be submitted upstream via PR to the official Kodi repo.

DarrenHill at 08:27, 25 January 2020

2020-01-25T08:27:37Z

← Older revision		Revision as of 08:27, 25 January 2020
Line 153:		Line 153:

	Explanation - We obviously do not want fragmentation to occur, and it is in the open source culture on which Kodi is founded that changes and fixes should be shared upstream with the official maintainers of the code. We aim to provide a cross-platform player with as much of a common feature set as possible.		Explanation - We obviously do not want fragmentation to occur, and it is in the open source culture on which Kodi is founded that changes and fixes should be shared upstream with the official maintainers of the code. We aim to provide a cross-platform player with as much of a common feature set as possible.


	=== Example 4 ===		=== Example 4 ===

DarrenHill: /* Example 3 */

2020-01-25T08:26:20Z

Example 3

← Older revision		Revision as of 08:26, 25 January 2020
Line 150:		Line 150:
	Acceptable - I want to fork Kodi and add a new feature/fix. This version will then be distributed for testing purposes, and the modification submitted upstream to github.com/xbmc for possible PR inclusion into the core code.		Acceptable - I want to fork Kodi and add a new feature/fix. This version will then be distributed for testing purposes, and the modification submitted upstream to github.com/xbmc for possible PR inclusion into the core code.

	Not Acceptable - I want to fork Kodi and add a new feature/fix and then release that fork under the Kodi brand name. This feature/fix will only be included in this version and will not be submitted upstream to ~~github.com/xbmc~~.		Not Acceptable - I want to fork Kodi and add a new feature/fix and then release that fork under the Kodi brand name. This feature/fix will only be included in this version and will not be submitted upstream via PR to the official Kodi repo.

	Explanation - We obviously do not want fragmentation to occur, and it is in the open source culture on which Kodi is founded that changes and fixes should be shared upstream with the official maintainers of the code. We aim to provide a cross-platform player with as much of a common feature set as possible.		Explanation - We obviously do not want fragmentation to occur, and it is in the open source culture on which Kodi is founded that changes and fixes should be shared upstream with the official maintainers of the code. We aim to provide a cross-platform player with as much of a common feature set as possible.


	=== Example 4 ===		=== Example 4 ===

DarrenHill: /* Guidance Examples */

2020-01-24T15:20:57Z

Guidance Examples

← Older revision		Revision as of 15:20, 24 January 2020
Line 132:		Line 132:
	Not Acceptable - I want to pre-install Kodi onto a batch of generic boxes, set them up including popular addons relevant to the target market and sell them.		Not Acceptable - I want to pre-install Kodi onto a batch of generic boxes, set them up including popular addons relevant to the target market and sell them.

	Explanation - We do not allow unapproved distribution of pre-configured or modified Kodi installations that directly allow access to media sources, even if the modifications are Kodi settings or ~~including~~ addons from the official repo.		Explanation - We do not allow unapproved distribution of pre-configured or modified Kodi installations that directly allow access to media sources, even if the modifications are Kodi settings or involve addons that are sourced from the official repo.

DarrenHill: /* Example 4 */

2020-01-24T15:10:49Z

Example 4

← Older revision		Revision as of 15:10, 24 January 2020
Line 157:		Line 157:
	=== Example 4 ===		=== Example 4 ===

	Not acceptable - I want to fork Kodi and revert or change a fundamental behaviour of the ~~vanilla~~ Kodi version.		Not acceptable - I want to fork Kodi and revert or change a fundamental behaviour of the reference Kodi version.

	Explanation - Again we do not want fragmentation of the code base, nor can we properly support Kodi if there are altered variants available which work in unexpected ways compared to our own version. If we did not make the changes and are unaware of them, we cannot properly support the code in relation to the effects and repercussions of those changes. This can of course also lead to the introduction of issues and resulting negative criticism about which we are entirely innocent.		Explanation - Again we do not want fragmentation of the code base, nor can we properly support Kodi if there are altered variants available which work in unexpected ways compared to our own version. If we did not make the changes and are unaware of them, we cannot properly support the code in relation to the effects and repercussions of those changes. This can of course also lead to the introduction of issues and resulting negative criticism about which we are entirely innocent.

DarrenHill: /* Guidance Examples */

2020-01-24T15:09:20Z

Guidance Examples

← Older revision		Revision as of 15:09, 24 January 2020
Line 128:		Line 128:
	=== Example 1 ===		=== Example 1 ===

	Acceptable - I want to include Kodi without pre-configuration as part of the standard OS image used on all my company laptops. The ~~user~~ will then configure it themselves to their own requirements.		Acceptable - I want to include Kodi without pre-configuration as part of the standard OS image used on all my company laptops. The users will then configure it themselves to their own requirements.

	Not Acceptable - I want to pre-install Kodi onto a batch of generic boxes, set them up including popular addons relevant to the target market and sell them.		Not Acceptable - I want to pre-install Kodi onto a batch of generic boxes, set them up including popular addons relevant to the target market and sell them.

DarrenHill at 15:08, 24 January 2020

2020-01-24T15:08:19Z

← Older revision		Revision as of 15:08, 24 January 2020
Line 128:		Line 128:
	=== Example 1 ===		=== Example 1 ===

	Acceptable - I want to ~~build the official master branch of~~ Kodi ~~and include it~~ without pre-configuration as part of the standard OS image used on all my company laptops. The user will then configure it themselves to their own requirements.		Acceptable - I want to include Kodi without pre-configuration as part of the standard OS image used on all my company laptops. The user will then configure it themselves to their own requirements.

	Not Acceptable - I want to ~~build the official master branch of~~ Kodi ~~and install it~~ onto a batch of generic boxes, set them up including popular addons relevant to the target market and sell them.		Not Acceptable - I want to pre-install Kodi onto a batch of generic boxes, set them up including popular addons relevant to the target market and sell them.

	Explanation - We do not allow unapproved distribution of pre-configured or modified Kodi installations that directly allow access to media sources, even if the modifications are Kodi settings or including addons from the official repo.		Explanation - We do not allow unapproved distribution of pre-configured or modified Kodi installations that directly allow access to media sources, even if the modifications are Kodi settings or including addons from the official repo.
Line 137:		Line 137:
	=== Example 2 ===		=== Example 2 ===

	Acceptable - I want to ~~build the official master branch of~~ Kodi and include an addon to simplify the set-up networking, shares and other OS level functionality.		Acceptable - I want to distribute Kodi and include an addon to simplify the set-up of networking, shares and other OS level functionality.

	Not Acceptable - I want to ~~build and~~ distribute a fork ~~of the official master branch~~ of Kodi with 3rd party sources enabled by default, without changing anything else.		Not Acceptable - I want to distribute a fork of Kodi with 3rd party sources enabled by default, without changing anything else.

	Explanation - Any configuration add-on should only be for the underlying OS features (beneath and outside of Kodi), and not for modifying Kodi settings themselves. The changing of default settings can easily confuse users as to who is delivering addons and services that they are installing and what source they are using to obtain them. As we do not know who is maintaining such external sources and what their content may be, this is explicitly forbidden and against our policy.		Explanation - Any configuration add-on should only be for the underlying OS features (beneath and outside of Kodi), and not for modifying Kodi settings themselves. The changing of default settings can easily confuse users as to who is delivering addons and services that they are installing and what source they are using to obtain them. As we do not know who is maintaining such external sources and what their content may be, this is explicitly forbidden and against our policy.
Line 148:		Line 148:
	=== Example 3 ===		=== Example 3 ===

	Acceptable - I want to fork ~~the official master branch of~~ Kodi and add a new feature/fix. This version will then be distributed for testing purposes, and the modification submitted upstream to github.com/xbmc for possible PR inclusion into the core code.		Acceptable - I want to fork Kodi and add a new feature/fix. This version will then be distributed for testing purposes, and the modification submitted upstream to github.com/xbmc for possible PR inclusion into the core code.

	Not Acceptable - I want to fork ~~the official master branch of~~ Kodi and add a new feature/fix and then release fork under the Kodi brand name. This feature/fix will only be included in this version and will not be submitted upstream to github.com/xbmc.		Not Acceptable - I want to fork Kodi and add a new feature/fix and then release that fork under the Kodi brand name. This feature/fix will only be included in this version and will not be submitted upstream to github.com/xbmc.

	Explanation - We obviously do not want fragmentation to occur, and it is in the open source culture on which Kodi is founded that changes and fixes should be shared upstream with the official maintainers of the code. We aim to provide a cross-platform player with as much of a common feature set as possible.		Explanation - We obviously do not want fragmentation to occur, and it is in the open source culture on which Kodi is founded that changes and fixes should be shared upstream with the official maintainers of the code. We aim to provide a cross-platform player with as much of a common feature set as possible.
Line 157:		Line 157:
	=== Example 4 ===		=== Example 4 ===

	Not acceptable - I want to fork ~~the official master branch of~~ Kodi and revert or change a fundamental behaviour of the vanilla Kodi version.		Not acceptable - I want to fork Kodi and revert or change a fundamental behaviour of the vanilla Kodi version.

	Explanation - Again we do not want fragmentation of the code base, nor can we properly support Kodi if there are altered variants available which work in unexpected ways compared to our own version. If we did not make the changes and are unaware of them, we cannot properly support the code in relation to the effects and repercussions of those changes. This can of course also lead to the introduction of issues and resulting negative criticism about which we are entirely innocent.		Explanation - Again we do not want fragmentation of the code base, nor can we properly support Kodi if there are altered variants available which work in unexpected ways compared to our own version. If we did not make the changes and are unaware of them, we cannot properly support the code in relation to the effects and repercussions of those changes. This can of course also lead to the introduction of issues and resulting negative criticism about which we are entirely innocent.

DarrenHill at 14:58, 24 January 2020

2020-01-24T14:58:01Z

← Older revision		Revision as of 14:58, 24 January 2020
Line 137:		Line 137:
	=== Example 2 ===		=== Example 2 ===

	Acceptable - I want to build the official ~~github.com/xbmc version~~ of Kodi and include an addon to simplify the set-up networking, shares and other OS level functionality.		Acceptable - I want to build the official master branch of Kodi and include an addon to simplify the set-up networking, shares and other OS level functionality.

	Not Acceptable - I want to build and distribute a fork of the official ~~github.com/xbmc version~~ of Kodi with 3rd party sources enabled by default, without changing anything else.		Not Acceptable - I want to build and distribute a fork of the official master branch of Kodi with 3rd party sources enabled by default, without changing anything else.

	Explanation - Any configuration add-on should only be for the underlying OS features (beneath and outside of Kodi), and not for modifying Kodi settings themselves. The changing of default settings can easily confuse users as to who is delivering addons and services that they are installing and what source they are using to obtain them. As we do not know who is maintaining such external sources and what their content may be, this is explicitly forbidden and against our policy.		Explanation - Any configuration add-on should only be for the underlying OS features (beneath and outside of Kodi), and not for modifying Kodi settings themselves. The changing of default settings can easily confuse users as to who is delivering addons and services that they are installing and what source they are using to obtain them. As we do not know who is maintaining such external sources and what their content may be, this is explicitly forbidden and against our policy.
Line 148:		Line 148:
	=== Example 3 ===		=== Example 3 ===

	Acceptable - I want to fork the official ~~github.com/xbmc version~~ of Kodi and add a new feature/fix. This version will then be distributed for testing purposes, and the modification submitted upstream to github.com/xbmc for possible PR inclusion into the core code.		Acceptable - I want to fork the official master branch of Kodi and add a new feature/fix. This version will then be distributed for testing purposes, and the modification submitted upstream to github.com/xbmc for possible PR inclusion into the core code.

	Not Acceptable - I want to fork the official ~~github.com/xbmc version~~ of Kodi and add a new feature/fix and then release fork under the Kodi brand name. This feature/fix will only be included in this version and will not be submitted upstream to github.com/xbmc.		Not Acceptable - I want to fork the official master branch of Kodi and add a new feature/fix and then release fork under the Kodi brand name. This feature/fix will only be included in this version and will not be submitted upstream to github.com/xbmc.

	Explanation - We obviously do not want fragmentation to occur, and it is in the open source culture on which Kodi is founded that changes and fixes should be shared upstream with the official maintainers of the code. We aim to provide a cross-platform player with as much of a common feature set as possible.		Explanation - We obviously do not want fragmentation to occur, and it is in the open source culture on which Kodi is founded that changes and fixes should be shared upstream with the official maintainers of the code. We aim to provide a cross-platform player with as much of a common feature set as possible.
Line 157:		Line 157:
	=== Example 4 ===		=== Example 4 ===

	Not acceptable - I want to fork the official ~~github.com/xbmc version~~ of Kodi and revert or change a fundamental behaviour of the vanilla Kodi version.		Not acceptable - I want to fork the official master branch of Kodi and revert or change a fundamental behaviour of the vanilla Kodi version.

	Explanation - Again we do not want fragmentation of the code base, nor can we properly support Kodi if there are altered variants available which work in unexpected ways compared to our own version. If we did not make the changes and are unaware of them, we cannot properly support the code in relation to the effects and repercussions of those changes. This can of course also lead to the introduction of issues and resulting negative criticism about which we are entirely innocent.		Explanation - Again we do not want fragmentation of the code base, nor can we properly support Kodi if there are altered variants available which work in unexpected ways compared to our own version. If we did not make the changes and are unaware of them, we cannot properly support the code in relation to the effects and repercussions of those changes. This can of course also lead to the introduction of issues and resulting negative criticism about which we are entirely innocent.

DarrenHill at 14:56, 24 January 2020

2020-01-24T14:56:20Z

← Older revision		Revision as of 14:56, 24 January 2020
Line 128:		Line 128:
	=== Example 1 ===		=== Example 1 ===

	Acceptable - I want to build the official ~~github.com/xbmc version~~ of Kodi and include it without pre-~~configured~~ as part of the standard OS image used on all my company laptops. The user will then configure it themselves to their own requirements.		Acceptable - I want to build the official master branch of Kodi and include it without pre-configuration as part of the standard OS image used on all my company laptops. The user will then configure it themselves to their own requirements.

	Not Acceptable - I want to build the official ~~github.com/xbmc version~~ of Kodi and install it onto a batch of generic boxes, set them up including popular addons relevant to the target market and sell them.		Not Acceptable - I want to build the official master branch of Kodi and install it onto a batch of generic boxes, set them up including popular addons relevant to the target market and sell them.

	Explanation - We do not allow unapproved distribution of pre-configured or modified Kodi installations, even if the modifications are Kodi settings or including addons from the official repo.		Explanation - We do not allow unapproved distribution of pre-configured or modified Kodi installations that directly allow access to media sources, even if the modifications are Kodi settings or including addons from the official repo.