[RFCv2] OE.org BSP hosting guidelines

[Tom Rini]

On 03/22/2011 01:40 AM, Koen Kooi wrote:
> Hi,
>
> Here's a more refined version based on the feedback received:
>
> --------------------------------------
>
> Allow layers to be hosted on oe.org with access setup to the maintainers liking. The layers should adhere to the following guidelines:
>
> 1) Have a README describing layer dependencies, maintainer and optionally bugtracker and mailinglist(s). The layer's objective/purpose/goal should also be clearly
> documented.
>
> 2) Have a long term commitment to maintain it, dead layers are no good to anyone. If the listed maintainers are unresponsive and the layer no longer maintained for a period of longer than 12 weeks, a layer can be marked as inactive, allocated to a new maintainer or removed at the discretion of the TSC/OE Board.
>
> 3) Allow external contributions where applicable (e.g. allow pull requests) as clearly documented in the README.
>
> 4) SRC_URI should be fetchable by the unwashed masses for most, if not all of the recipes
>
> 5) The OE hosted layer is the master, not a mirror.
>
> 6) The layer shouldn't contain much, if any source code for recipe software, this should be referenced by SRC_URI except in exceptional cases.
>
> Companies are strongly encouraged to become a patron of the e.V. and/or donate to it when having their layers hosted.
>
> --------------------------------------

Looks good to me.

-- 
Tom Rini
Mentor Graphics Corporation