| Summary: | Reference material for how a user creates a build that meets GPL obligations given a reference BSP, standard rootfs/kernel...etc. | ||
|---|---|---|---|
| Product: | [Documentation] Reference | Reporter: | Mark Morton <mark.morton> |
| Component: | handbook | Assignee: | Michael Opdenacker <michael.opdenacker> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | bluelightning, dvhart, elizabeth.flanagan, joshuagloe, poky.doc.watcher, poky.watcher, randy.macleod, richard.purdie, sgw, srifenbark |
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Mark Morton
2013-04-03 20:30:38 UTC
This is super old and probably involves me at some point. Putting this comment in to refresh it. Scott Need to know who would be the expert on this and then I need information from that person. I will add Paul to the already pretty big list. Hopefully someone can tell me who to work with. Scott Scott, this was assigned to me as I've been tasked with collating the right information. It's going to take some research for me to do that but I'll be sure to update in here when I've got something you can start to work with. Joshua, You are probably even further away from stuff like this right? Scott I'm afraid so, I can't see my having time to work on this. I think it would be an exceptionally valuable piece of documentation, but there's the danger of appearing to provide legal advice. Added Richard to CC list. Hoping to find an expert for information. Scott Mark Morton, I've taken ownership of this so maybe we can work on it together as a medium priority for 2.8. Thanks Randy Michael, I'd be happy to talk about this with you.. ping me on irc: vmeson. All things considered, I don't think we shouldn't guide people through specific cases. Explaining license compliance in general looks better, and it's what https://docs.yoctoproject.org/dev-manual/licenses.html#maintaining-open-source-license-compliance-during-your-product-s-lifecycle is trying to do. Anything missing in this section? I find it quite exhaustive. Closing this bug. Don't hesitate to comment and re-open if you disagree. |