https://wiki.yoctoproject.org/wiki/api.php?action=feedcontributions&user=Darknighte&feedformat=atomYocto Project - User contributions [en]2024-03-29T11:40:11ZUser contributionsMediaWiki 1.39.5https://wiki.yoctoproject.org/wiki/index.php?title=Third_Party_BSP_Release_Process&diff=13002Third Party BSP Release Process2014-06-10T21:32:00Z<p>Darknighte: Updating broken link</p>
<hr />
<div>==Overview==<br />
<br />
Third Party BSPs may be released with any major/minor Yocto release by the maintainers of the various BSP layers. The process for including a BSP release into a yocto release has a few routes, some less complicated than others.<br />
<br />
===Release Requirements===<br />
* If your DL_DIR contains source which we are required to provide and that source package/revision does not exist at http://downloads.yoctoproject.org/mirror/sources/ you MUST provide the source, as generated from your DL_DIR.<br />
* md5sums must be generated for EVERY file to be included in the release. Please use something similar to <code> find . -type f -exec md5sum {} \; >> ../mybsp-poky-edison-6.0.md5sum </code> to generate.<br />
** This should include additional files needed from your DL_DIR. <br />
** I do validate every file's md5sum prior to release and will not gpg sign an invalid .md5sum <br />
* You must include release notes.<br />
* You should include some sort of QA report, preferably a link to the QA report on the yocto wiki.<br />
* You should inform the Yocto Release Engineer (elizabeth.flanagan@intel.com) at least 2 weeks prior to your intended release date (We prefer 4 weeks so we don't surprise those kind folks who mirror yocto). <br />
* Everything required for release must available to the Yocto Release Engineer at least 48 hours prior to release. This time is needed for mirror propagation.<br />
* Please do NOT mix major releases (e.g. building a meta-foo bsp layer with edison 6.0 and meta-qt3 5.0.1 ).<br />
* Please ensure that your release is built with a known poky release.<br />
<br />
===Release Checklist===<br />
<br />
2-4 Weeks Prior:<br />
* You have emailed the Yocto Release Engineer with your intention to release. Please try to give an estimate size of the release and against what released version of yocto you are building against.<br />
<p></p><br />
Prior to the Release:<br />
* You have generated a tested BSP release against a known released version of yocto. Please include the git hash for EVERY official yocto layer you have built against. (meta-qt3, etc). <br />
* You have created a publicly accessible QA report that the release may link against.<br />
* You have generated an md5sum file of all files needed.<br />
* You have validated that all required source files are either in http://downloads.yoctoproject.org/sources or in the area to be used for the release.<br />
* You have created a valid and documented BSP layer tarball named LAYERNAME-RELEASENAME-M.m.p.tar.bz2<br />
<p></p>48 Hours Prior to your release:<br />
* You have emailed the Yocto Release Engineer a link to download all files needed for the release<br />
* I validate the md5sums<br />
* I gpg sign the .md5sum file and prepare the release for the release directory/mirrors<br />
<p></p><br />
Hours Prior to release:<br />
* Download links are made live and verified by both the Yocto Release Engineer and You.<br />
* If you would like the release announcement to be sent out to yocto-announce you have provided the text to the Yocto Community Manager (Jefro) and the Yocto Release Engineer.</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Main_Page&diff=8511Main Page2013-01-22T16:16:05Z<p>Darknighte: /* Current Project Status */</p>
<hr />
<div>== Welcome to the Yocto Project Wiki! ==<br />
=== Current Project Status and Schedule ===<br />
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.4_Status<br />
<br />
https://wiki.yoctoproject.org/wiki/Yocto_1.4_Schedule<br />
<br />
=== Main Wiki Sections ===<br />
* [[Planning and Governance]]<br />
* [[Community Guidelines]]<br />
* [[Processes and Activities]]<br />
** [[YoctoCalendar]]<br />
* [[Projects]]<br />
* [[Yocto Interest Groups]]<br />
* [[FAQ]]<br />
* [[How do I]]<br />
* [[Contributors]]<br />
* [[Training]]<br />
<br />
== Other resources ==<br />
* [http://yoctoproject.org Yocto Project Front Page]</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Project_v1.3_Status&diff=6430Yocto Project v1.3 Status2012-06-26T15:18:14Z<p>Darknighte: /* Milestone 2 */</p>
<hr />
<div>Yocto Project 1.3 release Status<br />
<br />
= Project Dashboard =<br />
[[File: feature-burndown13.png]]<br />
<br />
<br/><br/><br />
<br />
= Feature/Task Board = <br />
== Overview ==<br />
{|border="1" {{table}}<br />
| align="center" style="background:#f0f0f0;"|'''Scheduled'''<br />
| align="center" style="background:#f0f0f0;"|'''Design'''<br />
| align="center" style="background:#f0f0f0;"|'''Design Review'''<br />
| align="center" style="background:#f0f0f0;"|'''Development'''<br />
| align="center" style="background:#f0f0f0;"|'''Patch Review'''<br />
| align="center" style="background:#f0f0f0;"|'''Merged'''<br />
| align="center" style="background:#f0f0f0;"|'''Testing'''<br />
| align="center" style="background:#00ff00;"|'''Done'''<br />
| align="center" style="background:#ff0000;"|'''Blocked'''<br />
|-valign="top"<br />
|{{#bugzilla:<br />
|columns=id,to,milestone<br />
|filters=whiteboard%3D%(scheduled)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified, closed)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
}}<br />
||{{#bugzilla:<br />
|columns=id,to,milestone<br />
|filters=whiteboard%3D%(design)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
}}<br />
||{{#bugzilla:<br />
|columns=id,to,milestone<br />
|filters=whiteboard%3D%(design review)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
}}<br />
||{{#bugzilla:<br />
|columns=id,to,milestone<br />
|filters=whiteboard%3D%(development%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
}}<br />
||{{#bugzilla:<br />
|columns=id,to,milestone<br />
|filters=whiteboard%3D%(patch review)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
}}<br />
||{{#bugzilla:<br />
|columns=id,to,milestone<br />
|status=RESOLVED<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
}}<br />
||{{#bugzilla:<br />
|columns=id,to,milestone<br />
|filters=whiteboard%3D%(testing)%<br />
|noresultsmessage="None"<br />
|status=!VERIFIED<br />
|milestone=1.3 M1,1.3 M2,1.3 M3, 1.3 M4<br />
|sort=milestone,to<br />
}}<br />
||{{#bugzilla:<br />
|columns=id,to,milestone<br />
|status=verified, closed<br />
|milestone=1.3 M1,1.3 M2,1.3 M3, 1.3 M4<br />
|sort=milestone,to<br />
}}<br />
||{{#bugzilla:<br />
|columns=id,to,milestone<br />
|filters=whiteboard%3D%(blocked)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3, 1.3 M4<br />
|sort=milestone,to<br />
}}<br />
|}<br />
<br />
== List View ==<br />
=== Blocked === <br />
{{#bugzilla:<br />
|columns=id,to,estimated,whiteboard,milestone,status<br />
|filters=whiteboard%3D%(blocked)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3, 1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br />
=== Scheduled ===<br />
{{#bugzilla:<br />
|columns=id,to,estimated,summary,whiteboard,milestone,status<br />
|filters=whiteboard%3D%(scheduled)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified, closed)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br />
=== Design ===<br />
{{#bugzilla:<br />
|columns=id,to,estimated,summary,whiteboard,milestone,status<br />
|filters=whiteboard%3D%(design)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br />
=== Design Review ===<br />
{{#bugzilla:<br />
|columns=id,to,estimated,summary,whiteboard,milestone,status<br />
|filters=whiteboard%3D%(design review)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br />
=== Development ===<br />
{{#bugzilla:<br />
|columns=id,to,estimated,summary,whiteboard,milestone,status<br />
|filters=whiteboard%3D%(development%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br />
=== Patch Review ===<br />
{{#bugzilla:<br />
|columns=id,to,estimated,summary,whiteboard,milestone,status<br />
|filters=whiteboard%3D%(patch review)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br />
=== Merged ===<br />
{{#bugzilla:<br />
|columns=id,to,estimated,summary,whiteboard,milestone,status<br />
|status=RESOLVED<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br />
=== Testing ===<br />
{{#bugzilla:<br />
|columns=id,to,estimated,summary,whiteboard,milestone,status<br />
|filters=whiteboard%3D%(testing)%<br />
|noresultsmessage="None"<br />
|status=!VERIFIED<br />
|milestone=1.3 M1,1.3 M2,1.3 M3, 1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br />
=== Done ===<br />
{{#bugzilla:<br />
|columns=id,to,estimated,summary,whiteboard,milestone,status<br />
|status=verified, closed<br />
|milestone=1.3 M1,1.3 M2,1.3 M3, 1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br/><br/><br />
<br />
= Yocto Project SWAT team = <br />
Chairperson of the current week: nitin.a.kamble@intel.com <br/> <br/><br />
Please see here for the details of the SWAT team: https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team<br />
<br/><br/><br />
<br />
= Yocto Project 1.3 Release Criteria = <br />
== Milestone 1 == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Target''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Status'''<br />
|- <br />
| Functional Completion || All P1 features are completed. || bgcolor="" | [[File: feature-burndown13-M1.png]] <br/> See https://wiki.yoctoproject.org/wiki/Yocto_1.3_Schedule for details.<br />
|- <br />
| Build and Release (Yocto) || All completed features can be built with no errors. || bgcolor="" | <br />
|- <br />
| Build and Release (BSPs) || Core BSPs can be built with no errors. || bgcolor="" |<br />
|- <br />
| Open Bugs || All bugs have been dispositioned. High issues have been fixed. || bgcolor="" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_status=NEW&version=1.3] - new bugs for 1.3.<br>[http://bugzilla.yoctoproject.org/buglist.cgi?bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&columnlist=bug_severity%2Cpriority%2Ctarget_milestone%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc&priority=High&query_format=advanced&target_milestone=---&target_milestone=1.3%20M1&target_milestone=1.3%20M1&target_milestone=1.3%20M3&target_milestone=1.3%20M4&query_based_on= HIGH priority bugs] - high bugs for 1.3 <br>See trend chart at https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.<br />
|- <br />
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="" | https://wiki.yoctoproject.org/wiki/Yocto_1.3_Milestone_Test_Report<br />
|- <br />
| Distros Tested || Fedora, Ubuntu, Opensuse current version || bgcolor="" | <br />
|- <br />
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="" | https://wiki.yoctoproject.org/wiki/Yocto_1.3_Milestone_Test_Report<br />
|- <br />
| Documentation || TBD || bgcolor="" |<br />
|- <br />
| Build Performance || Try to at least maintain the current performance and improve if possible. || bgcolor="" | <br />
|-<br />
| Package Update || 50% of the target || bgcolor="" |<br />
|- <br />
| Upstream Commits || Have upstream status updated on 100% of patches (so that we can have a status update) || bgcolor="" | <br />
|- <br />
| Publication || Yocto 1.3, Milestone 1 release is announced || bgcolor="" |<br />
|}<br />
<br/><br/><br />
<br />
== Milestone 2 == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Milestone 2 Target''' || ! scope="col" bgcolor="grey" | '''Milestone 2 Status'''<br />
|- <br />
| Functional Completion || All P1 features are completed. || bgcolor="" | [[File: feature-burndown13-M2.png]] <br/> See https://wiki.yoctoproject.org/wiki/Yocto_1.3_Schedule for details.<br />
|- <br />
| Build and Release (Yocto) || All completed features can be built with no errors. || bgcolor="" | <br />
|- <br />
| Build and Release (BSPs) || Core BSPs can be built with no errors. || bgcolor="" |<br />
|- <br />
| Open Bugs || All bugs have been dispositioned. M2 High issues have been fixed. || bgcolor="" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_status=NEW&version=1.3] - new bugs for 1.3.<br>[http://bugzilla.yoctoproject.org/buglist.cgi?bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&columnlist=bug_severity%2Cpriority%2Ctarget_milestone%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc&priority=High&query_format=advanced&target_milestone=---&target_milestone=1.3%20M1&target_milestone=1.3%20M1&target_milestone=1.3%20M3&target_milestone=1.3%20M4&query_based_on= HIGH priority bugs] - high bugs for 1.3 <br>See trend chart at https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.<br />
|- <br />
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="" | https://wiki.yoctoproject.org/wiki/Yocto_1.3_Milestone_Test_Report<br />
|- <br />
| Distros Tested || Fedora, Ubuntu, Opensuse current version || bgcolor="" | <br />
|- <br />
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="" | https://wiki.yoctoproject.org/wiki/Yocto_1.3_Milestone_Test_Report<br />
|- <br />
| Documentation || TBD || bgcolor="" |<br />
|- <br />
| Build Performance || Try to at least maintain the current performance and improve if possible. || bgcolor="" | <br />
|-<br />
| Package Update || 70% of the target || bgcolor="" |<br />
|- <br />
| Upstream Commits || Have upstream status updated on 100% of patches (so that we can have a status update) || bgcolor="" | <br />
|- <br />
| Publication || Yocto 1.3, Milestone 2 release is announced || bgcolor="" |<br />
|}<br />
<br/><br/></div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Project_v1.3_Status&diff=6429Yocto Project v1.3 Status2012-06-26T15:15:28Z<p>Darknighte: /* Milestone 1 */</p>
<hr />
<div>Yocto Project 1.3 release Status<br />
<br />
= Project Dashboard =<br />
[[File: feature-burndown13.png]]<br />
<br />
<br/><br/><br />
<br />
= Feature/Task Board = <br />
== Overview ==<br />
{|border="1" {{table}}<br />
| align="center" style="background:#f0f0f0;"|'''Scheduled'''<br />
| align="center" style="background:#f0f0f0;"|'''Design'''<br />
| align="center" style="background:#f0f0f0;"|'''Design Review'''<br />
| align="center" style="background:#f0f0f0;"|'''Development'''<br />
| align="center" style="background:#f0f0f0;"|'''Patch Review'''<br />
| align="center" style="background:#f0f0f0;"|'''Merged'''<br />
| align="center" style="background:#f0f0f0;"|'''Testing'''<br />
| align="center" style="background:#00ff00;"|'''Done'''<br />
| align="center" style="background:#ff0000;"|'''Blocked'''<br />
|-valign="top"<br />
|{{#bugzilla:<br />
|columns=id,to,milestone<br />
|filters=whiteboard%3D%(scheduled)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified, closed)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
}}<br />
||{{#bugzilla:<br />
|columns=id,to,milestone<br />
|filters=whiteboard%3D%(design)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
}}<br />
||{{#bugzilla:<br />
|columns=id,to,milestone<br />
|filters=whiteboard%3D%(design review)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
}}<br />
||{{#bugzilla:<br />
|columns=id,to,milestone<br />
|filters=whiteboard%3D%(development%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
}}<br />
||{{#bugzilla:<br />
|columns=id,to,milestone<br />
|filters=whiteboard%3D%(patch review)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
}}<br />
||{{#bugzilla:<br />
|columns=id,to,milestone<br />
|status=RESOLVED<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
}}<br />
||{{#bugzilla:<br />
|columns=id,to,milestone<br />
|filters=whiteboard%3D%(testing)%<br />
|noresultsmessage="None"<br />
|status=!VERIFIED<br />
|milestone=1.3 M1,1.3 M2,1.3 M3, 1.3 M4<br />
|sort=milestone,to<br />
}}<br />
||{{#bugzilla:<br />
|columns=id,to,milestone<br />
|status=verified, closed<br />
|milestone=1.3 M1,1.3 M2,1.3 M3, 1.3 M4<br />
|sort=milestone,to<br />
}}<br />
||{{#bugzilla:<br />
|columns=id,to,milestone<br />
|filters=whiteboard%3D%(blocked)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3, 1.3 M4<br />
|sort=milestone,to<br />
}}<br />
|}<br />
<br />
== List View ==<br />
=== Blocked === <br />
{{#bugzilla:<br />
|columns=id,to,estimated,whiteboard,milestone,status<br />
|filters=whiteboard%3D%(blocked)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3, 1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br />
=== Scheduled ===<br />
{{#bugzilla:<br />
|columns=id,to,estimated,summary,whiteboard,milestone,status<br />
|filters=whiteboard%3D%(scheduled)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified, closed)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br />
=== Design ===<br />
{{#bugzilla:<br />
|columns=id,to,estimated,summary,whiteboard,milestone,status<br />
|filters=whiteboard%3D%(design)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br />
=== Design Review ===<br />
{{#bugzilla:<br />
|columns=id,to,estimated,summary,whiteboard,milestone,status<br />
|filters=whiteboard%3D%(design review)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br />
=== Development ===<br />
{{#bugzilla:<br />
|columns=id,to,estimated,summary,whiteboard,milestone,status<br />
|filters=whiteboard%3D%(development%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br />
=== Patch Review ===<br />
{{#bugzilla:<br />
|columns=id,to,estimated,summary,whiteboard,milestone,status<br />
|filters=whiteboard%3D%(patch review)%<br />
|noresultsmessage="None"<br />
|status=!(RESOLVED,verified)<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br />
=== Merged ===<br />
{{#bugzilla:<br />
|columns=id,to,estimated,summary,whiteboard,milestone,status<br />
|status=RESOLVED<br />
|milestone=1.3 M1,1.3 M2,1.3 M3,1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br />
=== Testing ===<br />
{{#bugzilla:<br />
|columns=id,to,estimated,summary,whiteboard,milestone,status<br />
|filters=whiteboard%3D%(testing)%<br />
|noresultsmessage="None"<br />
|status=!VERIFIED<br />
|milestone=1.3 M1,1.3 M2,1.3 M3, 1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br />
=== Done ===<br />
{{#bugzilla:<br />
|columns=id,to,estimated,summary,whiteboard,milestone,status<br />
|status=verified, closed<br />
|milestone=1.3 M1,1.3 M2,1.3 M3, 1.3 M4<br />
|sort=milestone,to<br />
|total=estimated<br />
}}<br />
<br/><br/><br />
<br />
= Yocto Project SWAT team = <br />
Chairperson of the current week: nitin.a.kamble@intel.com <br/> <br/><br />
Please see here for the details of the SWAT team: https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team<br />
<br/><br/><br />
<br />
= Yocto Project 1.3 Release Criteria = <br />
== Milestone 1 == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Target''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Status'''<br />
|- <br />
| Functional Completion || All P1 features are completed. || bgcolor="" | [[File: feature-burndown13-M1.png]] <br/> See https://wiki.yoctoproject.org/wiki/Yocto_1.3_Schedule for details.<br />
|- <br />
| Build and Release (Yocto) || All completed features can be built with no errors. || bgcolor="" | <br />
|- <br />
| Build and Release (BSPs) || Core BSPs can be built with no errors. || bgcolor="" |<br />
|- <br />
| Open Bugs || All bugs have been dispositioned. High issues have been fixed. || bgcolor="" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_status=NEW&version=1.3] - new bugs for 1.3.<br>[http://bugzilla.yoctoproject.org/buglist.cgi?bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&columnlist=bug_severity%2Cpriority%2Ctarget_milestone%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc&priority=High&query_format=advanced&target_milestone=---&target_milestone=1.3%20M1&target_milestone=1.3%20M1&target_milestone=1.3%20M3&target_milestone=1.3%20M4&query_based_on= HIGH priority bugs] - high bugs for 1.3 <br>See trend chart at https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.<br />
|- <br />
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="" | https://wiki.yoctoproject.org/wiki/Yocto_1.3_Milestone_Test_Report<br />
|- <br />
| Distros Tested || Fedora, Ubuntu, Opensuse current version || bgcolor="" | <br />
|- <br />
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="" | https://wiki.yoctoproject.org/wiki/Yocto_1.3_Milestone_Test_Report<br />
|- <br />
| Documentation || TBD || bgcolor="" |<br />
|- <br />
| Build Performance || Try to at least maintain the current performance and improve if possible. || bgcolor="" | <br />
|-<br />
| Package Update || 50% of the target || bgcolor="" |<br />
|- <br />
| Upstream Commits || Have upstream status updated on 100% of patches (so that we can have a status update) || bgcolor="" | <br />
|- <br />
| Publication || Yocto 1.3, Milestone 1 release is announced || bgcolor="" |<br />
|}<br />
<br/><br/><br />
<br />
== Milestone 2 == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Milestone 2 Target''' || ! scope="col" bgcolor="grey" | '''Milestone 2 Status'''<br />
|- <br />
| Functional Completion || All P1 features are completed. || bgcolor="" | [[File: feature-burndown13-M2.png]] <br/> See https://wiki.yoctoproject.org/wiki/Yocto_1.2_Schedule for details.<br />
|- <br />
| Build and Release (Yocto) || All completed features can be built with no errors. || bgcolor="" | <br />
|- <br />
| Build and Release (BSPs) || Core BSPs can be built with no errors. || bgcolor="" |<br />
|- <br />
| Open Bugs || All bugs have been dispositioned. M2 High issues have been fixed. || bgcolor="" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_status=NEW&version=1.3] - new bugs for 1.3.<br>[http://bugzilla.yoctoproject.org/buglist.cgi?bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&columnlist=bug_severity%2Cpriority%2Ctarget_milestone%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc&priority=High&query_format=advanced&target_milestone=---&target_milestone=1.3%20M1&target_milestone=1.3%20M1&target_milestone=1.3%20M3&target_milestone=1.3%20M4&query_based_on= HIGH priority bugs] - high bugs for 1.3 <br>See trend chart at https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.<br />
|- <br />
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="" | https://wiki.yoctoproject.org/wiki/Yocto_1.3_Milestone_Test_Report<br />
|- <br />
| Distros Tested || Fedora, Ubuntu, Opensuse current version || bgcolor="" | <br />
|- <br />
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="" | https://wiki.yoctoproject.org/wiki/Yocto_1.3_Milestone_Test_Report<br />
|- <br />
| Documentation || TBD || bgcolor="" |<br />
|- <br />
| Build Performance || Try to at least maintain the current performance and improve if possible. || bgcolor="" | <br />
|-<br />
| Package Update || 70% of the target || bgcolor="" |<br />
|- <br />
| Upstream Commits || Have upstream status updated on 100% of patches (so that we can have a status update) || bgcolor="" | <br />
|- <br />
| Publication || Yocto 1.3, Milestone 2 release is announced || bgcolor="" |<br />
|}<br />
<br/><br/></div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Prop&diff=6098Working Draft of Compliance Prop2012-05-31T17:33:41Z<p>Darknighte: Add Yocto version to registration block and URL for organization</p>
<hr />
<div>= YOCTO PROJECT Compliance Guidelines =<br />
== Introduction ==<br />
The YOCTO PROJECT compliance program has been established to strengthen the YOCTO PROJECT strategic initiatives by providing guidelines for the use of its branding. This program is intended to provide a minimum level of standardization in order to enable both individual and corporate members to deliver implementations which support the goals of the project and contribute to an ecosystem built around the project. In addition, this program is intended to provide concrete benefits by associating a common set of definitions with the use of the YOCTO PROJECT branding. <br />
<br />
Some of the goals of the YOCTO PROJECT that the compliance program is intended to strengthen include:<br />
*Reducing fragmentation in the embedded market by encouraging the development of and collaboration on a common set of tools, standards and practices.<br />
*Ensuring that these tools, standards, and practices are architecturally independent as much as possible.<br />
<br />
Compliance as defined by the YOCTO PROJECT governs the RIGHTS for the usage of the project name, Logo and marks in association with products, marketing materials, and announcements. The YOCTO PROJECT brand guidelines describes how members that follow these compliance guidelines are allowed to use these RIGHTS. (Add document link here – document and guidelines are in development)<br />
<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF RESULTING PRODUCTS OR PROJECTS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
:'''''Note: The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here).''''' <br/><br />
<br />
== Compliance levels, Compliance Recommendations and Terminology ==<br />
The YOCTO PROJECT compliance program defines steps to register compliance for both individual and corporate members.<br />
<br />
== YOCTO PROJECT Brand Documentation ==<br />
Clear documentation how the brands can be used (palette etc) as well as when they can be used in conjunction with the above are found in the “YOCTO PROJECT Brand Usage Guide.” (add link here)<br />
<br />
= YOCTO PROJECT Aligned = <br />
<br />
=== Registration Steps ===<br />
:To register compliance for use of the YOCTO PROJECT Aligned logo/text:<br />
:# Edit the designated wiki page as follows: <br />
:## copy the text below<br />
:## add a new section for your project / organization<br />
:# Send email to the [mailto:yocto-ab@yoctoproject.org Yocto Advisory Board] requesting registration<br />
:# When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
== YOCTO PROJECT Aligned Registration Template == <br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|-<br />
| '''URL to organization or product link''' || (replace with appropriate URL)<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
== YOCTO PROJECT Aligned Registrar ==<br />
<br />
=== OpenSDR (Consultant) ===<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || OpenSDR (Example) <br />
|-<br />
| '''Contact Name / Email address''' || Philip Balister / philip@balister.org<br />
|-<br />
| '''Registration Date''' || May 20, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|-<br />
| '''URL to organization or product link''' || http://opensdr.com/<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y || bgcolor="" | <br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y || bgcolor="" | <br />
|}<br />
<br />
= YOCTO PROJECT Compatible = <br />
<br />
=== Registration Steps ===<br />
:To register compliance for use of the YOCTO PROJECT Compatible logo/text:<br />
:# Edit the designated wiki page as follows: <br />
:## copy the text below<br />
:## add a new section for your project / organization<br />
:# Send email to the [mailto:yocto-ab@yoctoproject.org Yocto Advisory Board] requesting registration<br />
:# When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Product / Project name''' || (Replace with text)<br />
|-<br />
| '''Product release version''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|-<br />
| '''Yocto version tested''' || (replace with appropriate release # or possibly a link )<br />
|-<br />
| '''URL to organization or product link''' || (replace with appropriate URL)<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Compatible Acceptance Criteria == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT working group, regardless of organization size || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If any item in the "YOCTO PROJECT Compatible Compliance Recommendations" list is not true, is this documented in the testing report?|| Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
|}<br />
<br />
== YOCTO PROJECT Compatible Compliance Recommendations == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Compatible Registrar == <br />
<br />
=== Mentor Graphics Embedded Linux ===<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || Mentor Graphics, Inc <br />
|-<br />
| '''Contact Name / Email address''' || Sean Hudson, Sean_Hudson@mentor.com<br />
|-<br />
| '''Product / Project name''' || Mentor Embedded Linux<br />
|-<br />
| '''Product release version''' || v5.0<br />
|-<br />
| '''Registration Date''' || March 27, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|-<br />
| '''Yocto version tested''' || Version 1.1<br />
|-<br />
| '''URL to organization or product link''' || http://www.mentor.com/embedded-software/linux/<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Compatible Acceptance Criteria === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT || Y || bgcolor="" | <br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y || bgcolor="" | <br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y || bgcolor="" | <br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y || bgcolor="" | <br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y || bgcolor="" | <br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y || bgcolor="" | <br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y || bgcolor="" | <br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y || bgcolor="" | <br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y || bgcolor="" | <br />
|-<br />
| If any item in the "YOCTO PROJECT Compatible Compliance Recommendations" list is not true, is this documented in the testing report?|| Y || bgcolor="" | <br />
|-<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Compatible Compliance Recommendations === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y || bgcolor="" | Based on YOCTO PROJECT v1.1<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y || bgcolor="" | <br />
|}</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Prop&diff=6097Working Draft of Compliance Prop2012-05-31T17:09:55Z<p>Darknighte: Substituted "compatible" for "powered"</p>
<hr />
<div>= YOCTO PROJECT Compliance Guidelines =<br />
== Introduction ==<br />
The YOCTO PROJECT compliance program has been established to strengthen the YOCTO PROJECT strategic initiatives by providing guidelines for the use of its branding. This program is intended to provide a minimum level of standardization in order to enable both individual and corporate members to deliver implementations which support the goals of the project and contribute to an ecosystem built around the project. In addition, this program is intended to provide concrete benefits by associating a common set of definitions with the use of the YOCTO PROJECT branding. <br />
<br />
Some of the goals of the YOCTO PROJECT that the compliance program is intended to strengthen include:<br />
*Reducing fragmentation in the embedded market by encouraging the development of and collaboration on a common set of tools, standards and practices.<br />
*Ensuring that these tools, standards, and practices are architecturally independent as much as possible.<br />
<br />
Compliance as defined by the YOCTO PROJECT governs the RIGHTS for the usage of the project name, Logo and marks in association with products, marketing materials, and announcements. The YOCTO PROJECT brand guidelines describes how members that follow these compliance guidelines are allowed to use these RIGHTS. (Add document link here – document and guidelines are in development)<br />
<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF RESULTING PRODUCTS OR PROJECTS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
:'''''Note: The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here).''''' <br/><br />
<br />
== Compliance levels, Compliance Recommendations and Terminology ==<br />
The YOCTO PROJECT compliance program defines steps to register compliance for both individual and corporate members.<br />
<br />
== YOCTO PROJECT Brand Documentation ==<br />
Clear documentation how the brands can be used (palette etc) as well as when they can be used in conjunction with the above are found in the “YOCTO PROJECT Brand Usage Guide.” (add link here)<br />
<br />
= YOCTO PROJECT Aligned = <br />
<br />
=== Registration Steps ===<br />
:To register compliance for use of the YOCTO PROJECT Aligned logo/text:<br />
:# Edit the designated wiki page as follows: <br />
:## copy the text below<br />
:## add a new section for your project / organization<br />
:# Send email to the [mailto:yocto-ab@yoctoproject.org Yocto Advisory Board] requesting registration<br />
:# When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
== YOCTO PROJECT Aligned Registration Template == <br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
== YOCTO PROJECT Aligned Registrar ==<br />
<br />
=== OpenSDR (Consultant) ===<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || OpenSDR (Example) <br />
|-<br />
| '''Contact Name / Email address''' || Philip Balister / philip@balister.org<br />
|-<br />
| '''Registration Date''' || May 20, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y || bgcolor="" | <br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y || bgcolor="" | <br />
|}<br />
<br />
= YOCTO PROJECT Compatible = <br />
<br />
=== Registration Steps ===<br />
:To register compliance for use of the YOCTO PROJECT Compatible logo/text:<br />
:# Edit the designated wiki page as follows: <br />
:## copy the text below<br />
:## add a new section for your project / organization<br />
:# Send email to the [mailto:yocto-ab@yoctoproject.org Yocto Advisory Board] requesting registration<br />
:# When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Product / Project name''' || (Replace with text)<br />
|-<br />
| '''Product release version''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Compatible Acceptance Criteria == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT working group, regardless of organization size || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If any item in the "YOCTO PROJECT Compatible Compliance Recommendations" list is not true, is this documented in the testing report?|| Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
|}<br />
<br />
== YOCTO PROJECT Compatible Compliance Recommendations == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Compatible Registrar == <br />
<br />
=== Mentor Graphics Embedded Linux ===<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || Mentor Graphics, Inc <br />
|-<br />
| '''Contact Name / Email address''' || Sean Hudson, Sean_Hudson@mentor.com<br />
|-<br />
| '''Product / Project name''' || Mentor Embedded Linux<br />
|-<br />
| '''Product release version''' || v5.0<br />
|-<br />
| '''Registration Date''' || March 27, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Compatible Acceptance Criteria === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT || Y || bgcolor="" | <br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y || bgcolor="" | <br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y || bgcolor="" | <br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y || bgcolor="" | <br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y || bgcolor="" | <br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y || bgcolor="" | <br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y || bgcolor="" | <br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y || bgcolor="" | <br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y || bgcolor="" | <br />
|-<br />
| If any item in the "YOCTO PROJECT Compatible Compliance Recommendations" list is not true, is this documented in the testing report?|| Y || bgcolor="" | <br />
|-<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Compatible Compliance Recommendations === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y || bgcolor="" | Based on YOCTO PROJECT v1.1<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y || bgcolor="" | <br />
|}</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Prop&diff=6096Working Draft of Compliance Prop2012-05-31T17:05:41Z<p>Darknighte: /* Introduction */</p>
<hr />
<div>= YOCTO PROJECT Compliance Guidelines =<br />
== Introduction ==<br />
The YOCTO PROJECT compliance program has been established to strengthen the YOCTO PROJECT strategic initiatives by providing guidelines for the use of its branding. This program is intended to provide a minimum level of standardization in order to enable both individual and corporate members to deliver implementations which support the goals of the project and contribute to an ecosystem built around the project. In addition, this program is intended to provide concrete benefits by associating a common set of definitions with the use of the YOCTO PROJECT branding. <br />
<br />
Some of the goals of the YOCTO PROJECT that the compliance program is intended to strengthen include:<br />
*Reducing fragmentation in the embedded market by encouraging the development of and collaboration on a common set of tools, standards and practices.<br />
*Ensuring that these tools, standards, and practices are architecturally independent as much as possible.<br />
<br />
Compliance as defined by the YOCTO PROJECT governs the RIGHTS for the usage of the project name, Logo and marks in association with products, marketing materials, and announcements. The YOCTO PROJECT brand guidelines describes how members that follow these compliance guidelines are allowed to use these RIGHTS. (Add document link here – document and guidelines are in development)<br />
<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF RESULTING PRODUCTS OR PROJECTS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
:'''''Note: The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here).''''' <br/><br />
<br />
== Compliance levels, Compliance Recommendations and Terminology ==<br />
The YOCTO PROJECT compliance program defines steps to register compliance for both individual and corporate members.<br />
<br />
== YOCTO PROJECT Brand Documentation ==<br />
Clear documentation how the brands can be used (palette etc) as well as when they can be used in conjunction with the above are found in the “YOCTO PROJECT Brand Usage Guide.” (add link here)<br />
<br />
= YOCTO PROJECT Aligned = <br />
<br />
=== Registration Steps ===<br />
:To register compliance for use of the YOCTO PROJECT Aligned logo/text:<br />
:# Edit the designated wiki page as follows: <br />
:## copy the text below<br />
:## add a new section for your project / organization<br />
:# Send email to the [mailto:yocto-ab@yoctoproject.org Yocto Advisory Board] requesting registration<br />
:# When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
== YOCTO PROJECT Aligned Registration Template == <br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
== YOCTO PROJECT Aligned Registrar ==<br />
<br />
=== OpenSDR (Consultant) ===<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || OpenSDR (Example) <br />
|-<br />
| '''Contact Name / Email address''' || Philip Balister / philip@balister.org<br />
|-<br />
| '''Registration Date''' || May 20, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y || bgcolor="" | <br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y || bgcolor="" | <br />
|}<br />
<br />
= YOCTO PROJECT Powered = <br />
<br />
=== Registration Steps ===<br />
:To register compliance for use of the YOCTO PROJECT Powered logo/text:<br />
:# Edit the designated wiki page as follows: <br />
:## copy the text below<br />
:## add a new section for your project / organization<br />
:# Send email to the [mailto:yocto-ab@yoctoproject.org Yocto Advisory Board] requesting registration<br />
:# When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Product / Project name''' || (Replace with text)<br />
|-<br />
| '''Product release version''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Acceptance Criteria == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT working group, regardless of organization size || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
|}<br />
<br />
== YOCTO PROJECT Powered Compliance Recommendations == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Registrar == <br />
<br />
=== Mentor Graphics Embedded Linux ===<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || Mentor Graphics, Inc <br />
|-<br />
| '''Contact Name / Email address''' || Sean Hudson, Sean_Hudson@mentor.com<br />
|-<br />
| '''Product / Project name''' || Mentor Embedded Linux<br />
|-<br />
| '''Product release version''' || v5.0<br />
|-<br />
| '''Registration Date''' || March 27, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Acceptance Criteria === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT || Y || bgcolor="" | <br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y || bgcolor="" | <br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y || bgcolor="" | <br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y || bgcolor="" | <br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y || bgcolor="" | <br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y || bgcolor="" | <br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y || bgcolor="" | <br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y || bgcolor="" | <br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y || bgcolor="" | <br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y || bgcolor="" | <br />
|-<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Compliance Recommendations === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y || bgcolor="" | Based on YOCTO PROJECT v1.1<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y || bgcolor="" | <br />
|}</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Prop&diff=6095Working Draft of Compliance Prop2012-05-31T17:05:23Z<p>Darknighte: Undo revision 6093 by Darknighte (talk)</p>
<hr />
<div>= YOCTO PROJECT Compliance Guidelines =<br />
== Introduction ==<br />
The YOCTO PROJECT compliance program has been established to strengthen the YOCTO PROJECT strategic initiatives by providing guidelines for the use of its branding. This program is intended to provide a minimum level of standardization in order to enable both individual and corporate members to deliver implementations which support the goals of the project and contribute to an ecosystem built around the project. In addition, this program is intended to provide concrete benefits to contributing members by associating a common set of definitions with the use of the YOCTO PROJECT branding. <br />
<br />
Some of the goals of the YOCTO PROJECT that the compliance program is intended to strengthen include:<br />
*Reducing fragmentation in the embedded market by encouraging the development of and collaboration on a common set of tools, standards and practices.<br />
*Ensuring that these tools, standards, and practices are architecturally independent as much as possible.<br />
<br />
Compliance as defined by the YOCTO PROJECT governs the RIGHTS for the usage of the project name, Logo and marks in association with products, marketing materials, and announcements. The YOCTO PROJECT brand guidelines describes how members that follow these compliance guidelines are allowed to use these RIGHTS. (Add document link here – document and guidelines are in development)<br />
<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF RESULTING PRODUCTS OR PROJECTS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
:'''''Note: The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here).''''' <br/><br />
<br />
<br />
== Compliance levels, Compliance Recommendations and Terminology ==<br />
The YOCTO PROJECT compliance program defines steps to register compliance for both individual and corporate members.<br />
<br />
== YOCTO PROJECT Brand Documentation ==<br />
Clear documentation how the brands can be used (palette etc) as well as when they can be used in conjunction with the above are found in the “YOCTO PROJECT Brand Usage Guide.” (add link here)<br />
<br />
= YOCTO PROJECT Aligned = <br />
<br />
=== Registration Steps ===<br />
:To register compliance for use of the YOCTO PROJECT Aligned logo/text:<br />
:# Edit the designated wiki page as follows: <br />
:## copy the text below<br />
:## add a new section for your project / organization<br />
:# Send email to the [mailto:yocto-ab@yoctoproject.org Yocto Advisory Board] requesting registration<br />
:# When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
== YOCTO PROJECT Aligned Registration Template == <br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
== YOCTO PROJECT Aligned Registrar ==<br />
<br />
=== OpenSDR (Consultant) ===<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || OpenSDR (Example) <br />
|-<br />
| '''Contact Name / Email address''' || Philip Balister / philip@balister.org<br />
|-<br />
| '''Registration Date''' || May 20, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y || bgcolor="" | <br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y || bgcolor="" | <br />
|}<br />
<br />
= YOCTO PROJECT Powered = <br />
<br />
=== Registration Steps ===<br />
:To register compliance for use of the YOCTO PROJECT Powered logo/text:<br />
:# Edit the designated wiki page as follows: <br />
:## copy the text below<br />
:## add a new section for your project / organization<br />
:# Send email to the [mailto:yocto-ab@yoctoproject.org Yocto Advisory Board] requesting registration<br />
:# When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Product / Project name''' || (Replace with text)<br />
|-<br />
| '''Product release version''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Acceptance Criteria == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT working group, regardless of organization size || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
|}<br />
<br />
== YOCTO PROJECT Powered Compliance Recommendations == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Registrar == <br />
<br />
=== Mentor Graphics Embedded Linux ===<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || Mentor Graphics, Inc <br />
|-<br />
| '''Contact Name / Email address''' || Sean Hudson, Sean_Hudson@mentor.com<br />
|-<br />
| '''Product / Project name''' || Mentor Embedded Linux<br />
|-<br />
| '''Product release version''' || v5.0<br />
|-<br />
| '''Registration Date''' || March 27, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Acceptance Criteria === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT || Y || bgcolor="" | <br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y || bgcolor="" | <br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y || bgcolor="" | <br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y || bgcolor="" | <br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y || bgcolor="" | <br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y || bgcolor="" | <br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y || bgcolor="" | <br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y || bgcolor="" | <br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y || bgcolor="" | <br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y || bgcolor="" | <br />
|-<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Compliance Recommendations === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y || bgcolor="" | Based on YOCTO PROJECT v1.1<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y || bgcolor="" | <br />
|}</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Prop&diff=6093Working Draft of Compliance Prop2012-05-30T23:04:34Z<p>Darknighte: Flagged the use of the terms Aligned/Powered. Surely we can come up with better, e.g. enabled or enhanced?</p>
<hr />
<div>= YOCTO PROJECT Compliance Guidelines =<br />
== Introduction ==<br />
The YOCTO PROJECT compliance program has been established to strengthen the YOCTO PROJECT strategic initiatives by providing guidelines for the use of its branding. This program is intended to provide a minimum level of standardization in order to enable both individual and corporate members to deliver implementations which support the goals of the project and contribute to an ecosystem built around the project. In addition, this program is intended to provide concrete benefits to contributing members by associating a common set of definitions with the use of the YOCTO PROJECT branding. <br />
<br />
Some of the goals of the YOCTO PROJECT that the compliance program is intended to strengthen include:<br />
*Reducing fragmentation in the embedded market by encouraging the development of and collaboration on a common set of tools, standards and practices.<br />
*Ensuring that these tools, standards, and practices are architecturally independent as much as possible.<br />
<br />
Compliance as defined by the YOCTO PROJECT governs the RIGHTS for the usage of the project name, Logo and marks in association with products, marketing materials, and announcements. The YOCTO PROJECT brand guidelines describes how members that follow these compliance guidelines are allowed to use these RIGHTS. (Add document link here – document and guidelines are in development)<br />
<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF RESULTING PRODUCTS OR PROJECTS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
:'''''Note: The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here).''''' <br/><br />
<br />
<br />
== Compliance levels, Compliance Recommendations and Terminology ==<br />
The YOCTO PROJECT compliance program defines steps to register compliance for both individual and corporate members.<br />
<br />
== YOCTO PROJECT Brand Documentation ==<br />
Clear documentation how the brands can be used (palette etc) as well as when they can be used in conjunction with the above are found in the “YOCTO PROJECT Brand Usage Guide.” (add link here)<br />
<br />
= YOCTO PROJECT _____Aligned (Tier 1 compliance, perhaps the term should be left to the branding document for now?)_____ = <br />
<br />
=== Registration Steps ===<br />
:To register compliance for use of the YOCTO PROJECT _____Aligned (Tier 1 compliance, perhaps the term should be left to the branding document for now?)_____ logo/text:<br />
:# Edit the designated wiki page as follows: <br />
:## copy the text below<br />
:## add a new section for your project / organization<br />
:# Send email to the [mailto:yocto-ab@yoctoproject.org Yocto Advisory Board] requesting registration<br />
:# When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
== YOCTO PROJECT _____Aligned (Tier 1 compliance, perhaps the term should be left to the branding document for now?)_____ Registration Template == <br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
== YOCTO PROJECT _____Aligned (Tier 1 compliance, perhaps the term should be left to the branding document for now?)_____ Registrar ==<br />
<br />
=== OpenSDR (Consultant) ===<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || OpenSDR (Example) <br />
|-<br />
| '''Contact Name / Email address''' || Philip Balister / philip@balister.org<br />
|-<br />
| '''Registration Date''' || May 20, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y || bgcolor="" | <br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y || bgcolor="" | <br />
|}<br />
<br />
= YOCTO PROJECT _____Powered (Tier 2 compliance, perhaps the term should be left to the branding document for now?)_____ = <br />
<br />
=== Registration Steps ===<br />
:To register compliance for use of the YOCTO PROJECT _____Powered (Tier 2 compliance, perhaps the term should be left to the branding document for now?)_____ logo/text:<br />
:# Edit the designated wiki page as follows: <br />
:## copy the text below<br />
:## add a new section for your project / organization<br />
:# Send email to the [mailto:yocto-ab@yoctoproject.org Yocto Advisory Board] requesting registration<br />
:# When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Product / Project name''' || (Replace with text)<br />
|-<br />
| '''Product release version''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
<br />
== YOCTO PROJECT _____Powered (Tier 2 compliance, perhaps the term should be left to the branding document for now?)_____ Acceptance Criteria == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT working group, regardless of organization size || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If any item in the "YOCTO PROJECT _____Powered (Tier 2 compliance, perhaps the term should be left to the branding document for now?)_____ Compliance Recommendations" list is not true, is this documented in the testing report?|| Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
|}<br />
<br />
== YOCTO PROJECT _____Powered (Tier 2 compliance, perhaps the term should be left to the branding document for now?)_____ Compliance Recommendations == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
<br />
== YOCTO PROJECT _____Powered (Tier 2 compliance, perhaps the term should be left to the branding document for now?)_____ Registrar == <br />
<br />
=== Mentor Graphics Embedded Linux ===<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || Mentor Graphics, Inc <br />
|-<br />
| '''Contact Name / Email address''' || Sean Hudson, Sean_Hudson@mentor.com<br />
|-<br />
| '''Product / Project name''' || Mentor Embedded Linux<br />
|-<br />
| '''Product release version''' || v5.0<br />
|-<br />
| '''Registration Date''' || March 27, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT _____Powered (Tier 2 compliance, perhaps the term should be left to the branding document for now?)_____ Acceptance Criteria === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT || Y || bgcolor="" | <br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y || bgcolor="" | <br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y || bgcolor="" | <br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y || bgcolor="" | <br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y || bgcolor="" | <br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y || bgcolor="" | <br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y || bgcolor="" | <br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y || bgcolor="" | <br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y || bgcolor="" | <br />
|-<br />
| If any item in the "YOCTO PROJECT _____Powered (Tier 2 compliance, perhaps the term should be left to the branding document for now?)_____ Compliance Recommendations" list is not true, is this documented in the testing report?|| Y || bgcolor="" | <br />
|-<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT _____Powered (Tier 2 compliance, perhaps the term should be left to the branding document for now?)_____ Compliance Recommendations === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y || bgcolor="" | Based on YOCTO PROJECT v1.1<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y || bgcolor="" | <br />
|}</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Prop&diff=6092Working Draft of Compliance Prop2012-05-30T22:56:12Z<p>Darknighte: Re-format the steps for registration</p>
<hr />
<div>= YOCTO PROJECT Compliance Guidelines =<br />
== Introduction ==<br />
The YOCTO PROJECT compliance program has been established to strengthen the YOCTO PROJECT strategic initiatives by providing guidelines for the use of its branding. This program is intended to provide a minimum level of standardization in order to enable both individual and corporate members to deliver implementations which support the goals of the project and contribute to an ecosystem built around the project. In addition, this program is intended to provide concrete benefits to contributing members by associating a common set of definitions with the use of the YOCTO PROJECT branding. <br />
<br />
Some of the goals of the YOCTO PROJECT that the compliance program is intended to strengthen include:<br />
*Reducing fragmentation in the embedded market by encouraging the development of and collaboration on a common set of tools, standards and practices.<br />
*Ensuring that these tools, standards, and practices are architecturally independent as much as possible.<br />
<br />
Compliance as defined by the YOCTO PROJECT governs the RIGHTS for the usage of the project name, Logo and marks in association with products, marketing materials, and announcements. The YOCTO PROJECT brand guidelines describes how members that follow these compliance guidelines are allowed to use these RIGHTS. (Add document link here – document and guidelines are in development)<br />
<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF RESULTING PRODUCTS OR PROJECTS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
:'''''Note: The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here).''''' <br/><br />
<br />
<br />
== Compliance levels, Compliance Recommendations and Terminology ==<br />
The YOCTO PROJECT compliance program defines steps to register compliance for both individual and corporate members.<br />
<br />
== YOCTO PROJECT Brand Documentation ==<br />
Clear documentation how the brands can be used (palette etc) as well as when they can be used in conjunction with the above are found in the “YOCTO PROJECT Brand Usage Guide.” (add link here)<br />
<br />
= YOCTO PROJECT Aligned = <br />
<br />
=== Registration Steps ===<br />
:To register compliance for use of the YOCTO PROJECT Aligned logo/text:<br />
:# Edit the designated wiki page as follows: <br />
:## copy the text below<br />
:## add a new section for your project / organization<br />
:# Send email to the [mailto:yocto-ab@yoctoproject.org Yocto Advisory Board] requesting registration<br />
:# When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
== YOCTO PROJECT Aligned Registration Template == <br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
== YOCTO PROJECT Aligned Registrar ==<br />
<br />
=== OpenSDR (Consultant) ===<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || OpenSDR (Example) <br />
|-<br />
| '''Contact Name / Email address''' || Philip Balister / philip@balister.org<br />
|-<br />
| '''Registration Date''' || May 20, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y || bgcolor="" | <br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y || bgcolor="" | <br />
|}<br />
<br />
= YOCTO PROJECT Powered = <br />
<br />
=== Registration Steps ===<br />
:To register compliance for use of the YOCTO PROJECT Powered logo/text:<br />
:# Edit the designated wiki page as follows: <br />
:## copy the text below<br />
:## add a new section for your project / organization<br />
:# Send email to the [mailto:yocto-ab@yoctoproject.org Yocto Advisory Board] requesting registration<br />
:# When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Product / Project name''' || (Replace with text)<br />
|-<br />
| '''Product release version''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Acceptance Criteria == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT working group, regardless of organization size || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
|}<br />
<br />
== YOCTO PROJECT Powered Compliance Recommendations == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Registrar == <br />
<br />
=== Mentor Graphics Embedded Linux ===<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || Mentor Graphics, Inc <br />
|-<br />
| '''Contact Name / Email address''' || Sean Hudson, Sean_Hudson@mentor.com<br />
|-<br />
| '''Product / Project name''' || Mentor Embedded Linux<br />
|-<br />
| '''Product release version''' || v5.0<br />
|-<br />
| '''Registration Date''' || March 27, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Acceptance Criteria === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT || Y || bgcolor="" | <br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y || bgcolor="" | <br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y || bgcolor="" | <br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y || bgcolor="" | <br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y || bgcolor="" | <br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y || bgcolor="" | <br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y || bgcolor="" | <br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y || bgcolor="" | <br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y || bgcolor="" | <br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y || bgcolor="" | <br />
|-<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Compliance Recommendations === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y || bgcolor="" | Based on YOCTO PROJECT v1.1<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y || bgcolor="" | <br />
|}</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Prop&diff=6091Working Draft of Compliance Prop2012-05-30T22:45:18Z<p>Darknighte: Tweak terminology section and add reminder to add a link to the brand usage guide.</p>
<hr />
<div>= YOCTO PROJECT Compliance Guidelines =<br />
== Introduction ==<br />
The YOCTO PROJECT compliance program has been established to strengthen the YOCTO PROJECT strategic initiatives by providing guidelines for the use of its branding. This program is intended to provide a minimum level of standardization in order to enable both individual and corporate members to deliver implementations which support the goals of the project and contribute to an ecosystem built around the project. In addition, this program is intended to provide concrete benefits to contributing members by associating a common set of definitions with the use of the YOCTO PROJECT branding. <br />
<br />
Some of the goals of the YOCTO PROJECT that the compliance program is intended to strengthen include:<br />
*Reducing fragmentation in the embedded market by encouraging the development of and collaboration on a common set of tools, standards and practices.<br />
*Ensuring that these tools, standards, and practices are architecturally independent as much as possible.<br />
<br />
Compliance as defined by the YOCTO PROJECT governs the RIGHTS for the usage of the project name, Logo and marks in association with products, marketing materials, and announcements. The YOCTO PROJECT brand guidelines describes how members that follow these compliance guidelines are allowed to use these RIGHTS. (Add document link here – document and guidelines are in development)<br />
<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF RESULTING PRODUCTS OR PROJECTS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
:'''''Note: The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here).''''' <br/><br />
<br />
<br />
== Compliance levels, Compliance Recommendations and Terminology ==<br />
The YOCTO PROJECT compliance program defines steps to register compliance for both individual and corporate members.<br />
<br />
== YOCTO PROJECT Brand Documentation ==<br />
Clear documentation how the brands can be used (palette etc) as well as when they can be used in conjunction with the above are found in the “YOCTO PROJECT Brand Usage Guide.” (add link here)<br />
<br />
= YOCTO PROJECT Aligned = <br />
<br />
Instructions: To register for use of the YOCTO PROJECT Aligned logo/text:<br />
* Edit the wiki page, <br />
* copy the text below and add a new section for your project / organization<br />
* Send mail to yocto-ab@yoctoproject.org requesting registration<br />
* When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
== YOCTO PROJECT Aligned Registration Template == <br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
== YOCTO PROJECT Aligned Registrar ==<br />
<br />
=== OpenSDR (Consultant) ===<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || OpenSDR (Example) <br />
|-<br />
| '''Contact Name / Email address''' || Philip Balister / philip@balister.org<br />
|-<br />
| '''Registration Date''' || May 20, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y || bgcolor="" | <br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y || bgcolor="" | <br />
|}<br />
<br />
= YOCTO PROJECT Powered = <br />
<br />
<br />
Instructions: To register for use of the YOCTO PROJECT Powered logo/text:<br />
* Edit the wiki page, <br />
* copy the text below and add a new section for your project / organization<br />
* Send mail to yocto-ab@yoctoproject.org requesting registration<br />
* When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Product / Project name''' || (Replace with text)<br />
|-<br />
| '''Product release version''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Acceptance Criteria == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT working group, regardless of organization size || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
|}<br />
<br />
== YOCTO PROJECT Powered Compliance Recommendations == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Registrar == <br />
<br />
=== Mentor Graphics Embedded Linux ===<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || Mentor Graphics, Inc <br />
|-<br />
| '''Contact Name / Email address''' || Sean Hudson, Sean_Hudson@mentor.com<br />
|-<br />
| '''Product / Project name''' || Mentor Embedded Linux<br />
|-<br />
| '''Product release version''' || v5.0<br />
|-<br />
| '''Registration Date''' || March 27, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Acceptance Criteria === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT || Y || bgcolor="" | <br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y || bgcolor="" | <br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y || bgcolor="" | <br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y || bgcolor="" | <br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y || bgcolor="" | <br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y || bgcolor="" | <br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y || bgcolor="" | <br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y || bgcolor="" | <br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y || bgcolor="" | <br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y || bgcolor="" | <br />
|-<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Compliance Recommendations === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y || bgcolor="" | Based on YOCTO PROJECT v1.1<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y || bgcolor="" | <br />
|}</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Prop&diff=6090Working Draft of Compliance Prop2012-05-30T22:39:50Z<p>Darknighte: Significant edit of the introduction paragraph to make it more clarify and strengthen intent.</p>
<hr />
<div>= YOCTO PROJECT Compliance Guidelines =<br />
== Introduction ==<br />
The YOCTO PROJECT compliance program has been established to strengthen the YOCTO PROJECT strategic initiatives by providing guidelines for the use of its branding. This program is intended to provide a minimum level of standardization in order to enable both individual and corporate members to deliver implementations which support the goals of the project and contribute to an ecosystem built around the project. In addition, this program is intended to provide concrete benefits to contributing members by associating a common set of definitions with the use of the YOCTO PROJECT branding. <br />
<br />
Some of the goals of the YOCTO PROJECT that the compliance program is intended to strengthen include:<br />
*Reducing fragmentation in the embedded market by encouraging the development of and collaboration on a common set of tools, standards and practices.<br />
*Ensuring that these tools, standards, and practices are architecturally independent as much as possible.<br />
<br />
Compliance as defined by the YOCTO PROJECT governs the RIGHTS for the usage of the project name, Logo and marks in association with products, marketing materials, and announcements. The YOCTO PROJECT brand guidelines describes how members that follow these compliance guidelines are allowed to use these RIGHTS. (Add document link here – document and guidelines are in development)<br />
<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF RESULTING PRODUCTS OR PROJECTS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
:'''''Note: The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here).''''' <br/><br />
<br />
<br />
== Compliance levels, Compliance Recommendations and Terminology ==<br />
The YOCTO PROJECT compliance program defines several steps of compliance to support OSVs, ODMs, Project Contributors, and Application Developers.<br />
<br />
== YOCTO PROJECT Brand Documentation ==<br />
Clear documentation how the brands can be used (palette etc) as well as when they can be used in conjunction with the above are found in the “YOCTO PROJECT Brand Usage Guide.”<br />
<br />
= YOCTO PROJECT Aligned = <br />
<br />
Instructions: To register for use of the YOCTO PROJECT Aligned logo/text:<br />
* Edit the wiki page, <br />
* copy the text below and add a new section for your project / organization<br />
* Send mail to yocto-ab@yoctoproject.org requesting registration<br />
* When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
== YOCTO PROJECT Aligned Registration Template == <br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
== YOCTO PROJECT Aligned Registrar ==<br />
<br />
=== OpenSDR (Consultant) ===<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || OpenSDR (Example) <br />
|-<br />
| '''Contact Name / Email address''' || Philip Balister / philip@balister.org<br />
|-<br />
| '''Registration Date''' || May 20, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y || bgcolor="" | <br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y || bgcolor="" | <br />
|}<br />
<br />
= YOCTO PROJECT Powered = <br />
<br />
<br />
Instructions: To register for use of the YOCTO PROJECT Powered logo/text:<br />
* Edit the wiki page, <br />
* copy the text below and add a new section for your project / organization<br />
* Send mail to yocto-ab@yoctoproject.org requesting registration<br />
* When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Product / Project name''' || (Replace with text)<br />
|-<br />
| '''Product release version''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Acceptance Criteria == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT working group, regardless of organization size || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
|}<br />
<br />
== YOCTO PROJECT Powered Compliance Recommendations == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Registrar == <br />
<br />
=== Mentor Graphics Embedded Linux ===<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || Mentor Graphics, Inc <br />
|-<br />
| '''Contact Name / Email address''' || Sean Hudson, Sean_Hudson@mentor.com<br />
|-<br />
| '''Product / Project name''' || Mentor Embedded Linux<br />
|-<br />
| '''Product release version''' || v5.0<br />
|-<br />
| '''Registration Date''' || March 27, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Acceptance Criteria === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT || Y || bgcolor="" | <br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y || bgcolor="" | <br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y || bgcolor="" | <br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y || bgcolor="" | <br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y || bgcolor="" | <br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y || bgcolor="" | <br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y || bgcolor="" | <br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y || bgcolor="" | <br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y || bgcolor="" | <br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y || bgcolor="" | <br />
|-<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Compliance Recommendations === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y || bgcolor="" | Based on YOCTO PROJECT v1.1<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y || bgcolor="" | <br />
|}</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Proposal&diff=6089Working Draft of Compliance Proposal2012-05-30T22:34:03Z<p>Darknighte: Reverting these and moving them to the old page for now to preserve history. - Undo revision 6081 by Darknighte (talk)</p>
<hr />
<div>This document has been deprecated - the droids you are looking for are at: [ https://wiki.yoctoproject.org/wiki/Working_Draft_of_Compliance_Prop ]<br />
<br />
(This redirect is due to Dave Stewart's jet-lagged blunder. Apologies to Sean Hudson)</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Proposal&diff=6088Working Draft of Compliance Proposal2012-05-30T22:33:31Z<p>Darknighte: Reverting these and moving them to the old page for now to preserve history. - Undo revision 6083 by Darknighte (talk)</p>
<hr />
<div>= YOCTO PROJECT Branding and Compliance =<br />
== Introduction ==<br />
The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here). The YOCTO PROJECT compliance program has been established to support and strengthen the YOCTO PROJECT strategic initiatives and promote by use of its branding.<br />
*To encourage the development of and collaboration on the use of a common set of tools, standards and practices to reduce fragmentation in the embedded market.<br />
*To ensure as much as possible that the tooling for these developments is architecturally independent.<br />
*To provide benefits to membership in the YOCTO PROJECT.<br />
<br />
In other words, the compliance program provides the necessary level of standardizations to allow OSVs, ODMs, Tools and Application developers to deliver implementations which contribute to and support the goals of the project and encourage an ecosystem to build around the YOCTO PROJECT.<br />
<br />
Compliance as defined by the YOCTO PROJECT governs the RIGHTS for the usage of the project name, Logo and marks in association with products, marketing materials, and announcements. The YOCTO PROJECT brand guidelines describes how to use these RIGHTS. (Add document link here – document and guidelines are in development)<br />
<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF RESULTING PRODUCTS OR PROJECTS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
<br />
== Compliance levels, Compliance Recommendations and Terminology ==<br />
The YOCTO PROJECT compliance program defines several steps of compliance to support OSVs, ODMs, Project Contributors, and Application Developers.<br />
<br />
== YOCTO PROJECT Brand Documentation ==<br />
Clear documentation how the brands can be used (palette etc) as well as when they can be used in conjunction with the above are found in the “YOCTO PROJECT Brand Usage Guide.”<br />
<br />
= YOCTO PROJECT Aligned = <br />
<br />
Instructions: To register for use of the YOCTO PROJECT Aligned logo/text:<br />
* Edit the wiki page, <br />
* copy the text below and add a new section for your project / organization<br />
* Send mail to yocto-ab@yoctoproject.org requesting registration<br />
* When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
== YOCTO PROJECT Aligned Registration Template == <br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance version''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
== YOCTO PROJECT Aligned Registrar ==<br />
<br />
=== OpenSDR (Consultant) ===<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || OpenSDR (Example) <br />
|-<br />
| '''Contact Name / Email address''' || Philip Balister / philip@balister.org<br />
|-<br />
| '''Registration Date''' || May 20, 2012<br />
|-<br />
| '''Compliance version''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y || bgcolor="" | <br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y || bgcolor="" | <br />
|}<br />
<br />
= YOCTO PROJECT Powered = <br />
<br />
<br />
Instructions: To register for use of the YOCTO PROJECT Powered logo/text:<br />
* Edit the wiki page, <br />
* copy the text below and add a new section for your project / organization<br />
* Send mail to yocto-ab@yoctoproject.org requesting registration<br />
* When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Product / Project name''' || (Replace with text)<br />
|-<br />
| '''Release version number''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance version''' || Version 1.0<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Acceptance Criteria == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT working group, regardless of organization size || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
|}<br />
<br />
== YOCTO PROJECT Powered Compliance Recommendations == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Registrar == <br />
<br />
=== Mentor Graphics Embedded Linux ===<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || Mentor Graphics, Inc <br />
|-<br />
| '''Contact Name / Email address''' || Sean Hudson, Sean_Hudson@mentor.com<br />
|-<br />
| '''Product / Project name''' || Mentor Embedded Linux<br />
|-<br />
| '''Release version number''' || v3.0<br />
|-<br />
| '''Registration Date''' || May 22, 2012<br />
|-<br />
| '''Compliance version''' || Version 1.0<br />
|}<br />
<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Acceptance Criteria === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT || Y || bgcolor="" | <br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y || bgcolor="" | <br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y || bgcolor="" | <br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y || bgcolor="" | <br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y || bgcolor="" | <br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y || bgcolor="" | <br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y || bgcolor="" | <br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y || bgcolor="" | <br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y || bgcolor="" | <br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y || bgcolor="" | <br />
|-<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Compliance Recommendations === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y || bgcolor="" | Based on YOCTO PROJECT v1.1<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y || bgcolor="" | <br />
|}</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Proposal&diff=6087Working Draft of Compliance Proposal2012-05-30T22:31:55Z<p>Darknighte: Reverting these and moving them to the old page for now to preserve history. - Undo revision 6084 by Darknighte (talk)</p>
<hr />
<div>= YOCTO PROJECT Branding and Compliance =<br />
== Introduction ==<br />
The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here). The YOCTO PROJECT compliance program has been established to support and strengthen the YOCTO PROJECT strategic initiatives and promote by use of its branding.<br />
*To encourage the development of and collaboration on the use of a common set of tools, standards and practices to reduce fragmentation in the embedded market.<br />
*To ensure as much as possible that the tooling for these developments is architecturally independent.<br />
*To provide benefits to membership in the YOCTO PROJECT.<br />
<br />
In other words, the compliance program provides the necessary level of standardizations to allow OSVs, ODMs, Tools and Application developers to deliver implementations which contribute to and support the goals of the project and encourage an ecosystem to build around the YOCTO PROJECT.<br />
<br />
Compliance as defined by the YOCTO PROJECT governs the RIGHTS for the usage of the project name, Logo and marks in association with products, marketing materials, and announcements. The YOCTO PROJECT brand guidelines describes how to use these RIGHTS. (Add document link here – document and guidelines are in development)<br />
<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF RESULTING PRODUCTS OR PROJECTS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
<br />
== Compliance levels, Compliance Recommendations and Terminology ==<br />
The YOCTO PROJECT compliance program defines several steps of compliance to support OSVs, ODMs, Project Contributors, and Application Developers.<br />
<br />
== YOCTO PROJECT Brand Documentation ==<br />
Clear documentation how the brands can be used (palette etc) as well as when they can be used in conjunction with the above are found in the “YOCTO PROJECT Brand Usage Guide.”<br />
<br />
= YOCTO PROJECT Aligned = <br />
<br />
Instructions: To register for use of the YOCTO PROJECT Aligned logo/text:<br />
* Edit the wiki page, <br />
* copy the text below and add a new section for your project / organization<br />
* Send mail to yocto-ab@yoctoproject.org requesting registration<br />
* When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
== YOCTO PROJECT Aligned Registration Template == <br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance version''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
== YOCTO PROJECT Aligned Registrar ==<br />
<br />
=== OpenSDR (Consultant) ===<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || OpenSDR (Example) <br />
|-<br />
| '''Contact Name / Email address''' || Philip Balister / philip@balister.org<br />
|-<br />
| '''Registration Date''' || May 20, 2012<br />
|-<br />
| '''Compliance version''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y || bgcolor="" | <br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y || bgcolor="" | <br />
|}<br />
<br />
= YOCTO PROJECT Powered = <br />
<br />
<br />
Instructions: To register for use of the YOCTO PROJECT Powered logo/text:<br />
* Edit the wiki page, <br />
* copy the text below and add a new section for your project / organization<br />
* Send mail to yocto-ab@yoctoproject.org requesting registration<br />
* When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Product / Project name''' || (Replace with text)<br />
|-<br />
| '''Release version number''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance version''' || Version 1.0<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Acceptance Criteria == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT working group, regardless of organization size || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
|}<br />
<br />
== YOCTO PROJECT Powered Compliance Recommendations == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Registrar == <br />
<br />
=== Mentor Graphics Embedded Linux ===<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || Mentor Graphics, Inc <br />
|-<br />
| '''Contact Name / Email address''' || Sean Hudson, Sean_Hudson@mentor.com<br />
|-<br />
| '''Product / Project name''' || Mentor Embedded Linux<br />
|-<br />
| '''Release product version number''' || v5.0<br />
|-<br />
| '''Registration Date''' || March 27, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Acceptance Criteria === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT || Y || bgcolor="" | <br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y || bgcolor="" | <br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y || bgcolor="" | <br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y || bgcolor="" | <br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y || bgcolor="" | <br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y || bgcolor="" | <br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y || bgcolor="" | <br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y || bgcolor="" | <br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y || bgcolor="" | <br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y || bgcolor="" | <br />
|-<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Compliance Recommendations === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y || bgcolor="" | Based on YOCTO PROJECT v1.1<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y || bgcolor="" | <br />
|}</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Prop&diff=6086Working Draft of Compliance Prop2012-05-30T22:30:43Z<p>Darknighte: Updated Mentor registration and tweaked the headings in the registration sections.</p>
<hr />
<div>= YOCTO PROJECT Branding and Compliance =<br />
== Introduction ==<br />
The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here). The YOCTO PROJECT compliance program has been established to support and strengthen the YOCTO PROJECT strategic initiatives and promote by use of its branding.<br />
*To encourage the development of and collaboration on the use of a common set of tools, standards and practices to reduce fragmentation in the embedded market.<br />
*To ensure as much as possible that the tooling for these developments is architecturally independent.<br />
*To provide benefits to membership in the YOCTO PROJECT.<br />
<br />
In other words, the compliance program provides the necessary level of standardizations to allow OSVs, ODMs, Tools and Application developers to deliver implementations which contribute to and support the goals of the project and encourage an ecosystem to build around the YOCTO PROJECT.<br />
<br />
Compliance as defined by the YOCTO PROJECT governs the RIGHTS for the usage of the project name, Logo and marks in association with products, marketing materials, and announcements. The YOCTO PROJECT brand guidelines describes how to use these RIGHTS. (Add document link here – document and guidelines are in development)<br />
<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF RESULTING PRODUCTS OR PROJECTS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
<br />
== Compliance levels, Compliance Recommendations and Terminology ==<br />
The YOCTO PROJECT compliance program defines several steps of compliance to support OSVs, ODMs, Project Contributors, and Application Developers.<br />
<br />
== YOCTO PROJECT Brand Documentation ==<br />
Clear documentation how the brands can be used (palette etc) as well as when they can be used in conjunction with the above are found in the “YOCTO PROJECT Brand Usage Guide.”<br />
<br />
= YOCTO PROJECT Aligned = <br />
<br />
Instructions: To register for use of the YOCTO PROJECT Aligned logo/text:<br />
* Edit the wiki page, <br />
* copy the text below and add a new section for your project / organization<br />
* Send mail to yocto-ab@yoctoproject.org requesting registration<br />
* When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
== YOCTO PROJECT Aligned Registration Template == <br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
== YOCTO PROJECT Aligned Registrar ==<br />
<br />
=== OpenSDR (Consultant) ===<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || OpenSDR (Example) <br />
|-<br />
| '''Contact Name / Email address''' || Philip Balister / philip@balister.org<br />
|-<br />
| '''Registration Date''' || May 20, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y || bgcolor="" | <br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y || bgcolor="" | <br />
|}<br />
<br />
= YOCTO PROJECT Powered = <br />
<br />
<br />
Instructions: To register for use of the YOCTO PROJECT Powered logo/text:<br />
* Edit the wiki page, <br />
* copy the text below and add a new section for your project / organization<br />
* Send mail to yocto-ab@yoctoproject.org requesting registration<br />
* When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Product / Project name''' || (Replace with text)<br />
|-<br />
| '''Product release version''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Acceptance Criteria == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT working group, regardless of organization size || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
|}<br />
<br />
== YOCTO PROJECT Powered Compliance Recommendations == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Registrar == <br />
<br />
=== Mentor Graphics Embedded Linux ===<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || Mentor Graphics, Inc <br />
|-<br />
| '''Contact Name / Email address''' || Sean Hudson, Sean_Hudson@mentor.com<br />
|-<br />
| '''Product / Project name''' || Mentor Embedded Linux<br />
|-<br />
| '''Product release version''' || v5.0<br />
|-<br />
| '''Registration Date''' || March 27, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Acceptance Criteria === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT || Y || bgcolor="" | <br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y || bgcolor="" | <br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y || bgcolor="" | <br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y || bgcolor="" | <br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y || bgcolor="" | <br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y || bgcolor="" | <br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y || bgcolor="" | <br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y || bgcolor="" | <br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y || bgcolor="" | <br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y || bgcolor="" | <br />
|-<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Compliance Recommendations === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y || bgcolor="" | Based on YOCTO PROJECT v1.1<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y || bgcolor="" | <br />
|}</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Proposal&diff=6084Working Draft of Compliance Proposal2012-05-30T21:21:20Z<p>Darknighte: Tweaked the headings in the registration sections.</p>
<hr />
<div>= YOCTO PROJECT Branding and Compliance =<br />
== Introduction ==<br />
The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here). The YOCTO PROJECT compliance program has been established to support and strengthen the YOCTO PROJECT strategic initiatives and promote by use of its branding.<br />
*To encourage the development of and collaboration on the use of a common set of tools, standards and practices to reduce fragmentation in the embedded market.<br />
*To ensure as much as possible that the tooling for these developments is architecturally independent.<br />
*To provide benefits to membership in the YOCTO PROJECT.<br />
<br />
In other words, the compliance program provides the necessary level of standardizations to allow OSVs, ODMs, Tools and Application developers to deliver implementations which contribute to and support the goals of the project and encourage an ecosystem to build around the YOCTO PROJECT.<br />
<br />
Compliance as defined by the YOCTO PROJECT governs the RIGHTS for the usage of the project name, Logo and marks in association with products, marketing materials, and announcements. The YOCTO PROJECT brand guidelines describes how to use these RIGHTS. (Add document link here – document and guidelines are in development)<br />
<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF RESULTING PRODUCTS OR PROJECTS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
<br />
== Compliance levels, Compliance Recommendations and Terminology ==<br />
The YOCTO PROJECT compliance program defines several steps of compliance to support OSVs, ODMs, Project Contributors, and Application Developers.<br />
<br />
== YOCTO PROJECT Brand Documentation ==<br />
Clear documentation how the brands can be used (palette etc) as well as when they can be used in conjunction with the above are found in the “YOCTO PROJECT Brand Usage Guide.”<br />
<br />
= YOCTO PROJECT Aligned = <br />
<br />
Instructions: To register for use of the YOCTO PROJECT Aligned logo/text:<br />
* Edit the wiki page, <br />
* copy the text below and add a new section for your project / organization<br />
* Send mail to yocto-ab@yoctoproject.org requesting registration<br />
* When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
== YOCTO PROJECT Aligned Registration Template == <br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
== YOCTO PROJECT Aligned Registrar ==<br />
<br />
=== OpenSDR (Consultant) ===<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || OpenSDR (Example) <br />
|-<br />
| '''Contact Name / Email address''' || Philip Balister / philip@balister.org<br />
|-<br />
| '''Registration Date''' || May 20, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y || bgcolor="" | <br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y || bgcolor="" | <br />
|}<br />
<br />
= YOCTO PROJECT Powered = <br />
<br />
<br />
Instructions: To register for use of the YOCTO PROJECT Powered logo/text:<br />
* Edit the wiki page, <br />
* copy the text below and add a new section for your project / organization<br />
* Send mail to yocto-ab@yoctoproject.org requesting registration<br />
* When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Product / Project name''' || (Replace with text)<br />
|-<br />
| '''Product release version''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Acceptance Criteria == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT working group, regardless of organization size || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
|}<br />
<br />
== YOCTO PROJECT Powered Compliance Recommendations == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Registrar == <br />
<br />
=== Mentor Graphics Embedded Linux ===<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || Mentor Graphics, Inc <br />
|-<br />
| '''Contact Name / Email address''' || Sean Hudson, Sean_Hudson@mentor.com<br />
|-<br />
| '''Product / Project name''' || Mentor Embedded Linux<br />
|-<br />
| '''Product release version''' || v5.0<br />
|-<br />
| '''Registration Date''' || March 27, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Acceptance Criteria === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT || Y || bgcolor="" | <br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y || bgcolor="" | <br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y || bgcolor="" | <br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y || bgcolor="" | <br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y || bgcolor="" | <br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y || bgcolor="" | <br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y || bgcolor="" | <br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y || bgcolor="" | <br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y || bgcolor="" | <br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y || bgcolor="" | <br />
|-<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Compliance Recommendations === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y || bgcolor="" | Based on YOCTO PROJECT v1.1<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y || bgcolor="" | <br />
|}</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Proposal&diff=6083Working Draft of Compliance Proposal2012-05-30T21:14:29Z<p>Darknighte: Updated registration.</p>
<hr />
<div>= YOCTO PROJECT Branding and Compliance =<br />
== Introduction ==<br />
The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here). The YOCTO PROJECT compliance program has been established to support and strengthen the YOCTO PROJECT strategic initiatives and promote by use of its branding.<br />
*To encourage the development of and collaboration on the use of a common set of tools, standards and practices to reduce fragmentation in the embedded market.<br />
*To ensure as much as possible that the tooling for these developments is architecturally independent.<br />
*To provide benefits to membership in the YOCTO PROJECT.<br />
<br />
In other words, the compliance program provides the necessary level of standardizations to allow OSVs, ODMs, Tools and Application developers to deliver implementations which contribute to and support the goals of the project and encourage an ecosystem to build around the YOCTO PROJECT.<br />
<br />
Compliance as defined by the YOCTO PROJECT governs the RIGHTS for the usage of the project name, Logo and marks in association with products, marketing materials, and announcements. The YOCTO PROJECT brand guidelines describes how to use these RIGHTS. (Add document link here – document and guidelines are in development)<br />
<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF RESULTING PRODUCTS OR PROJECTS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
<br />
== Compliance levels, Compliance Recommendations and Terminology ==<br />
The YOCTO PROJECT compliance program defines several steps of compliance to support OSVs, ODMs, Project Contributors, and Application Developers.<br />
<br />
== YOCTO PROJECT Brand Documentation ==<br />
Clear documentation how the brands can be used (palette etc) as well as when they can be used in conjunction with the above are found in the “YOCTO PROJECT Brand Usage Guide.”<br />
<br />
= YOCTO PROJECT Aligned = <br />
<br />
Instructions: To register for use of the YOCTO PROJECT Aligned logo/text:<br />
* Edit the wiki page, <br />
* copy the text below and add a new section for your project / organization<br />
* Send mail to yocto-ab@yoctoproject.org requesting registration<br />
* When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
== YOCTO PROJECT Aligned Registration Template == <br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance version''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
== YOCTO PROJECT Aligned Registrar ==<br />
<br />
=== OpenSDR (Consultant) ===<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || OpenSDR (Example) <br />
|-<br />
| '''Contact Name / Email address''' || Philip Balister / philip@balister.org<br />
|-<br />
| '''Registration Date''' || May 20, 2012<br />
|-<br />
| '''Compliance version''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y || bgcolor="" | <br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y || bgcolor="" | <br />
|}<br />
<br />
= YOCTO PROJECT Powered = <br />
<br />
<br />
Instructions: To register for use of the YOCTO PROJECT Powered logo/text:<br />
* Edit the wiki page, <br />
* copy the text below and add a new section for your project / organization<br />
* Send mail to yocto-ab@yoctoproject.org requesting registration<br />
* When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Product / Project name''' || (Replace with text)<br />
|-<br />
| '''Release version number''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance version''' || Version 1.0<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Acceptance Criteria == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT working group, regardless of organization size || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
|}<br />
<br />
== YOCTO PROJECT Powered Compliance Recommendations == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Registrar == <br />
<br />
=== Mentor Graphics Embedded Linux ===<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || Mentor Graphics, Inc <br />
|-<br />
| '''Contact Name / Email address''' || Sean Hudson, Sean_Hudson@mentor.com<br />
|-<br />
| '''Product / Project name''' || Mentor Embedded Linux<br />
|-<br />
| '''Release product version number''' || v5.0<br />
|-<br />
| '''Registration Date''' || March 27, 2012<br />
|-<br />
| '''Compliance specification revision''' || Version 1.0<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Acceptance Criteria === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT || Y || bgcolor="" | <br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y || bgcolor="" | <br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y || bgcolor="" | <br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y || bgcolor="" | <br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y || bgcolor="" | <br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y || bgcolor="" | <br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y || bgcolor="" | <br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y || bgcolor="" | <br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y || bgcolor="" | <br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y || bgcolor="" | <br />
|-<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Compliance Recommendations === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y || bgcolor="" | Based on YOCTO PROJECT v1.1<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y || bgcolor="" | <br />
|}</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Prop&diff=6082Working Draft of Compliance Prop2012-05-30T21:07:10Z<p>Darknighte: Redirected to the original page without the truncated name</p>
<hr />
<div>#REDIRECT [[Working Draft of Compliance Proposal]]</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Proposal&diff=6081Working Draft of Compliance Proposal2012-05-30T21:05:55Z<p>Darknighte: Moved content from the truncated site to this one.</p>
<hr />
<div>= YOCTO PROJECT Branding and Compliance =<br />
== Introduction ==<br />
The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here). The YOCTO PROJECT compliance program has been established to support and strengthen the YOCTO PROJECT strategic initiatives and promote by use of its branding.<br />
*To encourage the development of and collaboration on the use of a common set of tools, standards and practices to reduce fragmentation in the embedded market.<br />
*To ensure as much as possible that the tooling for these developments is architecturally independent.<br />
*To provide benefits to membership in the YOCTO PROJECT.<br />
<br />
In other words, the compliance program provides the necessary level of standardizations to allow OSVs, ODMs, Tools and Application developers to deliver implementations which contribute to and support the goals of the project and encourage an ecosystem to build around the YOCTO PROJECT.<br />
<br />
Compliance as defined by the YOCTO PROJECT governs the RIGHTS for the usage of the project name, Logo and marks in association with products, marketing materials, and announcements. The YOCTO PROJECT brand guidelines describes how to use these RIGHTS. (Add document link here – document and guidelines are in development)<br />
<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF RESULTING PRODUCTS OR PROJECTS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
<br />
== Compliance levels, Compliance Recommendations and Terminology ==<br />
The YOCTO PROJECT compliance program defines several steps of compliance to support OSVs, ODMs, Project Contributors, and Application Developers.<br />
<br />
== YOCTO PROJECT Brand Documentation ==<br />
Clear documentation how the brands can be used (palette etc) as well as when they can be used in conjunction with the above are found in the “YOCTO PROJECT Brand Usage Guide.”<br />
<br />
= YOCTO PROJECT Aligned = <br />
<br />
Instructions: To register for use of the YOCTO PROJECT Aligned logo/text:<br />
* Edit the wiki page, <br />
* copy the text below and add a new section for your project / organization<br />
* Send mail to yocto-ab@yoctoproject.org requesting registration<br />
* When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
== YOCTO PROJECT Aligned Registration Template == <br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance version''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
== YOCTO PROJECT Aligned Registrar ==<br />
<br />
=== OpenSDR (Consultant) ===<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || OpenSDR (Example) <br />
|-<br />
| '''Contact Name / Email address''' || Philip Balister / philip@balister.org<br />
|-<br />
| '''Registration Date''' || May 20, 2012<br />
|-<br />
| '''Compliance version''' || Version 1.0<br />
|}<br />
<br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Committed to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other YOCTO PROJECT layers || Y || bgcolor="" | <br />
|- <br />
| Aim for compatibility and interoperability between different metadata layers. || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit, small business (up to 80 employees). || Y || bgcolor="" | <br />
|}<br />
<br />
= YOCTO PROJECT Powered = <br />
<br />
<br />
Instructions: To register for use of the YOCTO PROJECT Powered logo/text:<br />
* Edit the wiki page, <br />
* copy the text below and add a new section for your project / organization<br />
* Send mail to yocto-ab@yoctoproject.org requesting registration<br />
* When you have received email acknowledgement, you may use the logo / text treatment<br />
<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || (Replace with text) <br />
|-<br />
| '''Contact Name / Email address''' || (Replace with text)<br />
|-<br />
| '''Product / Project name''' || (Replace with text)<br />
|-<br />
| '''Release version number''' || (Replace with text)<br />
|-<br />
| '''Registration Date''' || (Replace with text)<br />
|-<br />
| '''Compliance version''' || Version 1.0<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Acceptance Criteria == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y or N || bgcolor="" | (Delete if "Y")<br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT working group, regardless of organization size || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
|}<br />
<br />
== YOCTO PROJECT Powered Compliance Recommendations == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y or N || bgcolor="" | (Delete if "Y")<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y or N || bgcolor="" | (Delete if "Y")<br />
|}<br />
<br />
<br />
== YOCTO PROJECT Powered Registrar == <br />
<br />
=== Mentor Graphics Embedded Linux ===<br />
<br />
{| border="1" {{table}} <br />
| '''Organization / Project name''' || Mentor Graphics, Inc <br />
|-<br />
| '''Contact Name / Email address''' || Sean Hudson, Sean_Hudson@mentor.com<br />
|-<br />
| '''Product / Project name''' || Mentor Embedded Linux<br />
|-<br />
| '''Release version number''' || v3.0<br />
|-<br />
| '''Registration Date''' || May 22, 2012<br />
|-<br />
| '''Compliance version''' || Version 1.0<br />
|}<br />
<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Acceptance Criteria === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Working towards and supporting the aims and objectives of the YOCTO PROJECT. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. || Y || bgcolor="" | <br />
|- <br />
| Promoting the OpenEmbedded Architecture, layer model and BSP format || Y || bgcolor="" | <br />
|- <br />
| Making visible contributions in the OpenEmbedded and component projects of the YOCTO PROJECT || Y || bgcolor="" | <br />
|- <br />
| Be an open source project, non-profit or member of the YOCTO PROJECT || Y || bgcolor="" | <br />
|-<br />
| If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? || Y || bgcolor="" | <br />
|-<br />
| If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components? || Y || bgcolor="" | <br />
|-<br />
| Have all patches applied to BitBake and OpenEmbedded-Core (if present) been submitted to the open source community? || Y || bgcolor="" | <br />
|-<br />
| Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements? || Y || bgcolor="" | <br />
|-<br />
| Do all layers build without errors against OpenEmbedded-Core with only the dependencies/requirements listed in their README file? || Y || bgcolor="" | <br />
|-<br />
| '''(For BSPs)''' Does the layer follow the format defined in the [http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html YOCTO PROJECT Board Support Package (BSP) Developers Guide]? || Y || bgcolor="" | <br />
|-<br />
| Are hardware support, configuration (distro) policy and recipe metadata separated into different layers which do not depend on each other? || Y || bgcolor="" | <br />
|-<br />
| A test report document is included of which combinations of layers, recipes and machines have been tested. || Y || bgcolor="" | <br />
|-<br />
| If any item in the "YOCTO PROJECT Powered Compliance Recommendations" list is not true, is this documented in the testing report?|| Y || bgcolor="" | <br />
|-<br />
|}<br />
<br />
=== Mentor Graphics YOCTO PROJECT Powered Compliance Recommendations === <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Criteria''' || ! scope="col" bgcolor="grey" | '''Yes/No''' || ! scope="col" bgcolor="grey" | '''Explanation (if N or N/A)'''<br />
|- <br />
| Linux kernels are either based around LTSI kernel versions or a YOCTO PROJECT kernel version || Y || bgcolor="" | Based on YOCTO PROJECT v1.1<br />
|-<br />
| Everything builds successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard? || Y || bgcolor="" | <br />
|}</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Talk:Working_Draft_of_Compliance_Proposal&diff=5973Talk:Working Draft of Compliance Proposal2012-05-17T17:31:48Z<p>Darknighte: Invitation for comments</p>
<hr />
<div>To the interested, here is a draft of a proposal from the advocacy group to be presented to the Advisory Board when complete. Please look it over and provide feedback!</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Compliancy_Discussion&diff=5972Compliancy Discussion2012-05-17T17:18:06Z<p>Darknighte: Made link more visible</p>
<hr />
<div>== Working Draft of Compliance Proposal ==<br />
The current working draft can be found '''[[ Working Draft of Compliance Proposal|here ]]'''<br />
<br />
== Yocto Project Aligned ==<br />
<br />
To use this term in connection with any product or project or in marketing materials you need to:<br />
<br />
* Be working towards and supporting the aims and objectives of the Yocto Project. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks.<br />
* Be promoting the OpenEmbedded Architecture, layer model and BSP format<br />
* Be making visible contributions in the OpenEmbedded and component projects of the Yocto Project <br />
* Aim for compatibility and interoperability between different metadata layers.<br />
* Be an open source project, charity organisation, small business or consultancy or member of the project. Larger companies (80+ employees) may also meet this criteria but are strongly recommended to be members of the project.<br />
<br />
== Yocto Project Powered ==<br />
<br />
To use this term in connection with any product or project or in marketing materials you need to:<br />
<br />
* Be able to satisfy all the criteria for "Yocto Project Aligned"<br />
* Be an open source project, charity organisation or a member of the Yocto Project<br />
* Be able to answer 'Yes' to all the criteria in the compliancy checklist.<br />
<br />
== Yocto Project Powered Compliancy Checklist ==<br />
<br />
* If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? (Y/N)<br />
* If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components?<br />
* Have all patches applied to BitBake and OpenEmbedded-Core (if present) been discussed with the open source community? (Y/N)<br />
* Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes for it and what dependencies or version requirements it has? (Y/N)<br />
* Do all layers present build cleanly against OpenEmbedded-Core with only the dependencies/requirements listed in their documentation? (Y/N)<br />
* Does any hardware support follow the format defined in the Yocto Project Board Support Package (BSP) Developers Guide? (Y/N)<br />
* Are hardware support, configuration (distro) policy and recipe meatdata clearly separated into different layers which do not depend on each other? (Y/N)<br />
* Is clear documentation of which combinations of layers, recipes and machines were tested included? (Y/N)<br />
* Where any item in the "Yocto Project Powered Compliancy Recommendations" list is not true, is this documented in the testing documentation? (Y/N)<br />
<br />
== Yocto Project Powered Compliancy Recommendations ==<br />
<br />
* Linux kernels are either based around LTSI kernel versions or are more recent that the last LTSI release<br />
* Everything should build successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard?</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Compliancy_Discussion&diff=5971Compliancy Discussion2012-05-17T17:17:18Z<p>Darknighte: Added link to draft of compliance proposal</p>
<hr />
<div>== Working Draft of Compliance Proposal ==<br />
The current working draft can be found [[ Working Draft of Compliance Proposal|here ]]<br />
<br />
== Yocto Project Aligned ==<br />
<br />
To use this term in connection with any product or project or in marketing materials you need to:<br />
<br />
* Be working towards and supporting the aims and objectives of the Yocto Project. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks.<br />
* Be promoting the OpenEmbedded Architecture, layer model and BSP format<br />
* Be making visible contributions in the OpenEmbedded and component projects of the Yocto Project <br />
* Aim for compatibility and interoperability between different metadata layers.<br />
* Be an open source project, charity organisation, small business or consultancy or member of the project. Larger companies (80+ employees) may also meet this criteria but are strongly recommended to be members of the project.<br />
<br />
== Yocto Project Powered ==<br />
<br />
To use this term in connection with any product or project or in marketing materials you need to:<br />
<br />
* Be able to satisfy all the criteria for "Yocto Project Aligned"<br />
* Be an open source project, charity organisation or a member of the Yocto Project<br />
* Be able to answer 'Yes' to all the criteria in the compliancy checklist.<br />
<br />
== Yocto Project Powered Compliancy Checklist ==<br />
<br />
* If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? (Y/N)<br />
* If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only contain those components?<br />
* Have all patches applied to BitBake and OpenEmbedded-Core (if present) been discussed with the open source community? (Y/N)<br />
* Do all layers contain a README file which details the origin of the layer, its maintainer, where to submit changes for it and what dependencies or version requirements it has? (Y/N)<br />
* Do all layers present build cleanly against OpenEmbedded-Core with only the dependencies/requirements listed in their documentation? (Y/N)<br />
* Does any hardware support follow the format defined in the Yocto Project Board Support Package (BSP) Developers Guide? (Y/N)<br />
* Are hardware support, configuration (distro) policy and recipe meatdata clearly separated into different layers which do not depend on each other? (Y/N)<br />
* Is clear documentation of which combinations of layers, recipes and machines were tested included? (Y/N)<br />
* Where any item in the "Yocto Project Powered Compliancy Recommendations" list is not true, is this documented in the testing documentation? (Y/N)<br />
<br />
== Yocto Project Powered Compliancy Recommendations ==<br />
<br />
* Linux kernels are either based around LTSI kernel versions or are more recent that the last LTSI release<br />
* Everything should build successfully with the standard toolchain from OE-Core where the architecture is one supported by OE-Core as standard?</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Proposal&diff=5970Working Draft of Proposal2012-05-17T17:16:33Z<p>Darknighte: moved Working Draft of Proposal to Working Draft of Compliance Proposal: Make it more clear what this is a draft of.</p>
<hr />
<div>#REDIRECT [[Working Draft of Compliance Proposal]]</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Proposal&diff=5969Working Draft of Compliance Proposal2012-05-17T17:16:33Z<p>Darknighte: moved Working Draft of Proposal to Working Draft of Compliance Proposal: Make it more clear what this is a draft of.</p>
<hr />
<div>== Introduction ==<br />
The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here). The YOCTO PROJECT compliance program has been established to support and strengthen the YOCTO PROJECT strategic initiatives and promote by use of its branding.<br />
*To encourage the development of and collaboration on the use of a common set of tools, standards and practices to reduce fragmentation in the embedded market.<br />
*To ensure as much as possible that the tooling for these developments is architecturally independent.<br />
*To provide benefits to membership in the YOCTOPROJECT.<br />
<br />
In other words, the compliance program provides the necessary level of standardizations to allow OSVs, ODMs, Tools and Application developers to deliver implementations which contribute to and support the goals of the project.<br />
<br />
Compliance as defined by the YOCTO PROJECT governs the use of the project name, Logo and marks in association with products, marketing materials, and announcements. Use of the YOCTO PROJECT name, logo and marks is governed by the YOCTO PROJECT brand guidelines. (Add document link here – document and guidelines are in development)<br />
<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF THE RESULTING DISTRIBUTIONS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
== Compliance levels, Compliance Recommendations and Terminology ==<br />
The Yocto Project compliance program defines several steps of compliance to support OSVs, ODMs, Project Contributors, and Application Developers.<br />
<br />
=== Yocto Project Aligned ===<br />
<br />
This covers use cases by those unlikely to be actively developing the project itself, companies which are supportive of the goals, but not influential in the governance of the project from a business or technology point of view. To use this term in connection with any commercial product or project or marketing materials you need to: <br />
*Be working towards and supporting the aims and objectives of the Yocto Project. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. <br />
*Be promoting the OpenEmbedded Architecture, layer model and BSP format over other systems <br />
*Be making visible contributions in the Open Embedded and component projects of the Yocto Project, or using a pre-defined recipe to build your own distribution<br />
*Aim for compatibility and interoperability between different metadata layers. <br />
*Be an open source project, charity organization or small business or consultancy. Larger companies (80+ employees) should be members of the project. <br />
<br />
=== Yocto Project Powered ===<br />
<br />
Suggested new term: Registered<br />
<br />
This is for companies who are deeply involved in the project, contributing and guiding. To use this term in connection with any product or project or in marketing materials you need to: <br />
*Be able to satisfy all the criteria for "Yocto Project Aligned" (except company size/type) <br />
*Be an open source project, charity organization or a member of the Yocto Project <br />
*Be making visible contributions in the Open Embedded and component projects of the Yocto Project, or using a pre-defined recipe to build their own distribution<br />
*Be able to answer 'Yes' to all the required criteria in the compliancy checklist. <br />
*Document the required criteria in the test documentation? Information to be supplied by the technology team.<br />
*Have considered the recommendations and documented those recommendations in the test documentation regarding what was actually tested. <br />
<br />
== Yocto Project Powered Compliancy Checklist ==<br />
* Does the project have clearly identifiable components that correspond to BitBake and OpenEmbedded-Core if these are present? (Y/N) <br />
* Have all patches applied to BitBake and OpenEmbedded-Core components been discussed with the open source community? (Y/N) <br />
* Do all layers build against OE-Core? (Y/N) <br />
* Does any hardware support follow the format defined in the Yocto Project Board Support Package (BSP) Developers Guide? (Y/N) <br />
* Are hardware support, configuration (distribution) policy and recipe metadata clearly separated into different layers which can be used separately? (Y/N) <br />
* Are the combinations of layers which were tested clearly documented? (Y/N) <br />
<br />
== Yocto Project Powered Compliance Recommendations ==<br />
It is recommended that users meet the following, but this is not required to be Yocto Project Powered, it is just a recommendation: <br />
* (O) Are Linux kernels either based around LTSI kernel versions or more recent that the last LTSI release? (Y/N) <br />
* (O) Does all code basically work with the standard tool chain from OE-Core (it may be un-optimized) where the architecture is one supported by OE-Core as standard? (Y/N) <br />
<br />
== Yocto Project Brand Documentation ==<br />
Clearly document how the brands can be used (palette etc) as well as when they can be used in conjunction with the above. (in progress)<br />
<br />
== Registration Process ==<br />
*A registration area will be available on the Yocto Project WIKI where companies interested in publically using the YOCTO PROJECT brand or wording associating a product or intent with the YOCTO PROJECT must register the following information:<br />
:#Company<br />
:#Product Name<br />
:#How the YOCTO PROJECT logo or text association is being used.<br />
:#Timeframe<br />
*Those found not in compliance will be WHAT?</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Proposal&diff=5968Working Draft of Compliance Proposal2012-05-17T17:12:14Z<p>Darknighte: Initial import of the draft sent by Tracey @ Intel</p>
<hr />
<div>== Introduction ==<br />
The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here). The YOCTO PROJECT compliance program has been established to support and strengthen the YOCTO PROJECT strategic initiatives and promote by use of its branding.<br />
*To encourage the development of and collaboration on the use of a common set of tools, standards and practices to reduce fragmentation in the embedded market.<br />
*To ensure as much as possible that the tooling for these developments is architecturally independent.<br />
*To provide benefits to membership in the YOCTOPROJECT.<br />
<br />
In other words, the compliance program provides the necessary level of standardizations to allow OSVs, ODMs, Tools and Application developers to deliver implementations which contribute to and support the goals of the project.<br />
<br />
Compliance as defined by the YOCTO PROJECT governs the use of the project name, Logo and marks in association with products, marketing materials, and announcements. Use of the YOCTO PROJECT name, logo and marks is governed by the YOCTO PROJECT brand guidelines. (Add document link here – document and guidelines are in development)<br />
<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF THE RESULTING DISTRIBUTIONS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
== Compliance levels, Compliance Recommendations and Terminology ==<br />
The Yocto Project compliance program defines several steps of compliance to support OSVs, ODMs, Project Contributors, and Application Developers.<br />
<br />
=== Yocto Project Aligned ===<br />
<br />
This covers use cases by those unlikely to be actively developing the project itself, companies which are supportive of the goals, but not influential in the governance of the project from a business or technology point of view. To use this term in connection with any commercial product or project or marketing materials you need to: <br />
*Be working towards and supporting the aims and objectives of the Yocto Project. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. <br />
*Be promoting the OpenEmbedded Architecture, layer model and BSP format over other systems <br />
*Be making visible contributions in the Open Embedded and component projects of the Yocto Project, or using a pre-defined recipe to build your own distribution<br />
*Aim for compatibility and interoperability between different metadata layers. <br />
*Be an open source project, charity organization or small business or consultancy. Larger companies (80+ employees) should be members of the project. <br />
<br />
=== Yocto Project Powered ===<br />
<br />
Suggested new term: Registered<br />
<br />
This is for companies who are deeply involved in the project, contributing and guiding. To use this term in connection with any product or project or in marketing materials you need to: <br />
*Be able to satisfy all the criteria for "Yocto Project Aligned" (except company size/type) <br />
*Be an open source project, charity organization or a member of the Yocto Project <br />
*Be making visible contributions in the Open Embedded and component projects of the Yocto Project, or using a pre-defined recipe to build their own distribution<br />
*Be able to answer 'Yes' to all the required criteria in the compliancy checklist. <br />
*Document the required criteria in the test documentation? Information to be supplied by the technology team.<br />
*Have considered the recommendations and documented those recommendations in the test documentation regarding what was actually tested. <br />
<br />
== Yocto Project Powered Compliancy Checklist ==<br />
* Does the project have clearly identifiable components that correspond to BitBake and OpenEmbedded-Core if these are present? (Y/N) <br />
* Have all patches applied to BitBake and OpenEmbedded-Core components been discussed with the open source community? (Y/N) <br />
* Do all layers build against OE-Core? (Y/N) <br />
* Does any hardware support follow the format defined in the Yocto Project Board Support Package (BSP) Developers Guide? (Y/N) <br />
* Are hardware support, configuration (distribution) policy and recipe metadata clearly separated into different layers which can be used separately? (Y/N) <br />
* Are the combinations of layers which were tested clearly documented? (Y/N) <br />
<br />
== Yocto Project Powered Compliance Recommendations ==<br />
It is recommended that users meet the following, but this is not required to be Yocto Project Powered, it is just a recommendation: <br />
* (O) Are Linux kernels either based around LTSI kernel versions or more recent that the last LTSI release? (Y/N) <br />
* (O) Does all code basically work with the standard tool chain from OE-Core (it may be un-optimized) where the architecture is one supported by OE-Core as standard? (Y/N) <br />
<br />
== Yocto Project Brand Documentation ==<br />
Clearly document how the brands can be used (palette etc) as well as when they can be used in conjunction with the above. (in progress)<br />
<br />
== Registration Process ==<br />
*A registration area will be available on the Yocto Project WIKI where companies interested in publically using the YOCTO PROJECT brand or wording associating a product or intent with the YOCTO PROJECT must register the following information:<br />
:#Company<br />
:#Product Name<br />
:#How the YOCTO PROJECT logo or text association is being used.<br />
:#Timeframe<br />
*Those found not in compliance will be WHAT?</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Working_Draft_of_Compliance_Proposal&diff=5966Working Draft of Compliance Proposal2012-05-17T17:00:53Z<p>Darknighte: Created page with "1. Introduction The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here). The YOCTO PROJECT compliance program has been established to support ..."</p>
<hr />
<div>1. Introduction<br />
The YOCTO PROJECT adheres to the guidelines set up by the Linux Foundation (add link here). The YOCTO PROJECT compliance program has been established to support and strengthen the YOCTO PROJECT strategic initiatives and promote by use of its branding.<br />
• To encourage the development of and collaboration on the use of a common set of tools, standards and practices to reduce fragmentation in the embedded market.<br />
• To ensure as much as possible that the tooling for these developments is architecturally independent.<br />
• To provide benefits to membership in the YOCTOPROJECT.<br />
In other words, the compliance program provides the necessary level of standardizations to allow OSVs, ODMs, Tools and Application developers to deliver implementations which contribute to and support the goals of the project.<br />
Compliance as defined by the YOCTO PROJECT governs the use of the project name, Logo and marks in association with products, marketing materials, and announcements. Use of the YOCTO PROJECT name, logo and marks is governed by the YOCTO PROJECT brand guidelines. (Add document link here – document and guidelines are in development)<br />
As with Linux, COMPLIANCE AFFECTS THE COMMERCIAL USE OF THE RESULTING DISTRIBUTIONS CREATED BY THE YOCTO PROJECT. PERSONAL USE CASES ARE NOT COVERED. <br />
<br />
2. Compliance levels, Compliance Recommendations and Terminology<br />
<br />
The Yocto Project compliance program defines several steps of compliance to support OSVs, ODMs, Project Contributors, and Application Developers.<br />
<br />
Term Description<br />
Yocto Project Aligned<br />
<br />
This covers use cases by those unlikely to be actively developing the project itself, companies which are supportive of the goals, but not influential in the governance of the project from a business or technology point of view. To use this term in connection with any commercial product or project or marketing materials you need to: <br />
• Be working towards and supporting the aims and objectives of the Yocto Project. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. <br />
• Be promoting the OpenEmbedded Architecture, layer model and BSP format over other systems <br />
• Be making visible contributions in the Open Embedded and component projects of the Yocto Project, or using a pre-defined recipe to build your own distribution<br />
• Aim for compatibility and interoperability between different metadata layers. <br />
• Be an open source project, charity organization or small business or consultancy. Larger companies (80+ employees) should be members of the project. <br />
<br />
Yocto Project Powered<br />
<br />
Suggested new term: Registered<br />
<br />
This is for companies who are deeply involved in the project, contributing and guiding. To use this term in connection with any product or project or in marketing materials you need to: <br />
• Be able to satisfy all the criteria for "Yocto Project Aligned" (except company size/type) <br />
• Be an open source project, charity organization or a member of the Yocto Project <br />
• Be making visible contributions in the Open Embedded and component projects of the Yocto Project, or using a pre-defined recipe to build their own distribution<br />
• Be able to answer 'Yes' to all the required criteria in the compliancy checklist. <br />
• Document the required criteria in the test documentation? Information to be supplied by the technology team.<br />
• Have considered the recommendations and documented those recommendations in the test documentation regarding what was actually tested. <br />
<br />
Yocto Project Powered Compliancy Checklist • Does the project have clearly identifiable components that correspond to BitBake and OpenEmbedded-Core if these are present? (Y/N) <br />
• Have all patches applied to BitBake and OpenEmbedded-Core components been discussed with the open source community? (Y/N) <br />
• Do all layers build against OE-Core? (Y/N) <br />
• Does any hardware support follow the format defined in the Yocto Project Board Support Package (BSP) Developers Guide? (Y/N) <br />
• Are hardware support, configuration (distribution) policy and recipe metadata clearly separated into different layers which can be used separately? (Y/N) <br />
• Are the combinations of layers which were tested clearly documented? (Y/N) <br />
<br />
Yocto Project Powered Compliance Recommendations It is recommended that users meet the following, but this is not required to be Yocto Project Powered, it is just a recommendation: <br />
• (O) Are Linux kernels either based around LTSI kernel versions or more recent that the last LTSI release? (Y/N) <br />
• (O) Does all code basically work with the standard tool chain from OE-Core (it may be un-optimized) where the architecture is one supported by OE-Core as standard? (Y/N) <br />
<br />
Yocto Project Brand Documentation Clearly document how the brands can be used (palette etc) as well as when they can be used in conjunction with the above. (in progress)<br />
<br />
3. Registration Process<br />
<br />
• A registration area will be available on the Yocto Project WIKI where companies interested in publically using the YOCTO PROJECT brand or wording associating a product or intent with the YOCTO PROJECT must register the following information:<br />
o Company<br />
o Product Name<br />
o How the YOCTO PROJECT logo or text association is being used.<br />
o Timeframe<br />
• Those found not in compliance will be WHAT?</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=BSP_Summit&diff=5131BSP Summit2012-03-29T20:01:00Z<p>Darknighte: /* Live Video/Audio Conference Information */</p>
<hr />
<div>The Yocto Project BSP Summit will be held April 2, 2012 at Mentor Graphics headquarters in Fremont, CA. This summit, which happens the day before the Linux Collaboration Summit in San Francisco, will focus on the creation of BSPs based on OpenEmbedded Core and usable by the Yocto Project. In addition to presentations, the summit will include working sessions to provide developers with the opportunity to refine the common definition of BSP layers and work collaboratively on their own BSP layers. To that end, developers are encouraged to bring development boards to work on during the summit. To continue the momentum for those also attending the Collaboration Summit, the Yocto Project will host an all-day working meeting give to work on their BSPs with community members.<br />
<br />
NOTE - Although this event is timed to coincide with the [https://events.linuxfoundation.org/events/collaboration-summit Collaboration Summit] in San Francisco, please remember that the Collaboration Summit is a completely separate event. If you want to attend Collaboration Summit, you need to [https://events.linuxfoundation.org/events/collaboration-summit/request-an-invitation request an invitation from Linux Foundation].<br />
<br />
= Agenda =<br />
<br />
08:00 - 09:00 -- Social/continental breakfast provided by Mentor Graphics<br /><br />
09:00 - 09:15 -- Welcome and introduction (Sean Hudson, Mentor Graphics)<br /><br />
09:15 - 10:15 -- Current state of Yocto Project BSP definition (Tom Zanussi, Intel)<br /><br />
10:15 - 10:30 -- Break<br /><br />
10:30 - 11:30 -- Working with meta-ti (Denys Dmitriyenko, TI)<br /><br />
11:30 - 12:30 -- Lunch provided by Mentor Graphics & hardware setup<br /><br />
12:30 - 13:00 -- BSP strategy (Bruce Ashfield, Wind River)<br /><br />
13:00 - 14:30 -- Yocto Project BSP open discussion (moderator: Sean Hudson)<br /><br />
14:30 - 17:00 -- Working sessions<br /><br />
17:00 - 18:30 -- Beer & pizza provided by Mentor Graphics<br />
<br />
= Live Video/Audio Conference Information =<br />
In order to allow for additional participation from the community at the BSP Summit,<br />
Mentor Graphics will be providing a live video conference, a WebEx session, and recording<br />
the stream for later viewing. Details can be found below. Please feel free to share<br />
this information with colleagues that are unable to attend in person.<br />
<br />
Live video conference details<br />
----<br />
Conference ID: 101<br />
<br />
Video participants will need to call into the Video Conference Bridge using one of the methods below.<br />
Once connected to our Video Conference Bridge, please enter the Conference ID followed by the # sign.<br />
IP Address: 192.94.38.249<br />
Video Address (H.323 or SIP): video@mentor.com<br />
<br />
NOTES:<br />
The video conference will not connect until the call is active. However, it will become live ~15 minutes early.<br />
A video conference setup will be required to connect. A free client can be found at [https://www.ekiga.net ekiga.net]<br />
<br />
Webex information:<br />
Meeting Number: 758 201 571<br />
Meeting Password: Yocto<br />
<br />
= Venue =<br />
<br />
The event will take place 8am-5pm at Mentor Graphics headquarters in Fremont:<br />
<br />
46871 Bayside Parkway<br /><br />
Fremont, CA 94538<br /><br />
Tel: (510) 354.7400<br />
<br />
= Local Hotels =<br />
<br />
Mentor has recommended the following hotels:<br />
<br />
'''Marriott''' (Nice, 1 Mile away, $134/night)<br />46100 Landing Parkway, Fremont, CA 94538<br />(510) 413-3700 <br />
<br />
'''Courtyard Fremont Silicon Valley''' (Budget, .5 Miles, $84/night breakfast included)<br /><br />
47000 Lakeview Boulevard, Fremont, CA 94538<br /><br />
(510) 656-1800 (510) 656-2441 (Fax) <br />
<br />
If you plan to take public transportation, there is a BART terminal in Fremont about 15 minutes away from the Mentor Graphics office. The nearest CalTrain station is either Santa Clara or downtown San Jose, both about 20 miles away, but you can transfer to Santa Clara Light Rail blue line up to the Great Mall station in Milpitas, which is only about 8 minutes from Mentor.<br />
<br />
= Carpooling =<br />
<br />
For those who have an extra seat in their car as well as those who wish to ride with others, please [mailto:jeffrey.osier-mixon@intel.com let me know] and I will try to match up the latter with the former.</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=BSP_Summit&diff=5125BSP Summit2012-03-28T16:32:37Z<p>Darknighte: /* Live Feed */</p>
<hr />
<div>The Yocto Project BSP Summit will be held April 2, 2012 at Mentor Graphics headquarters in Fremont, CA. This summit, which happens the day before the Linux Collaboration Summit in San Francisco, will focus on the creation of BSPs based on OpenEmbedded Core and usable by the Yocto Project. In addition to presentations, the summit will include working sessions to provide developers with the opportunity to refine the common definition of BSP layers and work collaboratively on their own BSP layers. To that end, developers are encouraged to bring development boards to work on during the summit. To continue the momentum for those also attending the Collaboration Summit, the Yocto Project will host an all-day working meeting give to work on their BSPs with community members.<br />
<br />
NOTE - Although this event is timed to coincide with the [https://events.linuxfoundation.org/events/collaboration-summit Collaboration Summit] in San Francisco, please remember that the Collaboration Summit is a completely separate event. If you want to attend Collaboration Summit, you need to [https://events.linuxfoundation.org/events/collaboration-summit/request-an-invitation request an invitation from Linux Foundation].<br />
<br />
= Agenda =<br />
<br />
08:00 - 09:00 -- Social/continental breakfast provided by Mentor Graphics<br /><br />
09:00 - 09:15 -- Welcome and introduction (Sean Hudson, Mentor Graphics)<br /><br />
09:15 - 10:15 -- Current state of Yocto Project BSP definition (Tom Zanussi, Intel)<br /><br />
10:15 - 10:30 -- Break<br /><br />
10:30 - 11:30 -- Working with meta-ti (Denys Dmitriyenko, TI)<br /><br />
11:30 - 12:30 -- Lunch provided by Mentor Graphics & hardware setup<br /><br />
12:30 - 13:00 -- BSP strategy (Bruce Ashfield, Wind River)<br /><br />
13:00 - 14:30 -- Yocto Project BSP open discussion (moderator: Sean Hudson)<br /><br />
14:30 - 17:00 -- Working sessions<br /><br />
17:00 - 18:30 -- Beer & pizza provided by Mentor Graphics<br />
<br />
= Live Video/Audio Conference Information =<br />
In order to allow for additional participation from the community at the BSP Summit,<br />
Mentor Graphics will be providing a live video conference, a WebEx session, and recording<br />
the stream for later viewing. Details can be found below. Please feel free to share<br />
this information with colleagues that are unable to attend in person.<br />
<br />
Live video conference details<br />
----<br />
Conference ID: 101<br />
<br />
Video participants will need to call into the Video Conference Bridge using one of the methods below.<br />
Once connected to our Video Conference Bridge, please enter the Conference ID followed by the # sign.<br />
IP Address: 192.94.38.249<br />
Video Address (H.323 or SIP): video@mentor.com<br />
<br />
NOTES:<br />
The video conference will not connect until the call is active. However, it will connect 15 minutes early.<br />
<br />
Webex information:<br />
Meeting Number: 758 201 571<br />
Meeting Password: Yocto<br />
<br />
= Venue =<br />
<br />
The event will take place 8am-5pm at Mentor Graphics headquarters in Fremont:<br />
<br />
46871 Bayside Parkway<br /><br />
Fremont, CA 94538<br /><br />
Tel: (510) 354.7400<br />
<br />
= Local Hotels =<br />
<br />
Mentor has recommended the following hotels:<br />
<br />
'''Marriott''' (Nice, 1 Mile away, $134/night)<br />46100 Landing Parkway, Fremont, CA 94538<br />(510) 413-3700 <br />
<br />
'''Courtyard Fremont Silicon Valley''' (Budget, .5 Miles, $84/night breakfast included)<br /><br />
47000 Lakeview Boulevard, Fremont, CA 94538<br /><br />
(510) 656-1800 (510) 656-2441 (Fax) <br />
<br />
If you plan to take public transportation, there is a BART terminal in Fremont about 15 minutes away from the Mentor Graphics office. The nearest CalTrain station is either Santa Clara or downtown San Jose, both about 20 miles away, but you can transfer to Santa Clara Light Rail blue line up to the Great Mall station in Milpitas, which is only about 8 minutes from Mentor.<br />
<br />
= Carpooling =<br />
<br />
For those who have an extra seat in their car as well as those who wish to ride with others, please [mailto:jeffrey.osier-mixon@intel.com let me know] and I will try to match up the latter with the former.</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=BSP_Summit&diff=5085BSP Summit2012-03-21T17:35:13Z<p>Darknighte: /* Live Feed */</p>
<hr />
<div>The Yocto Project BSP Summit will be held April 2, 2012 at Mentor Graphics headquarters in Fremont, CA. This summit, which happens the day before the Linux Collaboration Summit in San Francisco, will focus on the creation of BSPs based on OpenEmbedded Core and usable by the Yocto Project. In addition to presentations, the summit will include working sessions to provide developers with the opportunity to refine the common definition of BSP layers and work collaboratively on their own BSP layers. To that end, developers are encouraged to bring development boards to work on during the summit. To continue the momentum for those also attending the Collaboration Summit, the Yocto Project will host an all-day working meeting give to work on their BSPs with community members.<br />
<br />
NOTE - Although this event is timed to coincide with the [https://events.linuxfoundation.org/events/collaboration-summit Collaboration Summit] in San Francisco, please remember that the Collaboration Summit is a completely separate event. If you want to attend Collaboration Summit, you need to [https://events.linuxfoundation.org/events/collaboration-summit/request-an-invitation request an invitation from Linux Foundation].<br />
<br />
= Agenda =<br />
<br />
08:00 - 09:00 -- Social/continental breakfast<br /><br />
09:00 - 09:15 -- Welcome and introduction (Sean Hudson, Mentor Graphics)<br /><br />
09:15 - 10:15 -- Current state of Yocto Project BSP definition (Tom Zanussi, Intel)<br /><br />
10:15 - 10:30 -- Break<br /><br />
10:30 - 11:30 -- Working with meta-ti (Denys Dmitriyenko, TI)<br /><br />
11:30 - 13:00 -- Lunch & hardware setup<br /><br />
13:00 - 14:30 -- Yocto Project BSP open discussion (moderator: Sean Hudson)<br /><br />
14:30 - 17:00 -- Working sessions<br />
<br />
= Live Feed =<br />
<br />
A live feed is being worked on and may be provided, possibly with some opportunities for remote participation.<br />
<br />
More information on the feed will be posted here when it is available.<br />
<br />
= Venue =<br />
<br />
The event will take place 8am-5pm at Mentor Graphics headquarters in Fremont:<br />
<br />
46871 Bayside Parkway<br /><br />
Fremont, CA 94538<br /><br />
Tel: (510) 354.7400<br />
<br />
= Local Hotels =<br />
<br />
Mentor has recommended the following hotels:<br />
<br />
'''Marriott''' (Nice, 1 Mile away, $134/night)<br />46100 Landing Parkway, Fremont, CA 94538<br />(510) 413-3700 <br />
<br />
'''Courtyard Fremont Silicon Valley''' (Budget, .5 Miles, $84/night breakfast included)<br /><br />
47000 Lakeview Boulevard, Fremont, CA 94538<br /><br />
(510) 656-1800 (510) 656-2441 (Fax) <br />
<br />
If you plan to take public transportation, there is a BART terminal in Fremont about 15 minutes away from the Mentor Graphics office. The nearest CalTrain station is either Santa Clara or downtown San Jose, both about 20 miles away, but you can transfer to Santa Clara Light Rail blue line up to the Great Mall station in Milpitas, which is only about 8 minutes from Mentor.<br />
<br />
= Carpooling =<br />
<br />
For those who have an extra seat in their car as well as those who wish to ride with others, please [mailto:jeffrey.osier-mixon@intel.com let me know] and I will try to match up the latter with the former.</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Project_v1.2_Status&diff=3979Yocto Project v1.2 Status2011-11-08T16:19:40Z<p>Darknighte: /* Milestone 1 */</p>
<hr />
<div>Yocto Project 1.2 release Status<br />
<br />
= Feature/Task Board = <br />
{|border="1" {{table}}<br />
| align="center" style="background:#f0f0f0;"|'''Design'''<br />
| align="center" style="background:#f0f0f0;"|'''Design Review'''<br />
| align="center" style="background:#f0f0f0;"|'''Development'''<br />
| align="center" style="background:#f0f0f0;"|'''Patch Review'''<br />
| align="center" style="background:#f0f0f0;"|'''Testing'''<br />
| align="center" style="background:#f0f0f0;"|'''Done'''<br />
|-<br />
| 1634 [http://bugzilla.yoctoproject.org/show_bug.cgi?id=1634], Bruce, 1||1644[http://bugzilla.yoctoproject.org/show_bug.cgi?id=1644], Bruce, 1||1564[http://bugzilla.yoctoproject.org/show_bug.cgi?id=1564], Dongxiao, 1||||||<br />
|-<br />
| 1580[http://bugzilla.yoctoproject.org/show_bug.cgi?id=1580], Jessica, 1||||1008[http://bugzilla.yoctoproject.org/show_bug.cgi?id=1008], ScottG, 1||||||<br />
|-<br />
| 1582[http://bugzilla.yoctoproject.org/show_bug.cgi?id=1582], Joshua, 1||||||||||<br />
|-<br />
| 1603[http://bugzilla.yoctoproject.org/show_bug.cgi?id=1603], Kai, 1||||||||||<br />
|-<br />
| 1589[http://bugzilla.yoctoproject.org/show_bug.cgi?id=1589], Robert, 1||||||||||<br />
|-<br />
| 1598[http://bugzilla.yoctoproject.org/show_bug.cgi?id=1598], Paul, 1||||||||||<br />
|-<br />
| 1567[http://bugzilla.yoctoproject.org/show_bug.cgi?id=1567], Yi, 1||||||||||<br />
|}<br />
<br />
Note: Each column lists "Feature #, Owner, # of weeks in this stage".<br />
<br />
= Feature/Task Effort Burndown Chart =<br />
[[File: feature-burndown12.png]]<br />
<br />
= Yocto Project 1.2 Release Criteria = <br />
== Milestone 1 == <br />
{| border="1" {{table}} <br />
| ! scope="col" bgcolor="grey" | '''Release Criteria''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Target''' || ! scope="col" bgcolor="grey" | '''Milestone 1 Status'''<br />
|- <br />
| Functional Completion || All P1 features are completed. || bgcolor="" | See https://wiki.yoctoproject.org/wiki/Yocto_1.2_Schedule for details.<br />
|- <br />
| Build and Release (Yocto) || All completed features can be built with no errors. || bgcolor="" | <br />
|- <br />
| Build and Release (BSPs) || Core and meta-intel BSPs can be built with no errors. || bgcolor="" | <br />
|- <br />
| Open Bugs || All bugs have been dispositioned. High issues have been fixed. || bgcolor="" | [http://bugzilla.yoctoproject.org/buglist.cgi?query_format=advanced&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_status=NEW&version=1.2] - new bugs for 1.2.<br>[http://bugzilla.yoctoproject.org/buglist.cgi?bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&columnlist=bug_severity%2Cpriority%2Ctarget_milestone%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc&priority=High&query_format=advanced&target_milestone=---&target_milestone=1.2%20M1&target_milestone=1.2%20M2&target_milestone=1.2%20M3&target_milestone=1.2%20M4&query_based_on= HIGH priority bugs] - high bugs for 1.2 <br>See trend chart at https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.<br />
|- <br />
| Functional Tests || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="" | https://wiki.yoctoproject.org/wiki/Yocto_1.2_Milestone_Test_Report<br />
|- <br />
| Distros Tested || Fedora, Ubuntu, Opensuse || bgcolor="" | Fedora 15, Ubuntu 11.04, Opensuse 11.4<br />
|- <br />
| BSP Testing || 100% of planned tests are executed and results are logged in bugzilla. || bgcolor="" | https://wiki.yoctoproject.org/wiki/Yocto_1.2_Milestone_Test_Report<br />
|- <br />
| Documentation || All scheduled docs are complete || bgcolor="" | <br />
|- <br />
| Build Performance || None || bgcolor="" | N/A<br />
|- <br />
| Upstream Commits || Have upstream status updated on 90% of patches (so that we can have a status update) || bgcolor="" | Complete<br />
|- <br />
| Marketing Deliverables || None || bgcolor="" | N/A<br />
|- <br />
| Publication || Yocto 1.2, Milestone 1 release is announced || bgcolor="" |<br />
|}</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Governance/AdvisoryBoardMinutes&diff=3278Governance/AdvisoryBoardMinutes2011-08-29T15:59:26Z<p>Darknighte: </p>
<hr />
<div>This page links to minutes from all Yocto Project Advisory Board meetings.<br />
<br />
* [[Governance/AdvisoryBoardMinutes/2011-Mar-29|29 March, 2011]] (call)<br />
* [[Governance/AdvisoryBoardMinutes/2011-Apr-07|07 April, 2011]] (F2F)</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Main_Page&diff=3252Main Page2011-08-23T15:34:53Z<p>Darknighte: </p>
<hr />
<div>== Welcome to the Yocto Project Wiki! ==<br />
* [[Planning and Governance]]<br />
* [[Community Guidelines]]<br />
* [[Processes and Activities]]<br />
** [[YoctoCalendar]]<br />
* [[Projects]]<br />
* [[Yocto Interest Groups]]<br />
* [[FAQ]]<br />
* [[Contributors]]<br />
* [[Training]]<br />
<br />
== Other resources ==<br />
* [http://yoctoproject.org Yocto Project Front Page]</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Infrastructure/Administrative_Interest_Group&diff=1568Infrastructure/Administrative Interest Group2011-05-03T19:27:40Z<p>Darknighte: /* Welcome to the Yocto Project's Infrastructure/Administrative Interest Group */</p>
<hr />
<div>== Welcome to the Yocto Project's Infrastructure/Administrative Interest Group ==<br />
<br />
This group is intended to share common wisdom around the maintenance and administration of the infrastructure that supports the Yocto project.<br />
Also, it is a place to share deployment tips and advice with other members of the community.<br />
<br />
<br />
Want to help out? Sign up for the [https://lists.yoctoproject.org/listinfo/yocto-infrastructure mailing list]</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Project:Community_Portal&diff=1567Yocto Project:Community Portal2011-05-03T19:23:13Z<p>Darknighte: </p>
<hr />
<div>== Welcome to the Yocto Community Portal! ==<br />
* [[IRC Bug Day logs]]<br />
* [[Yocto Buildbot Autobuilder Discussions]]<br />
* [[Yocto Release Matrix]]<br />
* [[Yocto Interest Groups]]</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Help:Contents&diff=1566Help:Contents2011-05-03T19:22:09Z<p>Darknighte: Redirected page to Using the Wiki</p>
<hr />
<div>#REDIRECT [[Using_the_Wiki]]</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Infrastructure/Administrative_Interest_Group&diff=1565Infrastructure/Administrative Interest Group2011-05-03T19:18:22Z<p>Darknighte: Created page with '== Welcome to the Yocto Project's Infrastructure/Administrative Interest Group == This group is intended to share common wisdom around the maintenance and administration of the …'</p>
<hr />
<div>== Welcome to the Yocto Project's Infrastructure/Administrative Interest Group ==<br />
<br />
This group is intended to share common wisdom around the maintenance and administration of the infrastructure that supports the Yocto project.<br />
Also, it is a place to share deployment tips and advice with other members of the community.</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Interest_Groups&diff=1564Yocto Interest Groups2011-05-03T19:09:56Z<p>Darknighte: Created page with '== Welcome to Yocto Project Interest Groups! == These are Bird of a Feather groups that further a specific interest, related to the Yocto project. * [[Infrastructure/Administra…'</p>
<hr />
<div>== Welcome to Yocto Project Interest Groups! ==<br />
<br />
These are Bird of a Feather groups that further a specific interest, related to the Yocto project.<br />
<br />
* [[Infrastructure/Administrative Interest Group]]</div>Darknightehttps://wiki.yoctoproject.org/wiki/index.php?title=Main_Page&diff=1563Main Page2011-05-03T19:05:24Z<p>Darknighte: </p>
<hr />
<div>== Welcome to the Yocto Project Wiki! ==<br />
* [[Planning and Governance]]<br />
* [[Community Guidelines]]<br />
* [[Processes and Activities]]<br />
* [[Projects]]<br />
* [[Yocto Interest Groups]]<br />
* [[FAQ]]<br />
* [[Contributors]]</div>Darknighte