aboutsummaryrefslogtreecommitdiffstats
path: root/recipes/liburiparser
AgeCommit message (Expand)Author
2010-08-03500+ recipes: remove do_stageFrans Meulenbroeks
2010-05-25Make the do_patch apply=yes param implicit if extension is .diff/.patchChris Larson
2010-05-25Rename url params patch=<ignored>/pnum=<n> to apply={yes,no}/striplevel=<n>Chris Larson
2010-04-12recipes: move checksums to recipes from checksums.iniMartin Jansa
2009-03-17rename packages/ to recipes/ per earlier agreementDenys Dmytriyenko
m64'>ChenQi/systemd-qemuarm64 OpenEmbedded Core user contribution treesGrokmirror user
summaryrefslogtreecommitdiffstats
path: root/MAINTAINERS.md
blob: 505c2e234d3c8236b7de094c1b066407e2993d5c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
OpenEmbedded-Core and Yocto Project Maintainer Information
==========================================================

OpenEmbedded and Yocto Project work jointly together to maintain the metadata,
layers, tools and sub-projects that make up their ecosystems.

The projects operate through collaborative development. This currently takes
place on mailing lists for many components as the "pull request on github"
workflow works well for single or small numbers of maintainers but we have
a large number, all with different specialisms and benefit from the mailing
list review process. Changes therefore undergo peer review through mailing
lists in many cases.

This file aims to acknowledge people with specific skills/knowledge/interest
both to recognise their contributions but also empower them to help lead and
curate those components. Where we have people with specialist knowledge in
particular areas, during review patches/feedback from these people in these
areas would generally carry weight.

This file is maintained in OE-Core but may refer to components that are separate
to it if that makes sense in the context of maintainership. The README of specific
layers and components should ultimately be definitive about the patch process and
maintainership for the component.

Recipe Maintainers
------------------

See meta/conf/distro/include/maintainers.inc

Component/Subsystem Maintainers
-------------------------------

* Kernel (inc. linux-yocto, perf): Bruce Ashfield
* Reproducible Builds: Joshua Watt
* Toaster: David Reyna
* Hash-Equivalence: Joshua Watt
* Recipe upgrade infrastructure: Alex Kanavin
* Toolchain: Khem Raj
* ptest-runner: Aníbal Limón
* opkg: Alex Stewart
* devtool: Saul Wold
* eSDK: Saul Wold
* overlayfs: Vyacheslav Yurkov

Maintainers needed
------------------

* Pseudo
* Layer Index
* recipetool
* QA framework/automated testing
* error reporting system/web UI
* wic
* Patchwork
* Patchtest
* Matchbox
* Sato
* Autobuilder

Layer Maintainers needed
------------------------

* meta-gplv2 (ideally new strategy but active maintainer welcome)

Shadow maintainers/development needed
--------------------------------------

* toaster
* bitbake