Guidelines for contributing to meta-intel layer - Revision history

Nitinkamble at 16:00, 28 October 2013

2013-10-28T16:00:05Z

← Older revision		Revision as of 16:00, 28 October 2013
Line 26:		Line 26:
	To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.		To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

	===1 Make sure the BSP is functioning well at all the times ===		===1. Make sure the BSP is functioning well at all the times ===
	Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.		Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.

	Check this link showing status of the various meta-intel BSPs kept up to date: [https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]		Check this link showing status of the various meta-intel BSPs kept up to date: [https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]

	===2 Prepare the BSP for release with every meta-intel release ===		===2. Prepare the BSP for release with every meta-intel release ===
	This involves these things:		This involves these things:
	* tag the commit of the release in the meta-intel repository		* tag the commit of the release in the meta-intel repository

Nitinkamble at 15:59, 28 October 2013

2013-10-28T15:59:35Z

← Older revision		Revision as of 15:59, 28 October 2013
Line 1:		Line 1:
	Note: This page is "Work in Progress", it is not finalized yet.		Note: This page is "Work in Progress", it is not finalized yet.


	= meta-intel Layer Information =		= meta-intel Layer Information =
Line 25:		Line 26:
	To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.		To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

	==1 Make sure the BSP is functioning well at all the times ==		===1 Make sure the BSP is functioning well at all the times ===
	Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.		Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.

	Check this link showing status of the various meta-intel BSPs kept up to date: [https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]		Check this link showing status of the various meta-intel BSPs kept up to date: [https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]

	==2 Prepare the BSP for release with every meta-intel release ==		===2 Prepare the BSP for release with every meta-intel release ===
	This involves these things:		This involves these things:
	* tag the commit of the release in the meta-intel repository		* tag the commit of the release in the meta-intel repository

Nitinkamble at 15:58, 28 October 2013

2013-10-28T15:58:30Z

← Older revision		Revision as of 15:58, 28 October 2013
Line 1:		Line 1:
			Note: This page is "Work in Progress", it is not finalized yet.

	= meta-intel Layer Information =		= meta-intel Layer Information =
	git repository location:		git repository location:

Nitinkamble: /* 2 Prepare the BSP for release with every meta-intel release */

2013-10-28T15:54:16Z

2 Prepare the BSP for release with every meta-intel release

← Older revision		Revision as of 15:54, 28 October 2013
Line 30:		Line 30:
	==2 Prepare the BSP for release with every meta-intel release ==		==2 Prepare the BSP for release with every meta-intel release ==
	This involves these things:		This involves these things:
	* ~~git~~ tag the commit of the release		* tag the commit of the release in the meta-intel repository
	* Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration		* Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
	* Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.		* Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.

Nitinkamble at 15:53, 28 October 2013

2013-10-28T15:53:32Z

← Older revision		Revision as of 15:53, 28 October 2013
Line 26:		Line 26:
	Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.		Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.

	Check this link showing status of the various meta-intel BSPs kept up to date:		Check this link showing status of the various meta-intel BSPs kept up to date: [https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]
	[https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]

	==2 Prepare the BSP for release with every meta-intel release ==		==2 Prepare the BSP for release with every meta-intel release ==

Nitinkamble at 15:51, 28 October 2013

2013-10-28T15:51:31Z

Nitinkamble at 15:50, 28 October 2013

2013-10-28T15:50:16Z

@@ Line 19: / Line 19: @@
 * [http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html Yocto Project Linux Kernel Development Manual]
 * To save everybodies time, please make sure you can meet these expectations before submitting a BSP for meta-intel layer
-** [[Expectations for up-streaming a BSP in meta-intel layer]]
 == Review process for sending commits and BSPs to meta-intel layer ==

Nitinkamble at 00:17, 25 October 2013

2013-10-25T00:17:35Z

← Older revision		Revision as of 00:17, 25 October 2013
Line 18:		Line 18:
	* [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html Board Support Packages (BSP) - Developer's Guide]		* [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html Board Support Packages (BSP) - Developer's Guide]
	* [http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html Yocto Project Linux Kernel Development Manual]		* [http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html Yocto Project Linux Kernel Development Manual]
	* Expectations for ~~upstreaming~~ a BSP in meta-intel layer.		* To save everybodies time, please make sure you can meet these expectations before submitting a BSP for meta-intel layer
			** [[Expectations for up-streaming a BSP in meta-intel layer]]

	== Review process for sending commits and BSPs to meta-intel layer ==		== Review process for sending commits and BSPs to meta-intel layer ==

Nitinkamble at 00:15, 25 October 2013

2013-10-25T00:15:24Z

← Older revision		Revision as of 00:15, 25 October 2013
Line 1:		Line 1:
	== meta-intel Layer ~~Details~~ ==		== meta-intel Layer Information ==
			git repository location:
	git repository:
	* git://git.yoctoproject.org/meta-intel		* git://git.yoctoproject.org/meta-intel

Line 7:		Line 6:
	* List email address: meta-intel@yoctoproject.org		* List email address: meta-intel@yoctoproject.org
	* How to subscribe : https://lists.yoctoproject.org/listinfo/meta-intel		* How to subscribe : https://lists.yoctoproject.org/listinfo/meta-intel


	== Guidelines for sending commits to meta-intel ==		== Guidelines for sending commits to meta-intel ==

	Please follow general guidelines for contributing to Yocto Project. Here are some of the links.		Please follow general guidelines for contributing to Yocto Project. Here are some of the links.
	* [[Community Guidelines]]		* [[Community Guidelines]]
