From 8c2bc7a96ad51b2c388512d25082f70187b256ff Mon Sep 17 00:00:00 2001 From: massonpj Date: Wed, 17 Jun 2015 12:37:47 -0400 Subject: [PATCH] Add OSI license requriements MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Open source licenses are only licenses that comply with the Open Source Definition — in brief, they allow software to be freely used, modified, and shared. To be approved by the Open Source Initiative (also known as the OSI), a license must go through the Open Source Initiative's license review process and as such is the industry and globally recognized standard for identifying open source software. The plays should explicitly require that software carry an OSI Approved Open Source License to ensure software freedom, meet the expectations of those involved with the open source community and ensure the benefits open source software and licenses afford. There are many organizations which use the label "open source" but develop their own licenses which do not comply with the OSD and limit the software freedom guaranteed by the OSI and OSD. --- _plays/05.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_plays/05.md b/_plays/05.md index 43d84fef..2a936de8 100644 --- a/_plays/05.md +++ b/_plays/05.md @@ -3,7 +3,7 @@ id: 5 title: Structure budgets and contracts to support delivery --- -To improve our chances of success when contracting out development work, we need to work with experienced budgeting and contracting officers. In cases where we use third parties to help build a service, a well-defined contract can facilitate good development practices like conducting a research and prototyping phase, refining product requirements as the service is built, evaluating open source alternatives, ensuring frequent delivery milestones, and allowing the flexibility to purchase cloud computing resources. +To improve our chances of success when contracting out development work, we need to work with experienced budgeting and contracting officers. In cases where we use third parties to help build a service, a well-defined contract can facilitate good development practices like conducting a research and prototyping phase, refining product requirements as the service is built, evaluating alternatives distributed with an [Open Source Initiative Approved Open Source License](http://opensource.org/licenses), ensuring frequent delivery milestones, and allowing the flexibility to purchase cloud computing resources. [The TechFAR Handbook](https://playbook.cio.gov/techfar/) provides a detailed explanation of the flexibilities in the Federal Acquisition Regulation (FAR) that can help agencies implement this play. @@ -12,7 +12,7 @@ To improve our chances of success when contracting out development work, we need 2. Contract is structured to request frequent deliverables, not multi-month milestones 3. Contract is structured to hold vendors accountable to deliverables 4. Contract gives the government delivery team enough flexibility to adjust feature prioritization and delivery schedule as the project evolves -5. Contract ensures open source solutions are evaluated when technology choices are made +5. Contract ensures solutions distributed with an [Open Source Initiative Approved Open Source License](http://opensource.org/licenses), are evaluated when technology choices are made 6. Contract specifies that software and data generated by third parties remains under our control, and can be reused and released to the public as appropriate and in accordance with the law 7. Contract allows us to use tools, services, and hosting from vendors with a variety of pricing models, including fixed fees and variable models like “pay-for-what-you-use” services 8. Contract specifies a warranty period where defects uncovered by the public are addressed by the vendor at no additional cost to the government @@ -21,4 +21,4 @@ To improve our chances of success when contracting out development work, we need #### key questions - What is the scope of the project? What are the key deliverables? - What are the milestones? How frequent are they? -- What are the performance metrics defined in the contract (e.g., response time, system uptime, time period to address priority issues)? \ No newline at end of file +- What are the performance metrics defined in the contract (e.g., response time, system uptime, time period to address priority issues)?