Janitors - Revision history

Paul Barker: /* Style and Formatting */

2013-09-19T13:11:33Z

Style and Formatting

← Older revision		Revision as of 13:11, 19 September 2013
Line 57:		Line 57:
	** Estimate: < 1 week		** Estimate: < 1 week
	** Submitter: paulbarker		** Submitter: paulbarker
	** Possibly look at reviving the old stylisation script ([[http://git.openembedded.org/openembedded/tree/contrib/oe-stylize.py]]). It would need bringing up-to-date with the current styleguide and then submitting to oe-core		** Possibly look at reviving the old stylisation script (http://git.openembedded.org/openembedded/tree/contrib/oe-stylize.py). It would need bringing up-to-date with the current styleguide and then submitting to oe-core

	* Convert short DESCRIPTION values (< 80 characters) to set SUMMARY instead		* Convert short DESCRIPTION values (< 80 characters) to set SUMMARY instead

Paul Barker at 13:10, 19 September 2013

2013-09-19T13:10:12Z

@@ Line 51: / Line 51: @@
 ** This is a task to address the compliance issues found when the LTP and POSIX compliance tests were run against a build created using Yocto Project.
 ** The test results from running these tests against a build created using Yocto Project are at https://wiki.yoctoproject.org/wiki/Posix_result and https://wiki.yoctoproject.org/wiki/LTP_result.
 == Misc ==
 * Write a friendly IRC bot for the #yocto channel
 ** Difficultly: Moderate
-** Estimage: 1 Week (requires feedback and iterative development)
+** Estimate: 1 Week (requires feedback and iterative development)
 ** Submitter: dvhart
 ** Possibly named "yocti"

PaulEggleton: Add janitor bugs table

2013-05-09T13:19:41Z

Add janitor bugs table

← Older revision		Revision as of 13:19, 9 May 2013
Line 73:		Line 73:
	*** .someday. (suggest the user add a task to the Janitors list)		*** .someday. (suggest the user add a task to the Janitors list)
	*** I'm sure there are more, current recipe version, maintainer of a recipe, etc.		*** I'm sure there are more, current recipe version, maintainer of a recipe, etc.

			== Janitor entries in Bugzilla ==

			{{#bugzilla:
			\|columns=id,to,estimated,summary,whiteboard,milestone,status
			\|noresultsmessage=None
			\|status=NEW,ACCEPTED,IN PROGRESS DESIGN,NEEDINFO
			\|severity=janitors
			}}

Dvhart: Clear create-pull-request to use git request-pull, completed by dvhart.

2011-05-24T16:16:53Z

Clear create-pull-request to use git request-pull, completed by dvhart.

← Older revision		Revision as of 16:16, 24 May 2011
Line 53:		Line 53:

	== Misc ==		== Misc ==
	* Modify create-pull-request and send-pull-request to use git-request-pull directly.
	** Difficulty: Easy
	** Estimate: 1 Day
	** Submitter: dvhart
	** The output of git-request-pull should be used to pre-populate the cover-letter, leaving the BLURB string in tact.
	** The URL should be harvested from the user's environment so that the script can be used with poky, oe-core, as well as other layers.
	** I wouldn't necessarily object to removing the alternative sending mechanism and make the script depend completely on git tools.

	* Write a friendly IRC bot for the #yocto channel		* Write a friendly IRC bot for the #yocto channel
	** Difficultly: Moderate		** Difficultly: Moderate

Jnfleisc: /* compliance */ added posix, ltp item

2011-05-05T14:58:11Z

compliance: added posix, ltp item

← Older revision		Revision as of 14:58, 5 May 2011
Line 43:		Line 43:
	** Submitter: dvhart		** Submitter: dvhart
	** bbvars.py does a rather dumb regex search for things vaguely resembling variables, the bitbake parser knows how to do this properly.		** bbvars.py does a rather dumb regex search for things vaguely resembling variables, the bitbake parser knows how to do this properly.

			== Compliance ==
			* Fix compliance issues
			** Difficulty: Moderate
			** Estimate: 3 days
			** Submitter: jnfleisc
			** This is a task to address the compliance issues found when the LTP and POSIX compliance tests were run against a build created using Yocto Project.
			** The test results from running these tests against a build created using Yocto Project are at https://wiki.yoctoproject.org/wiki/Posix_result and https://wiki.yoctoproject.org/wiki/LTP_result.

	== Misc ==		== Misc ==

Jnfleisc: /* Build */ added ability to archive work dir

2011-05-05T14:31:50Z

Build: added ability to archive work dir

← Older revision		Revision as of 14:31, 5 May 2011
Line 20:		Line 20:
	** Submitter: dvhart		** Submitter: dvhart
	** Package up the kernel sysroot and make it available on the target. This should become a linux-headers package or similar.		** Package up the kernel sysroot and make it available on the target. This should become a linux-headers package or similar.

			== Build ==
			* Ability to archive work dir
			** Difficulty: Easy
			** Estimate: 2 Days
			** Submitter: LCS suggestion
			** Add the ability to archive the work directory to handle the GPL compliance issue.

	== Documentation ==		== Documentation ==

Dvhart at 17:38, 18 April 2011

2011-04-18T17:38:25Z

← Older revision		Revision as of 17:38, 18 April 2011
Line 14:		Line 14:

	= Tasks =		= Tasks =
			== Kernel ==
			* Build kernel modules on target
			** Difficulty: Moderate
			** Estimate: 3 Days
			** Submitter: dvhart
			** Package up the kernel sysroot and make it available on the target. This should become a linux-headers package or similar.

	== Documentation ==		== Documentation ==
	* Document undocumented variables according to bbvars.py		* Document undocumented variables according to bbvars.py

Dvhart at 21:21, 15 April 2011

2011-04-15T21:21:47Z

← Older revision		Revision as of 21:21, 15 April 2011
Line 1:		Line 1:
			__TOC__

	The following tasks are intended to help people get started working with the Yocto Project. These tasks should not require a lot of context. Anyone with basic programming skills, experience working with Open Source software, and some time on their hands should be able to complete these.		The following tasks are intended to help people get started working with the Yocto Project. These tasks should not require a lot of context. Anyone with basic programming skills, experience working with Open Source software, and some time on their hands should be able to complete these.

Dvhart at 21:20, 15 April 2011

2011-04-15T21:20:17Z

← Older revision		Revision as of 21:20, 15 April 2011
Line 1:		Line 1:
	~~= Yocto Project Janitors =~~
	The following tasks are intended to help people get started working with the Yocto Project. These tasks should not require a lot of context. Anyone with basic programming skills, experience working with Open Source software, and some time on their hands should be able to complete these.		The following tasks are intended to help people get started working with the Yocto Project. These tasks should not require a lot of context. Anyone with basic programming skills, experience working with Open Source software, and some time on their hands should be able to complete these.

Dvhart: /* Tasks */

2011-04-15T21:18:38Z

Tasks

← Older revision		Revision as of 21:18, 15 April 2011
Line 17:		Line 17:
	** Difficulty: Moderate		** Difficulty: Moderate
	** Estimate: 1 Hour (per variable)		** Estimate: 1 Hour (per variable)
			** Submitter: dvhart
	** Start with the variables with the highest count		** Start with the variables with the highest count
	** First add a doctag to meta/conf/documentation.conf		** First add a doctag to meta/conf/documentation.conf
Line 25:		Line 26:
	** Difficulty: Hard		** Difficulty: Hard
	** Estimate: 3 Days		** Estimate: 3 Days
			** Submitter: dvhart
	** bbvars.py does a rather dumb regex search for things vaguely resembling variables, the bitbake parser knows how to do this properly.		** bbvars.py does a rather dumb regex search for things vaguely resembling variables, the bitbake parser knows how to do this properly.

Line 31:		Line 33:
	** Difficulty: Easy		** Difficulty: Easy
	** Estimate: 1 Day		** Estimate: 1 Day
			** Submitter: dvhart
	** The output of git-request-pull should be used to pre-populate the cover-letter, leaving the BLURB string in tact.		** The output of git-request-pull should be used to pre-populate the cover-letter, leaving the BLURB string in tact.
	** The URL should be harvested from the user's environment so that the script can be used with poky, oe-core, as well as other layers.		** The URL should be harvested from the user's environment so that the script can be used with poky, oe-core, as well as other layers.
Line 38:		Line 41:
	** Difficultly: Moderate		** Difficultly: Moderate
	** Estimage: 1 Week (requires feedback and iterative development)		** Estimage: 1 Week (requires feedback and iterative development)
			** Submitter: dvhart
	** Possibly named "yocti"		** Possibly named "yocti"
	** The bot should be either snarky or obsequious		** The bot should be either snarky or obsequious