OpenEmbeddedJanitors - Revision history

Paulbarker at 13:01, 19 September 2013

2013-09-19T13:01:30Z

← Older revision		Revision as of 13:01, 19 September 2013
Line 1:		Line 1:
	~~Here we have the current "janitor" tasks in OE. These are relatively simple, mechanical tasks which can be easily accomplished by someone who isn't an expert in~~ the ~~system~~, ~~but which can help acclimate them to contributing to~~ the ~~project. Current tasks~~:		Janitorial work for OpenEmbedded is now co-ordinated via the Yocto Project wiki, on the [https://wiki.yoctoproject.org/wiki/Janitors Janitors] page.

	* Make recipes more conform a standard layout (see also contrib/~~oe-stylize~~.~~py, which can be of help here)~~. ~~be careful though if require lines are moved. It is a good plan to test building a recipe after oe-stylizing it and use buildhistory to test for regressions.~~
	* Rework files dir. if there is only one recipe in the dir (like x_0.bb and x_1.bb) the dir should be called x, if the patches are only for x_1 then the dir should be called x-1. Also check if the patches in it are still applied or only deadwood.

PaulEggleton: Remove obsolete item

2013-07-30T16:11:12Z

Remove obsolete item

← Older revision		Revision as of 16:11, 30 July 2013
Line 1:		Line 1:
	Here we have the current "janitor" tasks in OE. These are relatively simple, mechanical tasks which can be easily accomplished by someone who isn't an expert in the system, but which can help acclimate them to contributing to the project. Current tasks:		Here we have the current "janitor" tasks in OE. These are relatively simple, mechanical tasks which can be easily accomplished by someone who isn't an expert in the system, but which can help acclimate them to contributing to the project. Current tasks:

	* Conversion of FILESDIR to FILESPATHPKG =. or =. when still needed or simple removal in most cases.
	* Make recipes more conform a standard layout (see also contrib/oe-stylize.py, which can be of help here). be careful though if require lines are moved. It is a good plan to test building a recipe after oe-stylizing it and use buildhistory to test for regressions.		* Make recipes more conform a standard layout (see also contrib/oe-stylize.py, which can be of help here). be careful though if require lines are moved. It is a good plan to test building a recipe after oe-stylizing it and use buildhistory to test for regressions.
	* Rework files dir. if there is only one recipe in the dir (like x_0.bb and x_1.bb) the dir should be called x, if the patches are only for x_1 then the dir should be called x-1. Also check if the patches in it are still applied or only deadwood.		* Rework files dir. if there is only one recipe in the dir (like x_0.bb and x_1.bb) the dir should be called x, if the patches are only for x_1 then the dir should be called x-1. Also check if the patches in it are still applied or only deadwood.

Rpurdie at 15:12, 7 November 2012

2012-11-07T15:12:52Z

← Older revision		Revision as of 15:12, 7 November 2012
Line 1:		Line 1:
	~~{{Outdated}}~~		Here we have the current "janitor" tasks in OE. These are relatively simple, mechanical tasks which can be easily accomplished by someone who isn't an expert in the system, but which can help acclimate them to contributing to the project. Current tasks:

	Here we have the current "janitor" tasks in the OE metadata. These are relatively simple, mechanical tasks which can be easily accomplished by someone who isn't an expert in the system, but which can help acclimate them to contributing to the project. Current tasks:

	* Conversion from [[legacy staging]] to new style staging
	* Conversion to use BBCLASSEXTEND
	* Conversion of FILESDIR to FILESPATHPKG =. or =. when still needed or simple removal in most cases.		* Conversion of FILESDIR to FILESPATHPKG =. or =. when still needed or simple removal in most cases.
	* ~~make~~ recipes more conform a standard layout (see also contrib/oe-stylize.py, which can be of help here). be careful though if require lines are moved. It is a good plan to test building a recipe after oe-stylizing it.		* Make recipes more conform a standard layout (see also contrib/oe-stylize.py, which can be of help here). be careful though if require lines are moved. It is a good plan to test building a recipe after oe-stylizing it and use buildhistory to test for regressions.
	* ~~rework~~ files dir. if there is only one recipe in the dir (like x_0.bb and x_1.bb) the dir should be called x, if the patches are only for x_1 then the dir should be called x-1. Also check if the patches in it are still applied or only deadwood.		* Rework files dir. if there is only one recipe in the dir (like x_0.bb and x_1.bb) the dir should be called x, if the patches are only for x_1 then the dir should be called x-1. Also check if the patches in it are still applied or only deadwood.

PaulEggleton at 16:59, 3 November 2012

2012-11-03T16:59:33Z

← Older revision		Revision as of 16:59, 3 November 2012
Line 1:		Line 1:
			{{Outdated}}

	Here we have the current "janitor" tasks in the OE metadata. These are relatively simple, mechanical tasks which can be easily accomplished by someone who isn't an expert in the system, but which can help acclimate them to contributing to the project. Current tasks:		Here we have the current "janitor" tasks in the OE metadata. These are relatively simple, mechanical tasks which can be easily accomplished by someone who isn't an expert in the system, but which can help acclimate them to contributing to the project. Current tasks:

