kellpossible / kellpossible/blog
Write an article about Open Source policy
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
## Guides
+ https://opensource.guide/legal/
## Policy Examples
### Rackspace
+ [Overview of their policy](https://processmechanics.com/2015/07/22/a-model-ip-and-open-source-contribution-policy/)
+ [Template IP and Open Source Agreement](https://docs.google.com/document/d/1-IzRinOw1Zu-NrhjGjJVqVldRuuiLdOiofrWW9QB_5E/edit)
### Google
+ [Google's open source policy](https://opensource.google/docs/)
### Linux Foundation
+ [Approval Request Form for the use of Open Source](https://github.com/todogroup/policies/blob/master/linuxfoundation/lf_compliance_approval.pdf)
+ [Open Source Policy](https://github.com/todogroup/policies/blob/master/linuxfoundation/lf_compliance_generic_policy.pdf)
### Joyent
+ [Joyent's Policy Overview](https://github.com/joyent/rfd/blob/master/rfd/0164/README.md)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the linked Open Source Guide and the Rackspace, Google, Linux Foundation, and Joyent policy examples. The article should explain open source policy and draw on these references, but the issue does not identify the destination file, article format, or additional acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100