Janitors: Difference between revisions
From Yocto Project
Jump to navigationJump to search
(Created page with '= 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 wit…') |
No edit summary |
||
| Line 2: | Line 2: | ||
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. | ||
When adding tasks, please be sure to follow this format: | When adding tasks, please be sure to follow this format: | ||
* Task Title | * Task Title | ||
| Line 14: | Line 11: | ||
As these are meant to help people get started, tasks should be self-contained and doable without a lot of context dealing with bitbake based build systems. Re-writing the recipe parser in C is probably not a good fit for this task list. | As these are meant to help people get started, tasks should be self-contained and doable without a lot of context dealing with bitbake based build systems. Re-writing the recipe parser in C is probably not a good fit for this task list. | ||
= Tasks = | |||
== Documentation == | == Documentation == | ||
* Document undocumented variables according to bbvars.py | * Document undocumented variables according to bbvars.py | ||
Revision as of 21:01, 15 April 2011
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.
When adding tasks, please be sure to follow this format:
* Task Title ** Difficulty: (Hard|Moderate|Easy) ** Estimate: 0-9 (Day|Hour)s? ** Task item detail ** Task item detail
As these are meant to help people get started, tasks should be self-contained and doable without a lot of context dealing with bitbake based build systems. Re-writing the recipe parser in C is probably not a good fit for this task list.
Tasks
Documentation
- Document undocumented variables according to bbvars.py
- Difficulty: Moderate
- Estimate: 1 Hour (per variable)
- Start with the variables with the highest count
- First add a doctag to meta/conf/documentation.conf
- Second prepare a patch to documentation/poky-ref-manual/poky-ref-manual.xml
$ scripts/contrib/bbvars.py -d documentation/poky-ref-manual/poky-ref-manual.xml -t meta/conf/documentation.conf -m meta
- Rewrite bbvars.py to use bitbake to find variables
- Difficulty: Hard
- Estimate: 3 Days
- bbvars.py does a rather dumb regex search for things vaguely resembling variables, the bitbake parser knows how to do this properly.
Misc
- Modify create-pull-request and send-pull-request to use git-request-pull directly.
- Difficulty: Easy
- Estimate: 1 Day
- 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.