24.132.200.125 at 07:57, 15 August 2010

2010-08-15T07:57:51Z

← Older revision		Revision as of 07:57, 15 August 2010
Line 5:		Line 5:
	* Conversion of FILESDIR to FILESPATHPKG =. or =. when still needed or simple removal in most cases.		* Conversion of FILESDIR to FILESPATHPKG =. or =. when still needed or simple removal in most cases.
	* make recipes more conform a standard layout (see also contrib/oe-stylize.py, which can be of help here). be careful though if require lines are moved. It is a good plan to test building a recipe after oe-stylizing it.		* make recipes more conform a standard layout (see also contrib/oe-stylize.py, which can be of help here). be careful though if require lines are moved. It is a good plan to test building a recipe after oe-stylizing it.
	* rework files dir. if there is only one recipe in the dir (like x_0.bb and x_1.bb) the dir should be called x, if the patches are only for x_1 then the dir should be called x-1		* rework files dir. if there is only one recipe in the dir (like x_0.bb and x_1.bb) the dir should be called x, if the patches are only for x_1 then the dir should be called x-1. Also check if the patches in it are still applied or only deadwood.

24.132.200.125 at 07:55, 15 August 2010

2010-08-15T07:55:22Z

← Older revision		Revision as of 07:55, 15 August 2010
Line 5:		Line 5:
	* Conversion of FILESDIR to FILESPATHPKG =. or =. when still needed or simple removal in most cases.		* Conversion of FILESDIR to FILESPATHPKG =. or =. when still needed or simple removal in most cases.
	* make recipes more conform a standard layout (see also contrib/oe-stylize.py, which can be of help here). be careful though if require lines are moved. It is a good plan to test building a recipe after oe-stylizing it.		* make recipes more conform a standard layout (see also contrib/oe-stylize.py, which can be of help here). be careful though if require lines are moved. It is a good plan to test building a recipe after oe-stylizing it.
			* rework files dir. if there is only one recipe in the dir (like x_0.bb and x_1.bb) the dir should be called x, if the patches are only for x_1 then the dir should be called x-1

212.178.107.193 at 06:46, 13 August 2010

2010-08-13T06:46:06Z

← Older revision		Revision as of 06:46, 13 August 2010
Line 4:		Line 4:
	* Conversion to use BBCLASSEXTEND		* Conversion to use BBCLASSEXTEND
	* Conversion of FILESDIR to FILESPATHPKG =. or =. when still needed or simple removal in most cases.		* Conversion of FILESDIR to FILESPATHPKG =. or =. when still needed or simple removal in most cases.
			* make recipes more conform a standard layout (see also contrib/oe-stylize.py, which can be of help here). be careful though if require lines are moved. It is a good plan to test building a recipe after oe-stylizing it.

Trini at 20:28, 12 August 2010

2010-08-12T20:28:17Z

← Older revision		Revision as of 20:28, 12 August 2010
Line 3:		Line 3:
	* Conversion from [[legacy staging]] to new style staging		* Conversion from [[legacy staging]] to new style staging
	* Conversion to use BBCLASSEXTEND		* Conversion to use BBCLASSEXTEND
			* Conversion of FILESDIR to FILESPATHPKG =. or =. when still needed or simple removal in most cases.

Trini at 19:50, 26 July 2010

2010-07-26T19:50:20Z

← Older revision		Revision as of 19:50, 26 July 2010
Line 1:		Line 1:
	Here we have the current "janitor" tasks in the OE metadata. These are relatively simple, mechanical tasks which can be easily accomplished by someone who isn't an expert in the system, but which can help acclimate them to contributing to the project. Current tasks:		Here we have the current "janitor" tasks in the OE metadata. These are relatively simple, mechanical tasks which can be easily accomplished by someone who isn't an expert in the system, but which can help acclimate them to contributing to the project. Current tasks:

	* Conversion to new style staging		* Conversion from [[legacy staging]] to new style staging
	* Conversion to use BBCLASSEXTEND		* Conversion to use BBCLASSEXTEND

24.251.170.95: New page: Here we have the current "janitor" tasks in the OE metadata. These are relatively simple, mechanical tasks which can be easily accomplished by someone who isn't an expert in the system, b...

2010-07-20T21:53:14Z

New page: Here we have the current "janitor" tasks in the OE metadata. These are relatively simple, mechanical tasks which can be easily accomplished by someone who isn't an expert in the system, b...

New page

Here we have the current "janitor" tasks in the OE metadata. These are relatively simple, mechanical tasks which can be easily accomplished by someone who isn't an expert in the system, but which can help acclimate them to contributing to the project. Current tasks:

* Conversion to new style staging
* Conversion to use BBCLASSEXTEND