Bug 1945

Summary: Developer's Guide needs to give guidance about making source available
Product: [Documentation] Quick Start Reporter: Dave Stewart <david.c.stewart>
Component: quick-startAssignee: Beth Flanagan <elizabeth.flanagan>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: alexandru.c.georgescu, bluelightning, elizabeth.flanagan, jessica.zhang, poky.doc.watcher, poky.watcher, richard.purdie, sgw, srifenbark
Version: 1.2   
Target Milestone: 1.6   
Hardware: All   
OS: Multiple   
Whiteboard: 21 March 2013 - NEEDINFO
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Done (doc changes complete)

Description Dave Stewart 2012-01-31 21:36:17 UTC
We have talked for some time about a chapter in the Dev Guide giving advice for how to "finish" a product using Yocto. For example, we talked about shutting down any security back doors like the TCE agent. But Beth reminded me that we need to tell people how to stay in compliance with open source licenses. Usually it just meant that they need to make their DL_DIR available on request (I think). This needs to be documented so we can promote best practices.
Comment 1 Scott Rifenbark 2012-04-24 23:03:32 UTC
Accepted.  Also, the Component needs to be "Developers Guide" when we have that set up under "Documentation."
Comment 2 Scott Rifenbark 2013-03-20 20:27:43 UTC
We did a bit of work in the "Using the Yocto Project in a Team Environment" section in the dev-manual.  I took information from Richard and integrated it into that section.  It seems like what Dave is wanting here could also be folded into that section.  I don't have the information to proceed with it so I am requesting further information.

Scott

http://www.yoctoproject.org/docs/1.4/dev-manual/dev-manual.html#usingpoky-changes-collaborate
Comment 3 Richard Purdie 2013-05-01 15:58:59 UTC
Beth: Can you please help Scott find some information about "polishing" images for release and also some kind of compliance checklist. This follows naturally into documenting some of the release process which we need to do too. If there is wiki information Scott can use, please share the links.

Scott: This makes a logical follow on from that section we created, I think it needs to follow it rather than join it though.
Comment 4 Scott Rifenbark 2013-05-06 12:37:44 UTC
Richard, 

Okay - I will follow the section with the information once it becomes available from Beth.

Scott
Comment 5 Scott Rifenbark 2013-05-21 19:30:50 UTC
Adding Paul to CC list.

this bug requires a load of information.  Please someone supply some baseline information for me.

Scott
Comment 6 Paul Eggleton 2014-01-16 16:39:17 UTC
For a couple of releases we've had the following manual section:

http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#maintaining-open-source-license-compliance-during-your-products-lifecycle

As far as I can see it should address the main part of this request.

The security documentation comment is covered under bug 5482, so with that I'm marking this as fixed.
Comment 7 Alexandru Georgescu 2014-07-30 08:42:01 UTC
marking as verified as per above comments.