Line 16:		Line 13:
	* [[Recipe & Patch Style Guide]]		* [[Recipe & Patch Style Guide]]
	* [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html The Yocto Project Development Manual]		* [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html The Yocto Project Development Manual]


	== Guidelines for submitting BSPs to meta-intel ==		== Guidelines for submitting BSPs to meta-intel ==
Line 22:		Line 18:
	* [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html Board Support Packages (BSP) - Developer's Guide]		* [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html Board Support Packages (BSP) - Developer's Guide]
	* [http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html Yocto Project Linux Kernel Development Manual]		* [http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html Yocto Project Linux Kernel Development Manual]
	* ~~[[Third_Party_BSP_Release_Process \| Third Party~~ BSP ~~Release Guidelines]]~~		* Expectations for upstreaming a BSP in meta-intel layer.


	== Review process for sending commits and BSPs to meta-intel layer ==		== Review process for sending commits and BSPs to meta-intel layer ==
Line 29:		Line 24:
	* The changes should be sent as individual commits. There are scripts available to prepare and send patches for review. Check http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#how-to-submit-a-change		* The changes should be sent as individual commits. There are scripts available to prepare and send patches for review. Check http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#how-to-submit-a-change
	* Do not send tarballs of code for review.		* Do not send tarballs of code for review.

			== Guidelines for releasing BSPs ==
			* [[Third_Party_BSP_Release_Process \| Third Party BSP Release Guidelines]]

Nitinkamble at 00:11, 25 October 2013

2013-10-25T00:11:04Z

← Older revision		Revision as of 00:11, 25 October 2013
Line 27:		Line 27:
	== Review process for sending commits and BSPs to meta-intel layer ==		== Review process for sending commits and BSPs to meta-intel layer ==
	* All the commits for meta-intel layer must go through the meta-intel mailing list.		* All the commits for meta-intel layer must go through the meta-intel mailing list.
	* The changes should be sent as individual commits. There ~~is a specific way~~ to send patches for review. Check http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#how-to-submit-a-change		* The changes should be sent as individual commits. There are scripts available to prepare and send patches for review. Check http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#how-to-submit-a-change
	* Do not send tarballs of code for review.		* Do not send tarballs of code for review.

← Older revision		Revision as of 15:51, 28 October 2013
Line 1:		Line 1:
	== meta-intel Layer Information ==		= meta-intel Layer Information =
	git repository location:		git repository location:
	* git://git.yoctoproject.org/meta-intel		* git://git.yoctoproject.org/meta-intel
Line 7:		Line 7:
	* How to subscribe : https://lists.yoctoproject.org/listinfo/meta-intel		* How to subscribe : https://lists.yoctoproject.org/listinfo/meta-intel

	== Guidelines for sending commits to meta-intel ==		= Guidelines for sending commits to meta-intel =
	Please follow general guidelines for contributing to Yocto Project. Here are some of the links.		Please follow general guidelines for contributing to Yocto Project. Here are some of the links.
	* [[Community Guidelines]]		* [[Community Guidelines]]
Line 14:		Line 14:
	* [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html The Yocto Project Development Manual]		* [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html The Yocto Project Development Manual]

	== Guidelines for submitting BSPs to meta-intel ==		= Guidelines for submitting BSPs to meta-intel =
	1st follow these general BSP developer's guides:		1st follow these general BSP developer's guides:
	* [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html Board Support Packages (BSP) - Developer's Guide]		* [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html Board Support Packages (BSP) - Developer's Guide]
Line 20:		Line 20:
	* To save everybodies time, please make sure you can meet these expectations before submitting a BSP for meta-intel layer		* To save everybodies time, please make sure you can meet these expectations before submitting a BSP for meta-intel layer

	== Expectations for up-streaming a BSP in meta-intel layer ==		= Expectations for up-streaming a BSP in meta-intel layer =
	To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.		To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.

	===1 Make sure the BSP is functioning well at all the times ===		==1 Make sure the BSP is functioning well at all the times ==
	Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.		Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly.

Line 29:		Line 29:
	[https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]		[https://wiki.yoctoproject.org/wiki/Last_Known_Good_Commits_for_meta-intel Last Known Good Commits for meta-intel]

	===2 Prepare the BSP for release with every meta-intel release ===		==2 Prepare the BSP for release with every meta-intel release ==
	This involves these things:		This involves these things:
	* git tag the commit of the release		* git tag the commit of the release
Line 36:		Line 36:
	* Provide the built release tarball of the BSP to the release engineer for releasing to Yocto Project BSP release area		* Provide the built release tarball of the BSP to the release engineer for releasing to Yocto Project BSP release area

	== Review process for sending commits and BSPs to meta-intel layer ==		= Review process for sending commits and BSPs to meta-intel layer =
	* All the commits for meta-intel layer must go through the meta-intel mailing list.		* All the commits for meta-intel layer must go through the meta-intel mailing list.
	* The changes should be sent as individual commits. There are scripts available to prepare and send patches for review. Check http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#how-to-submit-a-change		* The changes should be sent as individual commits. There are scripts available to prepare and send patches for review. Check http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#how-to-submit-a-change
	* Do not send tarballs of code for review.		* Do not send tarballs of code for review.

	== Guidelines for releasing BSPs ==		= Guidelines for releasing BSPs =
	* [[Third_Party_BSP_Release_Process \| Third Party BSP Release Guidelines]]		* [[Third_Party_BSP_Release_Process \| Third Party BSP Release Guidelines]]