Bug 12573 - split maintainers.inc into recipes themsevles
Summary: split maintainers.inc into recipes themsevles
Status: RESOLVED WONTFIX
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: configuration (show other bugs)
Version: 2.5
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Alexander Kanavin
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-02-28 08:43 UTC by Alexander Kanavin
Modified: 2018-03-01 15:58 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Comment 1 Alexander Kanavin 2018-02-28 10:17:27 UTC
Note: also update the patchtest to check for it when adding recipes (similar to check for SUMMARY).
Comment 2 Richard Purdie 2018-03-01 15:58:04 UTC
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.