Permalink
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
573 lines (286 sloc) 12.2 KB
  1. Where is your company or organization on its open source journey? (Check all that apply) Consuming open source code in products or services
  • Contributing to upstream open source projects

  • Influencing open source projects via leadership or maintainer roles

  • Initiating or releasing open source projects

  • Not involved in open source

  • Don’t know

  1. How many people work for your company or organization?
  • Self-employed or not working

  • 2-50

  • 51-250

  • 251-1,000

  • 1,000-10,000

  • 10,000+

  • Don't know

  1. How often does your company do the following activities?
  • Never Rarely Sometimes Frequently Don't know

  • Contribute code upstream

  • Use open source code for noncommercial or internal reasons

  • Use open source code in commercial products

  • Recruit and hire developers to work on open source projects

  • Train developers to contribute to open source projects

  • Create its own open source projects

  • Attend and speak at open source events or conferences

  1. Does your company have a formal policy governing use and contribution to open source projects in the following areas?

  2. Does your company have an open source program (either formal or informal) or management initiative? *

  • Yes

  • No, but planning one

  • No

  • Yes No Don't know

  • Use of open source code in products (dependencies)

  • Releasing open source code or projects

  • List of acceptable licenses

  • Contributing upstream to open source projects

  • Sponsoring open source projects, events or foundations

  1. What are the primary responsibilities of the open source program? (Check all that apply)
  • Owning and overseeing the execution of open source strategy

  • Clearly communicating the open source strategy within and outside the company

  • Facilitating the effective use of open source in commercial products and services

  • Ensuring high-quality and frequent releases of code to open source communities

  • Engaging with developer communities so the company contributes back to other projects effectively

  • Fostering an open source culture within an organization

  • Maintaining open source license compliance reviews and oversight

  • Launching new open source projects

  • Selecting and/or setting up infrastructure and tooling for open source use, contribution and creation

  • Developing and delivering open source training, resources and documentation

  • Other (please explain)

  1. How is the program or initiative structured?
  • Formal: dedicated person-hours, reporting structure and/or job titles

  • Informal: working groups, mailing lists and/or channels (e.g., Slack) managed by job roles not formally defined as "open source"

  1. Where is the open source program or initiative located within the organization? If the effort is informal, answer based on or who the primary organizers report to.
  • Legal

  • Software Engineering and Development

  • IT

  • Office of the CTO

  • Developer Relations, Marketing or Communications

  • Don't know

  • Other (please specify)

  1. What is your role in the open source program?
  • Executive leadership or oversight (program manager reports to me)

  • Program manager

  • Legal compliance

  • Engineering compliance

  • Developer relations, advocacy, and evangelists

  • Open source developer or engineer (reporting to the open source office)

  • Committee member

  • No formal role

  • Other (please specify)

  1. How long ago was the program established?
  • 0-2 years

  • 3-5 years

  • 5-10 years

  • 10 years

  • Don't know

  1. What are the areas where your company has most benefited from the open source program? (Check all that apply)
  • Increased developer recruitment and retention

  • Increased speed and agility in development cycle

  • Better license compliance

  • Lower licensing fees

  • Lower support costs

  • More influence in open source communities

  • Increased contributions to in-house open source projects from external or third-party contributors

  • More awareness of open source use and commercial dependencies

  • Increased market adoption of open source projects

  • Increased participation in external open source projects

  • Faster time to market with new products

  • Increased innovation

  • Culture change toward faster digital transformation, openness and agility

  • Better security testing and vulnerability management

  • Other (please specify)

  1. What are the ways your open source program quantifies success? (Check all that apply)
  • Fewer license violations

  • Faster compliance process

  • Volume of upstream code contributions

  • Number of open source projects initiated

  • Number of contributors

  • Market adoption or use of projects

  • Developer velocity, efficiency, and/or productivity

  • Developer hiring and onboarding

  • Reach in open source communities

  • Open source culture within the company

  • Time to market with new products

  • Other (please specify)

  1. What are the top three challenges your open source program faces? (Choose three) *
  • Talent: finding and recruiting open source developers

  • Ability to influence open source projects

  • Executive awareness and support

  • Insufficient budget; program costs

  • Internal awareness of the program

  • External awareness (marketing and communcations)

  • License compliance overhead

  • Tracking metrics and performance

  • Tool selection and adoption

  1. On a scale of 1-5, how business-critical is your open source program to the success of your engineering or product teams? (1= extremely critical, 5 = not at all critical)
  • 1 – Extremely critical

  • 2 – Very critical

  • 3 – Somewhat critical

  • 4 – Not so critical

  • 5 – Not at all critical

  1. Has the open source program had a specific impact on your company's DevOps practices or software architecture?
  • Yes

  • No

  • Don't know

  1. When does your company plan to start a program?
  • Next 6 months

  • 6-12 months

  • 13-24 months

  • 24+ months

  1. How will the program or initiative be structured? *
  • Formal: dedicated person-hours, reporting structure and/or job titles

  • Informal: working groups, mailing lists and/or channels (e.g., Slack) managed by job roles not formally defined as "open source"

  1. Where will the open source program or initiative be located within the organization? If the effort is informal, answer based on who the primary organizers will report to.
  • Legal

  • Software Engineering and Development

  • IT

  • Office of the CTO

  • Developer Relations, Marketing or Communications

  • Don't know

  • Other (please specify)

  1. What will be your role in the open source program?
  • Executive leadership or oversight (program manager reports to me)

  • Program manager

  • Legal compliance

  • Engineering compliance

  • Developer relations, advocacy, and evangelists

  • Open source developer or engineer (reporting to the open source office)

  • Committee member

  • No formal role

  1. What does your company aim to accomplish by starting an open source program? (Check all that apply)
  • Increased developer recruitment and retention

  • Increased speed and agility in development cycle

  • Better license compliance

  • Lower licensing fees

  • Lower support costs

  • More influence in open source communities

  • Increased contributions to in-house open source projects from external or third-party contributors

  • More awareness of open source use and commercial dependencies

  • Increased market adoption of open source projects

  • Increased participation in external open source projects

  • Faster time to market with new products

  • Increased innovation

  • Culture change toward faster digital transformation, openness and agility

  • Better security testing and vulnerability management

  • Other (please specify)

  1. What are top three ways your open source program will quantify success? (Choose three) Fewer license violations
  • Faster compliance process

  • Volume of upstream code contributions

  • Number of open source projects initiated

  • Number of contributors

  • Market adoption or use of projects

  • Developer velocity, efficiency, and/or productivity

  • Developer hiring and onboarding

  • Reach in open source communities

  • Open source culture within the company

  • Time to market with new products

  • Other (please specify)

  1. What have been the top three biggest challenges in establishing an open source program? (Choose three)
  • Strategy: planning or knowing how to approach it

  • Finding an open source program manager

  • Finding legal staff with open source expertise

  • Setting an open source policy

  • Getting executive support and buy-in

  • Getting engineering support and buy-in

  • Setting a budget and estimating program costs

  • Assessing or quantifying existing open source use and contribution

  • Resources required to perform license compliance

  • Finding commercial dependencies

  • Tool selection

  • Other (please specify)

  1. Why doesn’t your company have an open source program? (Check all that apply)
  • Used to have one, but ended it

  • Have never heard of an open source program

  • Haven’t considered it

  • Don’t use or participate in open source

  • Organization is too small to need one

  • Organization’s open source use and participation is too small to need one

  • Don’t see the business value

  • Don’t want to regulate or standardize open source practices

  • Time or resource constraints

  • Want one but can’t justify it

  • Other (please specify)

  1. Would your company benefit from an open source program?
  • Yes

  • No

  1. What are the top three ways your company would benefit from an open source program? (Choose three)
  • Increased developer recruitment and retention

  • Increased speed and agility in development cycle

  • Better license compliance

  • Lower licensing fees

  • Lower support costs

  • More influence in open source communities

  • Increased contributions to in-house open source projects from external or third-party contributors

  • More awareness of open source use and commercial dependencies

  • Increased market adoption of open source projects

  • Increased participation in external open source projects

  • Faster time to market with new products

  • Increased innovation

  • Culture change toward faster digital transformation, openness and agility

  • Better security testing and vulnerability management

  • Other (please specify)

  1. How would you approach creating an open source program within your organization?

  2. Why not?

  • Used to have one, but ended it

  • Have never heard of an open source program

  • Haven’t considered it

  • Don’t use or participate in open source

  • Organization is too small to need one

  • Organization's open source use and participation is too small to need one

  • Don’t see the business value

  • Don’t want to regulate or standardize open source practices

  • I don’t know

  • Other (please specify)

  1. If yes, please provide one or two specific examples.
  • Example 1

  • Example 2

  1. How many open source projects does your company maintain?
  • 0

  • 1-10

  • 11-50

  • 51-100

  • 101-1,000

  • 1,000+

  1. How often does your average application development team release code into production?
  • Hourly

  • Daily

  • Weekly

  • Monthly

  • Less than once a month

  • Don’t know

  1. What is the average time between major product releases?
  • < 1 month

  • 1-2 months

  • 3-6 months

  • 6-12 months

  • 12+ months

  1. What kinds of tools does your company use to manage open source code repositories? (Check all that apply)
  • GitHub paid version

  • Other vendor’s paid version (e.g., GitLab, Bitbucket)

  • Free version of vendor solution (e.g., GitHub, GitLab)

  • Homegrown solution

  • Other (please specify)

  1. Which category most closely defines your role?
  • Developer or Software Engineer

  • Other IT

  • Community Manager or Developer Advocate

  • IT management, including CIO, CISO, CTO

  • C-level (non-technology) management

  • Marketing / PR

  • Other

  1. What industry vertical is your company in?
  • Defense

  • Education

  • Financial Services

  • Government

  • Healthcare

  • Insurance

  • Manufacturing and raw materials

  • Retail

  • Technology (software or IT)

  • Telecom, communications, or media

  • Transportation and automotive

  • Utilities

  • Other

  1. Thank you for taking the time to answer our questions. If you would like a copy of the results, please give us your email address. We will only use this email address to communicate with you about this survey.

  2. Finally, if you are interested in participating in an in-depth interview, please provide us with your name and enterprise or organization affiliation.

  • Name

  • Enterprise or Organization