(→Conclusion) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | [[ar:ورقة_بحثية:_نشر_الشفرة_البرمجية_المصدرية_للبرمجيات_الحرة_مفتوحة_المصدر | ورقة_بحثية:_نشر_الشفرة_البرمجية_المصدرية_للبرمجيات_الحرة_مفتوحة_المصدر]] | ||
This paper discusses the aspect of publishing source code in meeting license obligations. It presents a sample process to follow when making source code available and offers checklists that user can use prior and post source code publication. | This paper discusses the aspect of publishing source code in meeting license obligations. It presents a sample process to follow when making source code available and offers checklists that user can use prior and post source code publication. | ||
| Line 12: | Line 13: | ||
This paper provides a practical discussion on the process of making source code available as part of meeting FOSS license obligations. | This paper provides a practical discussion on the process of making source code available as part of meeting FOSS license obligations. | ||
| − | + | In addition, this paper also showed that the implementation of open source compliance processes can vary from company to company based on a number of factors: the underlying product development process into which compliance must fit, the size and nature of the code base, number of products turned out, the amount of externally supplied code, size and organizational structure of the company, and so on. | |
But the core elements of compliance usually remain the same: | But the core elements of compliance usually remain the same: | ||
Latest revision as of 12:50, 4 July 2016
This paper discusses the aspect of publishing source code in meeting license obligations. It presents a sample process to follow when making source code available and offers checklists that user can use prior and post source code publication.
White paper main segment
Topics covered by this paper include the following:
- How to decide on source code’s publication model?
- Preparing source code packages
- How to create and fulfill a pre-publication Checklist
- Publishing source code process
- How to create and fulfill post-publication Checklist
Conclusion
This paper provides a practical discussion on the process of making source code available as part of meeting FOSS license obligations.
In addition, this paper also showed that the implementation of open source compliance processes can vary from company to company based on a number of factors: the underlying product development process into which compliance must fit, the size and nature of the code base, number of products turned out, the amount of externally supplied code, size and organizational structure of the company, and so on.
But the core elements of compliance usually remain the same:
- Identifying the open source in the code base
- Reviewing and approving its use
- Satisfying obligations
Full White Paper
Publishing Source Code for FOSS Compliance - By The Linux Foundation