1 / 81

Managing Open Source in Your Supply Chain

In his presentation at the O'Reilly Open Source Conference, Andy Wilson, Chief Open Source Compliance Officer at Intel, discusses the complexities of managing open source software in supply chains. He emphasizes the importance of minimizing friction caused by proprietary standards and undocumented hardware. Open source can be advantageous, but it comes with rules that must be followed to avoid costly mistakes. Wilson highlights the necessity of clear communication of information throughout the software development process to ensure compliance and maintain efficiency.

hashim
Télécharger la présentation

Managing Open Source in Your Supply Chain

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Managing Open Source in Your Supply Chain O’Reilly Open Source Conference Andy Wilson Chief open source compliance officer, Intel andrew.wilson@intel.com 22-July-2010

  2. agenda

  3. intro “the big picture” things that make a difference lots of time for discussion

  4. IANAL, TINLA, personal intro

  5. the SW world is not flat…

  6. … the SW world is systolic

  7. in a systolic economy, vendors provide direct, immediate value-add

  8. and pass through to the next stage

  9. the product cycle is continuous

  10. pipelines are deep

  11. development is highly parallel

  12. Each processing node runs on its own pulse

  13. as “wavefronts” of code flow through

  14. lub dub

  15. The beat goes on.

  16. The enemy of a systolic world is friction.

  17. proprietary standards, undocumented HW, restricted software cause friction

  18. Open standards, documented HW, open source reduce friction

  19. open source is not zero friction

  20. it is not public domain

  21. open source has rules

  22. not following the rules is a mistake

  23. mistakes can clog your pipeline

  24. mistakes can even land you in court

  25. don’t make mistakes

  26. to avoid mistakes

  27. it is in your interest to pass good information downstream

  28. information loss is friction

  29. friction is bad

  30. getting good information from upstream can be hard

  31. be clear with your downstream you need all their information

  32. (and a “no open source at all” policy from your vendors is so 1995)

  33. You need confidence in your vendor’s information

  34. you need to know where SW came from and how it is licensed

  35. you need downstream info in an understandable format

  36. and you need to document what you add in an understandable format

  37. pass on all your vendors’ information plus your information

  38. you will be asked for the info at some point

  39. if you can’t find the info, it’s a fire drill. fire drills are bad

  40. recap

  41. think systolically

  42. know exactly what you take in

  43. know exactly what you add

  44. always pass your information through; destroying information causes friction

  45. things that can help (1): have a GPL policy

  46. GPL is a high friction open source license

  47. not a criticism

  48. just a fact

  49. GPL is long

  50. it has never been litigated in the US

More Related