| Summary: | split maintainers.inc into recipes themsevles | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Alexander Kanavin <alex.kanavin> |
| Component: | configuration | Assignee: | Alexander Kanavin <alex.kanavin> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Undecided | CC: | richard.purdie |
| Version: | 2.5 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Alexander Kanavin
2018-02-28 08:43:11 UTC
Note: also update the patchtest to check for it when adding recipes (similar to check for SUMMARY). I think we're jumping the gun on making this change. There are proc and cons to a centralised list, the central approach does mean we get a good/easy snapshot of who is doing what and when people leave the project, it does make it easier to update, without the underlying recipes needing to be changed individually. In triage we did a quick poll and we're torn on this. The discussion linked to on oe-arch is really tangential to that original discussion and not a decision on this. There is also continued discussion about whether we want more "maintainers" like tooling like the kernel has and changing to individual recipe markup would make such a thing harder. I'm therefore in favour of a common maintainer information, at least for now. I'm therefore resolving this as WONTFIX right now. |