3 |
14 |
15 |
--------------------------------------------------------------------------------
/layouts/shortcodes/todo_presentation.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
14 |
15 |
--------------------------------------------------------------------------------
/Makefile:
--------------------------------------------------------------------------------
1 | serve:
2 | hugo server \
3 | --disableFastRender \
4 | --buildDrafts \
5 | --buildFuture \
6 | --ignoreCache
7 | --printI18nWarnings \
8 | --printMemoryUsage \
9 | --printPathWarnings \
10 | --printUnusedTemplates \
11 | --templateMetrics \
12 | --templateMetricsHints \
13 | --gc
14 |
15 | production-build:
16 | git submodule update --init --recursive
17 | hugo \
18 | --minify
19 |
20 | preview-build:
21 | git submodule update --init --recursive
22 | hugo \
23 | --baseURL $(DEPLOY_PRIME_URL) \
24 | --buildDrafts \
25 | --buildFuture \
26 | --minify
27 |
--------------------------------------------------------------------------------
/content/en/blog/linuxcon-japan-keynote.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "LinuxCon Japan 2016: The Rise of the Open Source Program Office"
3 | author: todogroup
4 | date: 2016-07-19
5 | ---
6 |
7 | Gil Yehuda ([@gyehuda](https://twitter.com/gyehuda)) had an opportunity to keynote at LinuxCon Japan 2016 about
8 | the rise of open source program offices, the presentation is provided below:
9 |
10 | [See the presentation](www.slideshare.net/gyehuda/rise-of-the-open-source-program-office-for-linuxcon-2016)
11 |
12 | If you're interested in joining the TODO Group, please reach out over [Twitter](https://twitter.com/todogroup)!
13 |
--------------------------------------------------------------------------------
/content/en/glossary.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Glossary
3 | url: "/resources/glossary/"
4 | ---
5 |
6 | The world of open source is vast and complex, with many different terms and concepts that can be difficult to navigate. Our aim with this glossary is not to provide a definitive or general definition of these terms, but to clarify what we mean specifically under the context of an OSPO framework (stratey, governance, compliance and community) for organizations.
7 |
8 | {{< button link="https://ospoglossary.todogroup.org/" text="Explore the Glossary" >}} {{< button link="https://ospoglossary.todogroup.org/contribute/" style="secondary" text="Learn how to contribute" >}}
9 |
--------------------------------------------------------------------------------
/content/en/faq/government-institution.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: As a government institution, can I join the TODO Group?
3 | weight: 70
4 | ---
5 |
6 | The TODO Group welcomes any government institution representative willing to collaborate on practices, tools, and other ways to run successful and effective open source programs and open source initatives, as well as to engage in discussions with experienced OSPO professionals.
7 |
8 | Please, take a look to the [TODO Group Overview Presentation](https://docs.google.com/presentation/d/1p4dhx0Dg8fZDO8yzp7nWC2r5WHyVH-jjSQM59lkKLdo/edit?usp=sharing) to learn more about TODO General Membership and/or the OSPO Associates Program.
9 |
--------------------------------------------------------------------------------
/content/en/blog/open-source-strategy-guide.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Open Source Program Guide: Setting an Open Source Strategy"
3 | author: todogroup
4 | date: 2018-08-29
5 | ---
6 |
7 | Last year, the TODO Group published an [initial set of guides](http://todogroup.org/blog/open-source-guides/) focused on the art of open source program management. This year, we plan to continue to update and publish new guides to help our peers in industry to scale out their open source programs and learn from our lesson. Today we are happy to publish a guide on what happens when you are faced with [setting an open source strategy](https://todogroup.org/guides/strategy) for your organization.
8 |
--------------------------------------------------------------------------------
/content/en/faq/todo-community.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Can I be part of the TODO Community without being a TODO Member?
3 | weight: 40
4 | ---
5 |
6 | Yes, TODO Group resources are essentially like any other open source project.
7 |
8 | Everyone willing to contribute to improve OSPO education and adoption across industries worldwide is more than welcome to join the community and take part of the public resources through our GitHub page: https://github.com/todogroup. TODO Community Members include, but are not restricted to:
9 |
10 | * OSPO Managers
11 | * OSPO initiatives
12 | * Industry partners
13 | * Foundations
14 |
15 | Check TODO General Member Charter to learn more.
--------------------------------------------------------------------------------
/content/en/guides/_index.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Guides and Resources
3 | url: "/resources/guides/"
4 | ---
5 |
6 | We collect best practices from the leading companies engaged in open source development and aim to help your organization successfully implement and run an open source program office. For guides tailored to individual contributors, we recommend GitHub’s [community guides](https://github.com/github/opensource.guide).
7 |
8 | ## OSPO Guides
9 |
10 | To build successful Open Source Program Offices, Open Source initiatives, and for open source program management best practices, start here. All content is licensed under [CC-BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).
--------------------------------------------------------------------------------
/content/en/members.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Members
3 | url: "/about/members/"
4 | ---
5 |
6 | TODO is a open community of practicioners who aims to create and share knowledge about Open Source Program Offices or similar Open Source initiatives. TODO Group community is open to all and is formed by its Community participants (including OSPO [Associates](/associates)) and General Members
7 |
8 | [TODO Group Community](/community/) is open to all. Usually, practicioners coming from an organization with an OSPO or an established strategy and policies around Open Source / FOSS efforts within its organization support TODO by becoming [General Members](/join/). Our General Members include:
9 |
10 | {{< todo_group_members >}}
11 |
--------------------------------------------------------------------------------
/content/en/blog/building-leadership.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Open Source Program Guide: Building Leadership in an Open Source Community"
3 | author: todogroup
4 | date: 2018-05-03
5 | ---
6 |
7 | Last year, the TODO Group published an [initial set of guides](http://todogroup.org/blog/open-source-guides/) focused on the art of open source program management. This year, we plan to continue to update and publish new guides to help our peers in industry to scale out their open source programs and learn from our lesson. Today we are happy to publish a guide on what happens when you are faced with [building leadership in your open source community](https://github.com/todogroup/guides/blob/master/building-leadership-in-an-open-source-community.md).
8 |
--------------------------------------------------------------------------------
/content/zh-CN/studies.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: 研究
3 | url: "/resources/studies/"
4 | ---
5 |
6 | * [深入浅出OSPO](https://www.linuxfoundation.org/tools/a-deep-dive-into-open-source-program-offices/) 涉及到OSPO的特征、组织结构、角色、职责和挑战。
7 | * [OSPO的演进](https://linuxfoundation.org/tools/the-evolution-of-the-open-source-program-office-ospo/)：包括OSPO成熟度模型、跨地区跨部门的知名OSPO计划的实施情况，以及一套OSPO原型。可下载多语言版本：
8 | * [English](https://linuxfoundation.org/wp-content/uploads/LFResearch_OSPO_Report.pdf)
9 | * [日本語](https://www.linuxfoundation.jp/wp-content/uploads//2022/05/LFResearch_OSPO_Report-ja3.pdf)
10 | * [中文](https://openevangel.com/yidaoshi/the-evolution-of-the-ospo/content)
11 |
12 | *翻译工作由社区贡献者完成。如欲参与贡献其他语言的翻译，请发送邮件至 info@todogroup.org*
13 |
--------------------------------------------------------------------------------
/layouts/partials/head/custom-head.html:
--------------------------------------------------------------------------------
1 | {{- $source := "scss/home.scss" }}
2 | {{- $target := "css/home.css" }}
3 | {{ $options := (dict "targetPath" $target) }}
4 | {{ if eq hugo.Environment "production" }}
5 | {{ $options = merge $options (dict "outputStyle" "compressed" "enableSourceMap" false) }}
6 | {{ else }}
7 | {{ $options = merge $options (dict "outputStyle" "nested" "enableSourceMap" true) }}
8 | {{ end }}
9 | {{ $style := resources.Get $source | resources.ToCSS $options | resources.PostCSS (dict "config" "postcss.config.js") | resources.Fingerprint "sha512" }}
10 | {{ if (eq .Kind "home") }}
11 |
12 | {{ end }}
13 |
--------------------------------------------------------------------------------
/content/en/comms.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Communication Channels
3 | url: "/community/comms/"
4 | ---
5 |
6 | Are you new to our community? We invite you to join us on the different communication Channels:
7 |
8 | * [Slack](https://join.slack.com/t/thetodogroup/shared_invite/zt-169ok18cz-Pi6tpVHTeW9254d1FpkLew): Includes OSPOlogy and TODO Member communication channels
9 | * [OSPOlogy Community Mailing List](https://docs.google.com/forms/d/e/1FAIpQLSeU0YGM_IJ6gY8E5IIiwXKD_FZi3kAVc4E9_-3dtTDyKMSjdA/viewform)
10 | * [OSPOlogy Forum (GH Discussions)](https://github.com/todogroup/ospology/discussions)
11 |
12 | **OSPOlogy Regional Communication Channels**
13 |
14 | * Europe Chapter: Slack channel #chapter-europe
15 | * APAC Chapter: Slack channel #chapter-apac
--------------------------------------------------------------------------------
/content/zh-CN/join.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: 加入 TODO Group
3 | ---
4 |
5 | [TODO Group 社区](/community/)面向所有人开放。有时，一些社区参与者已经建立了 OSPO 或开源计划，他们也希望成为普通会员。
6 |
7 | ## 成为普通会员
8 |
9 | 如果你有兴趣成为普通会员来加入并支持 TODO Group，请填写 [会员申请表](https://enrollment.lfx.linuxfoundation.org/?project=todogroup)。
10 |
11 | **注: 要成为 TODO Group 普通会员，必须先成为 [Linux 基金会会员](https://www.linuxfoundation.org/members/join)。**
12 |
13 | 每一位 TODO Group 普通会员必须同意并签署 [章程](https://github.com/todogroup/charter)。
14 |
15 | ## 成为 OSPO 合作伙伴
16 |
17 | 社区参与者来自关注 [OSPO 相关主题](https://ospomindmap.todogroup.org/)的实体，他们帮助 OSPO，但可能没有 OSPO，他们可以通过成为 [OSPO 合作伙伴](/associates)来支持 TODO。
18 |
19 | **注：OSPO 合作伙伴计划不同于 TODO Group 普通会员关系，不享有普通会员权益。要了解 OSPO 合作伙伴权益，请[阅读相关文档](https://github.com/todogroup/governance/blob/main/OSPO-Associate-Program.md)。**
20 |
--------------------------------------------------------------------------------
/content/en/blog/todo-take-survey.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Take the Open Source Programs Survey"
3 | author: todogroup
4 | date: 2018-07-02
5 | ---
6 |
7 | Almost every developer uses open source code. But not every organization has an open source policy or a formal program to manage how it is used or produced. The TODO Group has partnered with The Newstack to build the first ever open source programs survey.
8 |
9 | Some of the questions we ask include:
10 |
11 | * If your organization does not have an open source program, why not?
12 | * What are the challenges and benefits of an open source program?
13 | * How critical is an open source program to your engineering success?
14 | * How is open source code managed?
15 | * And more!
16 |
17 | Thank you for helping us collect the best data possible!
--------------------------------------------------------------------------------
/content/en/mindmap.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: MindMap
3 | url: "/resources/mindmap/"
4 | ---
5 |
6 | The [OSPO Mind Map](https://ospomindmap.todogroup.org/) - an interactive Mind Map that schemes the main Open Source program Office's responsibilities, roles, behavior and team size within the Ecosystem. Project can be found as part of [OSPOlogy repo](https://github.com/todogroup/ospology/tree/main/ospo-mindmap). People can find an interactive version in multiple languages:
7 |
8 | - [English](https://ospomindmap.todogroup.org/)
9 | - [日本語](https://ospomindmap.todogroup.org/jp)
10 | - [中文](https://ospomindmap.todogroup.org/cn)
11 |
12 | *Translations are done via community contributions via [OSPOlogy repo](https://github.com/todogroup/ospology/tree/main/ospo-mindmap)*
13 |
14 | {{< todo_mindmap >}}
--------------------------------------------------------------------------------
/content/en/faq/university.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: As a university or academic institution, can I join the TODO Group?
3 | weight: 60
4 | ---
5 |
6 | Universities can join the TODO Group to collaborate on practices, tools, and other ways to run successful and effective open source programs and open source initatives, as well as to engage in discussions with OSPO professionals.
7 |
8 | OSPO professionals from universities such as [Rochester Institute of Technology (RIT)](https://www.rit.edu/research/open) or [University of California Santa Cruz](cross.ucsc.edu) have been TODO Members over the past years.
9 |
10 | Please, take a look to the [TODO Group Overview Presentation](https://docs.google.com/presentation/d/1p4dhx0Dg8fZDO8yzp7nWC2r5WHyVH-jjSQM59lkKLdo/edit?usp=sharing) to learn more about membership benefits.
--------------------------------------------------------------------------------
/content/en/faq/should-i-join.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Should I join?
3 | weight: 20
4 | ---
5 |
6 | TODO is specifically intended as a space for organizations' open source program practitioners to come together, but also for people committed to open source willing to learn and get practical knowledge on open soruce program offices and open source initiatives.
7 |
8 | * General Members are representatives from organizations who consider open source to be an essential asset in their day-to-day operations.
9 |
10 | * OSPO Associates are representatives from open source projects and/or foundations willing to collaborate with TODO mission and build resources that are helpful for people working in OSPOs and open source initiatives.
11 |
12 | * OSPO Ambassadors are individuals actively contirbuting to OSPO resources and advocating for TODO values.
--------------------------------------------------------------------------------
/static/_redirects:
--------------------------------------------------------------------------------
1 | # Netlify redirects from what the browser requests to what we serve
2 | # 301 status is default
3 | /members/ /about/members/
4 | /community/ /community/get-started/
5 | /about/ /about/about-us/
6 | /code-of-conduct/ /about/code-of-conduct/
7 | /associates/ /about/associates/
8 | /faq/ /about/faqs/
9 | /guides/casestudies/ /resources/case-studies/
10 | /guides/casestudies/facebook/ /resources/case-studies/meta/
11 | /guides/casestudies/* /resources/case-studies/:splat
12 | /guides/ /resources/guides/
13 | /guides/* /resources/guides/:splat
14 |
15 | # Blog should work as before
16 | # Case studies were nested under guides
17 |
--------------------------------------------------------------------------------
/content/en/blog/oscon-talk.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "OSCON 2016: Open Source Lessons from the TODO Group"
3 | author: todogroup
4 | date: 2015-05-18
5 | ---
6 |
7 | We had an opportunity to speak at OSCON 2016, the slides are provided below:
8 |
9 |
10 |
11 | Thank you to everyone who attended our session and asked questions! If you're
12 | interested in joining the TODO Group, please reach out over Twitter!
13 |
14 | See a follow up [blog](http://www.ingeniousmalarkey.com/2016/05/starting-open-source-office-within-your.html) from Ben VanEvery about his experience starting the Open Source Office at Box.
15 |
16 |
--------------------------------------------------------------------------------
/content/ja/guides/ospo-simple-faq.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: オープンソースプログラムオフィス（OSPO）簡単なFAQ
3 | ---
4 | OSPO簡単なFAQ（作業中）は、オープンソースプログラムオフィス（OSPO）の設立と運営に関するキーポイントについて触れています。
5 |
6 | > OSPO簡単なFAQは進行中のプログレスを反映するため、定期的に更新されることをご留意ください。
7 |
8 | ## 💚 OSPO FAQの作業と寄稿者について
9 |
10 | 
11 |
12 | OSPOシンプルFAQはまだ作業中です。日本のOSPOローカルミートアップのメンバーが日本語で作成しており、OpenChain Japan WGとTODO Groupのサポートを受けています。
13 | オリジナルバージョンは、2週ごとのOSPO Japanローカルミートアップの一環として日本語で文書化されており、活動は大和田清志によってサポートされています。
14 |
15 | * ミーティングに参加するには、オンラインコミュニティプラットフォームに参加することができます。
16 | * 日常の会話はTODO GroupのSlackチャンネル「#chapter-japan」で行われます。
17 |
18 | ## 📝 文書化
19 |
20 | * [OSPO簡単なFAQ「作業中」を日本語でダウンロード](https://github.com/todogroup/todogroup.org/files/11635143/OSPO_SimpleQA.pdf)
21 | * [OSPO簡単なFAQ「作業中」を英語でダウンロード](https://github.com/todogroup/todogroup.org/files/11635329/OSPO_SimpleQA_en.pdf)
22 |
--------------------------------------------------------------------------------
/content/en/blog/oslc-tahoe.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "CFP: Open Source Leadership Summit 2017"
3 | author: todogroup
4 | date: 2016-11-29
5 | ---
6 |
7 | The TODO Group will be hosting a formal open source office track at the Open Source Leadership Summit in Tahoe next year.
8 |
9 | We hosted a track last year and encourage the wider community to submit your proposals. We are especially interested in proposals that examine the structure of existing open source programs, what has helped those programs succeed (or fail!), how company culture has shaped those programs, and any lessons learned along the way. We would also love to present case studies that examine the process of open sourcing a project - the good, the bad and the ugly.
10 |
11 | Good luck, we look forward to seeing you in Tahoe!
12 |
13 |
--------------------------------------------------------------------------------
/content/en/blog/ospo101.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "OSPO 101"
3 | author: todogroup
4 | date: 2021-05-11
5 | ---
6 |
7 | The TODO Group would like announce the sharing of a modular OSPO 101 course:
8 |
9 | 
10 |
11 | All the content is modularized and licensed under CC-BY 4.0 for your usage:
12 | [https://github.com/todogroup/ospo101](https://github.com/todogroup/ospo101)
13 |
14 | We would like to thank [Guy Martin](https://twitter.com/guyma) for helping seed the initial content for the course. The course was converted to friendly markdown format by the TODO Group community, including contributions from [Chris Aniszczyk](https://twitter.com/cra) and Greg Back.
15 |
16 | If you're interested in starting an open source program or collaborating with your peers in open source program management, please consider [joining the TODO Group](http://todogroup.org/join/)!
17 |
--------------------------------------------------------------------------------
/layouts/case-studies/list.html:
--------------------------------------------------------------------------------
1 | {{ define "main" }}
2 | {{ .Content }}
3 |
4 | {{ range .Pages }}
5 | {{ $title := .Title }}
6 | {{ $image := .Params.image }}
7 |
17 | {{ end }}
18 |
19 | {{ end }}
20 |
--------------------------------------------------------------------------------
/i18n/zh-cn.yaml:
--------------------------------------------------------------------------------
1 | hero1:
2 | other: 开放交流
3 | hero2:
4 | other: 开放开发
5 | subhero:
6 | other: 面向致力于开源办公室（OSPO）的开源从业者。
7 | explainerText:
8 | other: TODO 是一个开放的实践者社区，旨在创建和分享知识，在实践、工具和其他方式上进行协作，以成功、有效地运行开源办公室或类似的开源计划。TODO Group 由[社区](/community/ambassadors/)参与者和大使、[OSPO 合作伙伴](/about/associates/)和[普通会员](/about/members/) 组成。
9 | explainerButton:
10 | other: 关于我们
11 | sectionTitle:
12 | other: 参与其中
13 | sectionTitle1:
14 | other: 加入我们的社区
15 | sectionText1:
16 | other: 开源办公室的实践者领导跨组织的开源采纳
17 | sectionButton1:
18 | other: 加入社区
19 | sectionTitle2:
20 | other: 成为 OSPO 合作伙伴
21 | sectionText2:
22 | other: 支持 TODO 愿景并助力 OSPO 运动的开源社区、项目和基金会
23 | sectionButton2:
24 | other: 参与其中
25 | sectionTitle3:
26 | other: 成为普通会员
27 | sectionText3:
28 | other: 支持 TODO 愿景和 OSPO 采纳并致力于开源的组织
29 | sectionButton3:
30 | other: 成为支持者
31 | landscapeTitle:
32 | other: OSPO 全景图
33 | landscapeText:
34 | other: OSPO 全景图绘制了 OSPO 生态系统，包括采纳的组织和 OSPO 团队使用的工具，以及组织内的开源专业人员
35 | landscapeButton:
36 | other: 探索全景图
37 |
--------------------------------------------------------------------------------
/data/authors.yaml:
--------------------------------------------------------------------------------
1 | # blog author data, the key is github username.
2 | todogroup:
3 | # name: The TODO Group
4 | # twitter: todogroup
5 | jlprat:
6 | name: Josep Prat
7 | twitter: jlprat
8 | company: Aiven
9 | nruff:
10 | name: Nithya Ruff
11 | twitter: nithyaruff
12 | company: SanDisk
13 | bvanevery:
14 | name: Benjamin VanEvery
15 | twitter: bvanevery
16 | company: Box
17 | bkeepers:
18 | name: Brandon Keepers
19 | twitter: bkeepers
20 | company: GitHub
21 | gianugo:
22 | name: Gianugo Rabellino
23 | twitter: gianugo
24 | company: Microsoft
25 | caniszczyk:
26 | name: Chris Aniszczyk
27 | twitter: cra
28 | company: CNCF
29 | gyehuda:
30 | name: Gil Yehuda
31 | twitter: gyehuda
32 | company: Verizon Media
33 | dalmaer:
34 | name: Dion Almaer
35 | twitter: dalmaer
36 | company: Walmart Labs
37 | nzakas:
38 | name: Nicholas C. Zakas
39 | twitter: slicknet
40 | company: Box
41 | anajsana:
42 | name: Ana Jimenez Santamaria
43 | twitter: anajsana95
44 | company: The Linux Foudation
45 |
--------------------------------------------------------------------------------
/content/en/studies.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Studies
3 | url: "/resources/studies/"
4 | ---
5 |
6 | * [A Deep Dive into Open Source Program Offices](https://www.linuxfoundation.org/tools/a-deep-dive-into-open-source-program-offices/) Includes OSPO characteristics, structures, roles, responsibilities, and challenges.
7 | * [The Evolution of the OSPO](https://linuxfoundation.org/tools/the-evolution-of-the-open-source-program-office-ospo/): Includes an OSPO maturity model, practical implementation from noted OSPO programs across regions and sectors, and a set of OSPO Archetypes. People can download the PDF version in multiple languages:
8 | * [English](https://linuxfoundation.org/wp-content/uploads/LFResearch_OSPO_Report.pdf)
9 | * [日本語](https://www.linuxfoundation.jp/wp-content/uploads//2022/05/LFResearch_OSPO_Report-ja3.pdf)
10 | * [中文](https://openevangel.com/yidaoshi/the-evolution-of-the-ospo/content)
11 |
12 | *Translations are done via community contributions. Please send an email to info@todogroup.org to contribute to other translations.*
--------------------------------------------------------------------------------
/i18n/ja.yaml:
--------------------------------------------------------------------------------
1 | hero1:
2 | other: Talk openly
3 | hero2:
4 | other: Develop openly
5 | subhero:
6 | other: オープンソースに取り組むすべての企業のみなさんへ。
7 | explainerText:
8 | other: TODOは、知識を創造・共有し、実践、ツール、その他の方法で成功的かつ効果的なオープンソースプログラムオフィスや同様のオープンソースイニシアティブを運営することを目指す実践者のオープンなコミュニティです。TODOグループは、[Community](../community)の参加者と[General Members](../members)によって形成されています。
9 | explainerButton:
10 | other: 私たちについて
11 | sectionTitle:
12 | other: 関与する
13 | sectionTitle1:
14 | other: コミュニティに参加する
15 | sectionText1:
16 | other: 組織全体でオープンソースの採用をリードするオープンソースプログラムオフィスの実践者
17 | sectionButton1:
18 | other: コミュニティに参加
19 | sectionTitle2:
20 | other: OSPAアソシエイトになる
21 | sectionText2:
22 | other: TODOのミッションをサポートし、OSPOムーブメントを支援するオープンソースコミュニティ、プロジェクト、基盤
23 | sectionButton2:
24 | other: 関与する
25 | sectionTitle3:
26 | other: 一般メンバーになる
27 | sectionText3:
28 | other: TODOのミッションとOSPO採用をサポートするオープンソースにコミットした組織
29 | sectionButton3:
30 | other: サポーターになる
31 | landscapeTitle:
32 | other: OSPOの風景
33 | landscapeText:
34 | other: OSPOの風景は、OSPOチームや組織内のオープンソースの専門家が使用する採用者組織やツールをマッピングしたものです
35 | landscapeButton:
36 | other: 風景を探索する
37 |
--------------------------------------------------------------------------------
/layouts/_default/rss.xml:
--------------------------------------------------------------------------------
1 | {{ printf "" | safeHTML }}
2 | 
11 | {{ else }}
12 | 
13 | {{ end }}
14 |
3 |
26 |
27 |
4 |
5 | {{ i18n "hero1" }}
7 |
8 |
14 |
15 |
5 | {{ i18n "hero1" }}
{{ i18n "hero2" }}
6 |
7 |
8 | {{ i18n "subhero" }}
9 | 10 |{{ i18n "explainerText" | markdownify }}
11 | 12 | {{ i18n "explainerButton" }} 13 |
16 | 
24 |
25 | {{ i18n "sectionTitle" | markdownify }}
28 | 29 |
30 |
50 |
51 |
31 |
35 |
36 | {{ i18n "sectionTitle1" }}
32 |{{ i18n "sectionText1" | markdownify }}
33 | {{ i18n "sectionButton1" }} 34 |
37 |
43 |
44 | {{ i18n "sectionTitle2" }}
38 |{{ i18n "sectionText2" | markdownify }}
39 | {{ i18n "sectionButton2" }} 42 |
45 |
49 | {{ i18n "sectionTitle3" }}
46 |{{ i18n "sectionText3" | markdownify }}
47 | {{ i18n "sectionButton3" }} 48 |52 | 53 |
54 |
70 |
90 | {{ end }}
91 |
--------------------------------------------------------------------------------
/content/en/blog/why-we-run-an-open-source-program-github.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Why we run an open source program - GitHub
3 | author: bkeepers
4 | date: 2015-03-17
5 | ---
6 |
7 | _This is the fourth in a series of blog posts from TODO Group members, explaining why each company is committed to open source software. This week, we feature Brandon Keepers ([@bkeepers](https://twitter.com/bkeepers)), who is heading up the open source efforts at [GitHub](https://github.com/github)._
8 |
9 | From the very beginning, GitHub has been about open source. Scratching the itch of better code collaboration turned into a company built on and for open source; from the philosophies that founded the company, to the servers running the infrastructure, to the languages and libraries we use to build applications, to the millions of public repositories hosted on them. Even our business model - based on the premise that you shouldn't have to pay if you share - encourages open source.
10 |
11 | We support open source because we believe it is the best model for creating software. Employing reusable open source components forces you to construct modular and scalable systems. The healthiest parts of our infrastructure depend heavily on open source technology. For example, having dedicated people contributing to Git means we have the freedom to add features and share our improvements with the community. As we push the boundaries of what is possible with Git, our enhancements are tested in production on GitHub before we push them to the upstream project for the benefit of the rest of the community. We can create better tools by building on open source systems and being actively engaged with the community.
12 |
13 | We want to build the best platform for collaborating on software. There are subtle and important differences in the way we work together to build closed source products versus maintaining open source projects. We use GitHub to build GitHub, which gives us insight into how to shape our product to suit the ever-growing teams and codebases of our customers. Actively participating in open source means we also experience GitHub the same way the rest of the community does.
14 |
15 | Like other members of the TODO Group, we believe companies have just as much to learn from open source as the community has to benefit from the support of these businesses. As Kim Polese says in [_Open Sources 2.0_](http://commons.oreilly.com/wiki/index.php/Open_Sources_2.0/Foreword:_Source_Is_Everything), "open source has grown far beyond the mainstream. It has become the bedrock over which the mainstream flows." We celebrate the notion that nobody has to build their own bedrock any more. This is just the beginning. Open source will continue to significantly alter what is possible as we share our knowledge in the form of free software.
16 |
17 | Building the most popular platform for collaborating on open source puts GitHub in a unique position, and we take our responsibility to the community seriously. We participate in open source because it's who we are, and we want to help everyone become a contributor.
18 |
--------------------------------------------------------------------------------
/content/en/training.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Training Modules
3 | url: "/resources/training/"
4 | ---
5 | The [OSPO 101 Course](https://github.com/todogroup/ospo101) covers everything you need to know about Open Source Program Offices. The course materials are modular, available on GitHub, and licensed under a Creative Commons license, allowing them to be remixed and reused as needed.
6 |
7 | {{< img src="/img/ospo101.svg" width="300" alt="OSPO 101 Logo">}}
8 |
9 | It is intended to be a modularized so the content is reusable in a piecemeal fashion:
10 |
11 | * [Open Source Introduction](https://github.com/todogroup/ospo-career-path/tree/main/OSPO-101/module1)
12 | * Introducing Open Source
13 | * A Short History of Open Source Software
14 | * Reasons to Use Open Source
15 | * [Open Source Business Strategy](https://github.com/todogroup/ospo-career-path/tree/main/OSPO-101/module2)
16 | * Introducing Open Source Business Models
17 | * Developing an Open Source Strategy
18 | * Developing Open Source Policies
19 | * Introducing the Open Source Program Office (OSPO)
20 | * [Effective Open Source Program (OSPO) Management](https://github.com/todogroup/ospo-career-path/tree/main/OSPO-101/module3)
21 | * Open Source Program Offices & Your Organization
22 | * Building an Effective Open Source Program Office
23 | * Additional Information & Case Studies
24 | * [Open Source Development Practices](https://github.com/todogroup/ospo-career-path/tree/main/OSPO-101/module4)
25 | * Effective Open Source Development & Participation
26 | * The Role of Continuous Integration & Testing
27 | * Applying Open Source Methodologies Internally
28 | * [Open Source Compliance Programs](https://github.com/todogroup/ospo-career-path/tree/main/OSPO-101/module5)
29 | * Open Source Licensing and Compliance Basics
30 | * Building an Effective Compliance Program
31 | * Choosing the Right License Compliance Tool
32 | * The Role of Open Source Audits During M&A Activities
33 | * [Collaborating Effectively with Open Source Projects](https://github.com/todogroup/ospo-career-path/tree/main/OSPO-101/module6)
34 | * Understanding Upstream Open Source Projects
35 | * Effective Upstream Contribution Strategies
36 | * Upstream Development Practices
37 | * [Creating Open Source Projects](https://github.com/todogroup/ospo-career-path/blob/main/OSPO-101/module7/README.md)
38 | * Open Source Project Creation Overview
39 | * New Project Preparations
40 | * Successful Project Launch & Sustainment
41 |
42 | The OSPO 101 Course is part of a bigger initiative called OSPO Career Path, a set of open source, and free courses created by folks from the TODO community to support training inside the organization for people working in OSPOs and similar open source initiatives. Each course is intended to be modularized so the content is reusable in a piecemeal fashion.
43 |
44 | {{< button link="https://github.com/todogroup/ospo-career-path" text="Explore Training Resources" >}} {{< button link="https://lists.todogroup.org/g/WG-ospo-career-path" style="secondary" text="Join the Working Group" >}}
45 |
--------------------------------------------------------------------------------
/content/en/blog/top-ospo-resources.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Top OSPO resources to explore during August"
3 | author: todogroup
4 | date: 2022-08-04
5 | ---
6 |
7 |
8 | At TODO we are taking a short break from our [monthly community calls](https://github.com/todogroup/ospology#-community) during August. The good news is that this might be a great chance to
9 | start learning something new from a community! These are some of the most popular resources powered by TODO, helpful sources of information to read
10 | through and maybe be inspired by open source leaders involved in OSPOs.
11 |
12 |
13 | ## 1️⃣ OSPOlogy, the study of OSPOs
14 |
15 | Recorded videos that share [real OSPO Stories](https://github.com/todogroup/ospology/tree/main/meetings#event-page-and-past-sessions) and topics
16 | that matter. Take a look at [OSPOlogy Youtube Channel](https://www.youtube.com/channel/UCi-ELHAwzoYZvAs4FH-ShaA) and learn how organizations like
17 | Spotify, Google, RIT, Alliander, Aiven, Bloomberg, Sony, UC Santa Cruz, and more use their OSPOs.
18 |
19 | ## 2️⃣ OSPO Mind Map
20 |
21 | The [OSPO Mind Map](https://github.com/todogroup/ospology/tree/main/ospo-mindmap#welcome-to-the-ospo-mind-map-) schemes the main Open Source program
22 | Office's responsibilities, roles, behavior, and team size within the Ecosystem and is also a great tool to explain what your OSPO does or can do
23 | within your organization.
24 |
25 | An interactive OSPO Mind Map version can be found at:[https://ospomindmap.todogroup.org/](https://ospomindmap.todogroup.org/)
26 |
27 |
28 | ## 3️⃣ Templates on OSPO and OS policies
29 |
30 | Gathers different [OSPO and OS Policies](https://github.com/todogroup/policies) from various organizations such as eBay, GitLab, Google,
31 | Linux Foundation, FINOS, Indeed, SUSE, United States Government Services Administration (GSA), Zalando, Yahoo, and more!
32 |
33 | ## 4️⃣ OSS Management Tooling List
34 |
35 | [This list](https://github.com/todogroup/awesome-ospo) identifies packages and projects that are found helpful for managing open source projects and offices in key areas such as:
36 |
37 | - Code Reviews
38 | - Continuous Integration / Continuous Delivery
39 | - Contributor License Agreements / Developer Certificate of Origins
40 | - GitHub Metrics and Dashboards
41 | - GitHub Management
42 | - Project Quality
43 | - Supply Chain Trust
44 | - Licensing
45 | - Localization and Internationalization
46 | - Websites and Documentation
47 | - Security
48 | - In-Kind Donations
49 | - Content License
50 |
51 |
52 | ## 5️⃣ OSPO Jobs
53 |
54 | Contains a [list of published job descriptions related to open source program office (OSPO) roles](https://github.com/todogroup/job-descriptions). People can use these examples when creating a job description of your organization and to get a sense of the types of roles found in OSPOs.
55 |
56 | ## Bonus point: OSPONews
57 |
58 | [OSPONews](https://www.getrevue.co/profile/osponews) can be a good choice to help keep track of
59 | [Open Source Program Office](https://github.com/todogroup/ospodefinition.org)
60 | (OSPO) trends and new resources. It ships every month directly to your inbox!
61 |
--------------------------------------------------------------------------------
/content/en/blog/open-source-guides.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "TODO Open Source Program Guides"
3 | author: todogroup
4 | date: 2017-09-11
5 | ---
6 |
7 | Last March we held a [TODO Group track at Open Source Leadership Summit](http://todogroup.org/blog/todo-osls/) focused entirely on sharing best practices for businesses managing and building out open source programs. More than a dozen open source program leads and other leaders from companies shared their tips and best practices at the event.
8 |
9 | Furthermore in the last year or so, we have seen companies like AWS [build out an open source program](http://fortune.com/2016/12/01/amazon-open-source-guru/) via [@AWSOpen](https://twitter.com/AWSOpen) and even companies like [VMWare hired their first Chief Open Source Officer](https://thenewstack.io/makers-dirk-hohndel-vmware-role-open-source-commercial-software/). We've had many organizations approach TODO Group members asking for advice on how to get started with an open source program.
10 |
11 | To help companies inform and improve their open source practices, we here at the TODO Group have ramped up our knowledge sharing this year and offering more free resources by open sourcing a set of living guides to help you learn more about setting up an open source program:
12 |
13 | * [How to Create an Open Source Program](https://github.com/todogroup/guides/blob/master/creating-an-open-source-program.md)
14 | * [Measuring Your Open Source Program](https://github.com/todogroup/guides/blob/master/measuring-your-open-source-program.md)
15 | * [Tools for Measuring Your Open Source Program](https://github.com/todogroup/guides/blob/master/tools-for-managing-open-source-programs.md)
16 | * [Using Open Source Code](https://github.com/todogroup/guides/blob/master/using-open-source.md)
17 | * [Participating in Open Source Communities](https://github.com/todogroup/guides/blob/master/participating-in-open-source.md)
18 | * [Recruiting Open Source Developers](https://github.com/todogroup/guides/blob/master/recruiting-developers.md)
19 |
20 | We are also profiling the open source programs and many of these companies, which have shared their tips and best practices. Their advice comes from years of professional open source program management experience at some of the largest and most successful software companies -- many which built their businesses on open source software and contribute significantly to open source communities. We have open source two case studies initially and plan to do more soon:
21 |
22 | * [Comcast](https://github.com/todogroup/guides/blob/master/casestudies/comcast.md)
23 | * [Salesforce](https://github.com/todogroup/guides/blob/master/casestudies/salesforce.md)
24 |
25 | These guides and case studies are open source on GitHub under a CC-BY-SA 4.0 license. If you would like us to feature your open source program in our profiles please submit a pull request at https://github.com/todogroup/guides. We also welcome your contributions and ideas to these guides and invite you to contribute content to the existing versions, create case studies or new guides.
26 |
27 | If you're interested in starting an open source program or collaborating with your peers in open source program management, please consider [joining the TODO Group](http://todogroup.org/join/)!
28 |
--------------------------------------------------------------------------------
/content/zh-CN/guides/_index.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: 指南与资源
3 | ---
4 | TODO 小组提供了一个**成熟度模型**、一系列**指南**、一份**思维导图**、一个**101 入门课程**、**年度调研**，以及 **案例研究**，以帮助促进组织的 OSPO 之旅。这些 OSPO 资源由 TODO 小组与 Linux基金会及各大开源社区共同开发。我们希望这些资源，通过社区的贡献发展为持续迭代的文档。
5 |
6 | * 🚀 OSPO 研究与报告
7 | * [深入了解OSPO](https://www.linuxfoundation.org/tools/a-deep-dive-into-open-source-program-offices/) ：包括OSPO的特点、结构、角色、职责和挑战。
8 | * [English](https://www.linuxfoundation.org/research/a-deep-dive-into-open-source-program-offices)
9 | * [简体中文](https://www.ibrahimatlinux.com/wp-content/uploads/2023/01/OSPO-CN.pdf)
10 | * [OSPO的演变](https://linuxfoundation.org/tools/the-evolution-of-the-open-source-program-office-ospo/)：包含了一个OSPO成熟度模型，跨地区和部门的知名OSPO计划的实际实施，以及一组OSPO原型。 可在此下载不同语言的PDF文档:
11 | * [English](https://linuxfoundation.org/wp-content/uploads/LFResearch_OSPO_Report.pdf)
12 | * [日本語](https://www.linuxfoundation.jp/wp-content/uploads//2022/05/LFResearch_OSPO_Report-ja3.pdf)
13 | > *翻译工作由社区贡献。可发送邮件至info@todogroup.org请求贡献其他语言的翻译*
14 |
15 | * 📝 [TODO OSPO 指南](#ospo-guides)：向从事开源开发的领先公司收集最佳实践，以帮助组织成功实施和运行开源项目办公室。如果需要为个人开发者量身定制的指南，我们推荐 GitHub 的 [开源指南](https://github.com/github/opensource.guide)。
16 |
17 | * 🧭 [OSPO 思维导图](https://ospomindmap.todogroup.org/)：一个交互式思维导图，体现了OSPO在生态中的主要职责、角色、行为和团队规模。作为项目的一部分，可在这里了解 [OSPOlogy repo](https://github.com/todogroup/ospology/tree/main/ospo-mindmap)。交互式的多语言版本：
18 |
19 | * [English](https://ospomindmap.todogroup.org/)
20 | * [日本語](https://ospomindmap.todogroup.org/jp)
21 | * [简体中文](https://ospomindmap.todogroup.org/cn)
22 |
23 | > *翻译工作由社区贡献者通过 [OSPOlogy repo](https://github.com/todogroup/ospology/tree/main/ospo-mindmap)贡献*
24 |
25 | * 📚 [OSPO 101 入门课程](https://github.com/todogroup/ospo101): 涵盖了有关开源项目办公室你需要了解的所有信息。课程材料是模块化的，可在GitHub上获得，并根据知识共享许可证进行许可，允许根据需要重新组合和重复使用。
26 |
27 | * 📈 [OSPO 年度调研](https://github.com/todogroup/osposurvey): TODO 小组保证每年开展一次这项调研，并与更广泛的社区分享调研成果。在这里可以了解更多。
28 |
29 | * 🔎 [案例研究](#ospo-case-studies): 实践案例研究，向OSPO或组织内的类似开源计划学习。
30 |
31 | ## OSPO 指南
32 |
33 | 要建立成功的开源项目办公室或类似开源计划，请从这里开始：
34 |
35 | * [如何建立开源计划](/guides/create-program)
36 | * [度量你的开源计划](/guides/measuring)
37 | * [开源计划的管理工具](/guides/management-tools)
38 | * [OSPO职业发展管理](/guides/career-development)
39 |
40 | 开源项目管理最佳实践：
41 |
42 | * 🆕 [贡献和启动开源项目](/guides/outbound-oss)
43 | * [使用开源代码](/guides/using-open-source)
44 | * [参与开源社区](/guides/participating)
45 | * [招聘开源开发者](/guides/recruiting-developers)
46 | * [开始一个开源项目](/guides/starting)
47 | * [开源阅读清单](/guides/open-source-reading-list)
48 | * [提升开源开发影响力](/guides/impact)
49 | * [终止一个开源项目](/guides/shutting-down)
50 | * [建设开源社区领导力](/guides/building-leadership)
51 | * [制定开源战略](/guides/strategy)
52 | * [推广开源项目](/guides/marketing-open-source-projects)
53 | * [建立一个有包容性的开源社区](/guides/diversity-inclusion)
54 | * [组织和管理开源活动](/guides/organizing-and-managing-open-source-events)
55 | * [创建开源商业生态系统](/guides/os-commercial-ecosystem)
56 |
57 |
58 | ## Open Source Program Office (OSPO) 101
59 |
60 | [OSPO 101](https://github.com/todogroup/ospo101) 课程包含了关于OSPO的几乎所有知识。
61 |
62 | 
63 |
64 | 因为该课程是模块化的，所以该内容可以逐个重复学习和使用。
65 |
66 | ## OSPO 案例研究
67 |
68 | 如果你的开源办公室也希望增加一个案例研究，请发送一个提交请求！
69 |
70 | ## 许可
71 |
72 | 所有内容使用 [CC-BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) 许可。
73 |
--------------------------------------------------------------------------------
/content/en/blog/todo-ossna2020.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "TODO at Open Source Summit North America"
3 | author: todogroup
4 | date: 2020-06-18
5 | ---
6 |
7 | At [Open Source Summit North America](https://events.linuxfoundation.org/events/open-source-summit-north-america-2020/), the TODO Group will lead a virtual track featuring a variety of talks dedicated to open source program management:
8 |
9 | Listed below are the talks from the TODO track at OSSNA:
10 |
11 | ## Monday, June 20
12 | * [2020 Trends in Enterprise Open Source Programs - Alex Williams, The New Stack](https://ossna2020.sched.com/event/c3QB/2020-trends-in-enterprise-open-source-programs-alex-williams-the-new-stack)
13 | * [Building a Secure, Efficient, Compliance OSS Supplychain at Scale - Tan Zhongyi (Jerry Tan), Baidu](https://ossna2020.sched.com/event/c3U3/building-a-secure-efficient-compliance-oss-supplychain-at-scale-tan-zhongyi-jerry-tan-baidu)
14 | * [C in CRM Stands for Community: The DevRel Way - Ana Jimenez Santamaria, Bitergia](https://ossna2020.sched.com/event/c3ZH/c-in-crm-stands-for-community-the-devrel-way-ana-jimenez-santamaria-bitergia)
15 | * [Growing Participation in Your Company’s OSS Projects - Dawn Foster, VMware](https://ossna2020.sched.com/event/c3Sq/growing-participation-in-your-companys-oss-projects-dawn-foster-vmware)
16 | * [Growing Sustainable Contributions Through Ambassador Networks - Alison Yu, Indeed & Shilla Saebi, Comcast](https://ossna2020.sched.com/event/c3ZH/c-in-crm-stands-for-community-the-devrel-way-ana-jimenez-santamaria-bitergia)
17 | * [How (And Why) to Identify Your Critical OSS Dependencies - Julia Ferraioli, Google](https://ossna2020.sched.com/event/c3Sw/how-and-why-to-identify-your-critical-oss-dependencies-julia-ferraioli-google)
18 | * [How to Grow Your Open Source Project and Become an Umbrella Project - John Mertic, The Linux Foundation](https://ossna2020.sched.com/event/c3WQ/how-to-grow-your-open-source-project-and-become-an-umbrella-project-john-mertic-the-linux-foundation)
19 | * [Intelligent Open Source - Daniel Izquierdo, Bitergia & Jim Jagielski, Uber](https://ossna2020.sched.com/event/c3ZK/intelligent-open-source-daniel-izquierdo-bitergia-jim-jagielski-uber)
20 | *[Open Source on Purpose: Strategy, Process and Tools to Succeed - Kevin Nelson & Ben Woodring, UnitedHealth Group/Optum](https://ossna2020.sched.com/event/c3Pb/open-source-on-purpose-strategy-process-and-tools-to-succeed-kevin-nelson-ben-woodring-unitedhealth-groupoptum)
21 | * [BoF: The CHAOSS Project: Answering Specialized Questions About Community Health and Sustainability at Scale - Sean P. Goggins, University of Missouri](https://ossna2020.sched.com/event/c3Xy/bof-the-chaoss-project-answering-specialized-questions-about-community-health-and-sustainability-at-scale-sean-p-goggins-university-of-missouri)
22 | * [How to Keep Up with Open Source Innovation? - Alejandro del Castillo, National Instruments](https://ossna2020.sched.com/event/c3SJ/how-to-keep-up-with-open-source-innovation-alejandro-del-castillo-national-instruments)
23 |
24 |
25 | We hope you find these talks useful.
26 |
27 |
28 | If you're interested in starting an open source program or collaborating with your peers in open source program management, please consider [joining the TODO Group](http://todogroup.org/join/)!
29 |
--------------------------------------------------------------------------------
/static/img/todo-logo-on-black.svg:
--------------------------------------------------------------------------------
1 |
10 |
--------------------------------------------------------------------------------
/content/en/blog/survey-2019.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Open Source Program Management 2019 Survey Results"
3 | author: todogroup
4 | date: 2019-10-24
5 | ---
6 |
7 | The TODO Group is happy to announce the second annual Open Source Program Management Survey results that examines the prevalence and outcomes of open source programs among the Global Fortune 2000, including the key benefits and barriers to adoption. We have [open sourced all of our survey results and graphics](https://github.com/todogroup/survey/tree/master/2019).
8 |
9 | Key findings include:
10 |
11 | * **Adoption of open source programs and initiatives is widespread and goes beyond early adopters.** More than half (52%) of the 2,700 study participants either have a formal or informal program or their company is planning to create one, which is one percentage point less than last year. Despite tripling the study’s sample size, many of the study’s findings as well its demographic profile remained remarkably similar compared to last year. We see this as a validation of last year’s report.
12 | * **Expectations for open source program management have begun to crystalize.** Fostering an open source culture continues to be the top responsibility of these programs. However, the results show culture is less likely to be seen as a benefit when defined as interactions between departments as opposed to general digital transformation and agility. Compared to last year, facilitating the effective use of open source in commercial products and services rose from the fifth to the second most cited responsibility.
13 | * **Hiring of open source developers is a more prominent concern.** Mentions of developer recruitment and retention as a primary benefit of open source programs rose from 31% in 2018 to 36% in the latest study. Forty-two percent of companies planning a program say they are at least sometimes hiring developers to work on an open source project, up from 33% in 2018.
14 | * **Companies highly value their open source foundation memberships**. Of the 23% that are a member or sponsor of a foundation, 57% say their organization is getting high value from the investment; in contrast, only 7% are seeing low value.
15 | * **Code quality associated with open source software practices.** Forty-one percent of participants with OSS management initiatives say these programs are responsible for ensuring high quality and frequent releases to open source communities. In open-ended questions, many respondents discussed how code review processes instituted by OSS programs had a positive impact on code quality.
16 | * **There is no consensus about the impact of open source citizenship on buying decisions.** Twenty-nine percent say their perception of a company’s open source participation is very influential on their organization’s buying decisions but 32% say it is slightly or not at all influential.
17 |
18 | As an organization, we are committed to advancing the state of open source program management across the industry and will be performing this survey on an annual basis. We look forward to community feedback on this survey and how we can improve it in the future.
19 |
20 | If you're interested in starting an open source program or collaborating with your peers in open source program management, please consider [joining the TODO Group](http://todogroup.org/join/)!
21 |
--------------------------------------------------------------------------------
/content/en/blog/survey-2020.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Open Source Program Management 2020 Survey Results"
3 | author: todogroup
4 | date: 2020-08-04
5 | ---
6 |
7 | The TODO Group is happy to announce the third annual Open Source Program Management Survey results that examines the prevalence and outcomes of open source programs among the Global Fortune 2000, including the key benefits and barriers to adoption. We have [open sourced all of our survey results and graphics](https://github.com/todogroup/survey/tree/master/2020).
8 |
9 | Key findings include:
10 |
11 | * **Use of open source remains stable, and a new generation of companies are increasing their engagement with open source communities. The increased engagement is not because organizations with OSPOs are contributing more -- 72% contribute code upstream, which is practically identical to the 2018 results.** Instead, it is because organizations planning an OSPO are more likely to regularly create their own open projects, going from 35% in 2018 to 42% in 2020. Organizations planning an OSPO are also more likely to be influencing open source projects via leadership or maintainer roles, going from 18% to 24% over the last few years.
12 |
13 | * **Financial Services, Healthcare and Government all saw increased involvement with open source. Almost half (47%) of financial firms involved with the survey are contributing code upstream, a jump from 29% last year**. Healthcare and government organizations saw a similar increase, but these industry verticals are still less likely to have a formal policy governing use and contribution to open source.
14 |
15 | * **Large organizations are more likely to have open source policies, while smaller organizations look for help influencing the broader community. Seventy percent of respondents at an organization with over 1,000 employees have a formal policy governing the use of open source dependencies**. In contrast, only 49% of the 2-250 employee cohort have that type of policy. Compared to those with more than 1,000 employees, the smaller organizations are twice as likely to say the top benefits of operating an OSPO are lower licensing fees and support costs.
16 |
17 | * **The economy impacts existing open source program offices. In light of recent macroeconomic conditions, 37% believe funding for their initiative will increase in the upcoming fiscal year, while only 13% expect a decline**. This optimistic outlook is being driven by nimble, smaller organizations looking to save money using open source.
18 |
19 | * **The benefits of OSPOs and open source foundations continue to be appreciated. Compared to 2019, respondents are slightly less likely to say an open source program is critical to the success of their engineering or product teams, but 56% still say it is very or extremely critical for success.** Older programs are more valuable than younger ones, indicating that they have had success integrating into company processes.
20 |
21 | As an organization, we are committed to advancing the state of open source program management across the industry and will be performing this survey on an annual basis. We look forward to community feedback on this survey and how we can improve it in the future.
22 |
23 | If you're interested in starting an open source program or collaborating with your peers in open source program management, please consider [joining the TODO Group](http://todogroup.org/join/)!
24 |
--------------------------------------------------------------------------------
/content/en/ambassadors.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: TODO Ambassadors
3 | url: "/community/ambassadors/"
4 | ---
5 |
6 | TODO OSPO Ambassadors (TOAs) are official advocates within TODO helping the OSPO ecosystem.
7 |
8 | ## Responsibilities
9 |
10 | The TODO OSPO Ambassador Program encompasses a group of community leaders who provide support, training, mentorship, guidance, and rewards to:
11 |
12 | * Engage and enable the TODO community through local meetups, OSPOlogy meetings, OSPO content, and mentoring
13 | * Foster strong community collaboration and relationships
14 | * Attract and onboard new community participants
15 | * Provide valuable input and feedback to TODO about community programs and initiatives
16 | * Advocate OSPO best practices and TODO initiatives globally
17 |
18 | ## Requirements
19 |
20 | Program requirements for becoming an official TODO OSPO Ambassador are:
21 | * Must be 18 years of age or older
22 | * Must follow the [TODO Code Of Conduct](https://todogroup.org/code-of-conduct/)
23 | * Must comply with [LF antitrust policy](https://www.linuxfoundation.org/legal/antitrust-policy)
24 | * Must meet AT LEAST ONE of the following criteria:
25 | * An active contributor to a TODO initiative (OSPOlogy, OSPO Landscape, Website, OSPO Book, etc.)
26 | * A representative from a TODO General Member or OSPO Associate organization
27 | * An OSPO Local Organizer and/or OSPOlogy Organizer
28 | * An active leader in the TODO community with a minimum of 1 year of experience in:
29 | * Organizing events (virtual/in-person)
30 | * Speaking at events
31 | * Mentoring others
32 | * Creating content (e.g., blogs, videos, etc.)
33 |
34 | ## Benefits
35 |
36 | As a TOA, you are also eligible for Ambassador specific benefits, such as:
37 | * Gain recognition for your expertise and contributions to the community
38 | * Network with equally passionate Ambassadors globally
39 | * Receive support from the TODO and LF community platforms for hosting events, speaking, creating content, or mentoring others
40 | * Receive discount codes for you to attend LF-sponsored events
41 | * Enjoy exclusive swag and giveaways
42 | * Receive a TODO OSPO Ambassadors Credly badge issued by the Linux Foundation
43 |
44 | ## 🙋♀️ Frequently Asked Questions:
45 | ### What is the process for becoming an Ambassador?
46 | To become an Ambassador, an individual must review and meet the current requirements. We invite you to [submit your application for consideration](https://github.com/todogroup/governance/issues/new/choose) if you meet the requirements.
47 | ### Is the TODO OSPO Ambassador (TOAs) a paid position?
48 | No, the TODO OSPO Ambassador is not a paid position. However, TOAs will receive rewards like limited edition swag and exclusive discounts to LF events for their service.
49 |
50 | ### How long does my ambassadorship last?
51 | All ambassadorships will be a two-year commitment. For example, an Ambassador accepted in November 2023 will be an Ambassador until November 2025.
52 |
53 | ## Who do I contact with questions?
54 | For questions, please contact info@todogroup.org
55 |
56 |
57 | ## Attribution
58 |
59 | This Ambassador Program is adapted from the CNCF Ambassador Program, version 2.0, available at https://www.cncf.io/people/ambassadors/.
60 |
61 | > To make changes to this document, please [open a PR in TODO governance repo](https://github.com/todogroup/governance/blob/main/TODO-OSPO-Ambassador-Program.md).
62 |
--------------------------------------------------------------------------------
/content/en/blog/convince-manager-start-ospo.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: How to convince your manager to start an OSPO
3 | author: jlprat
4 | date: 2022-03-23
5 | ---
6 |
7 | _This time around we feature Josep Prat ([@jlprat](https://twitter.com/jlprat)) from [Aiven](https://aiven.io/) on how to convince your manager to start an OSPO at your company._
8 |
9 | Recently, I was asked by an ex-colleague to explain how they could convince management to create an OSPO at their company. This is a very interesting question, with several possible answers, that I think deserves a proper write down. Here’s my view on the matter:
10 |
11 | ## One Size Doesn't Fit All
12 |
13 | First of all, you need to find out which kind of Open Source Program Office you want/need.
14 | There are several focus areas for OSPOs:
15 |
16 | * Legal compliance
17 | * Generating OSS projects
18 | * Contributing to or (financially) supporting existing (external) OSS projects
19 |
20 | These are not discrete areas, as OSPOs do several of these at the same time. But more often than not, one of these different areas has more weight than the others in their mission.
21 |
22 | A good source of resources on how to set up an OSPO can be found under the [guides section](https://todogroup.org/guides/) in the TODO Group website. If you want to know more about how Aiven’s OSPO does it, tune to Aiven's [blog](https://aiven.io/blog) as I’ll be publishing an article on it real soon.
23 |
24 | ## Open Source At The Forefront
25 |
26 | We have reached a point where all companies rely on Open Source Software, and it's time for them to acknowledge this situation and act accordingly. We are all well aware of the latest security incidents that affected some well known OSS libraries. Incidents and bugs are bound to happen regularly, the important factor is not only to mitigate the impact of those but also how quickly we can react when a new incident or bug is detected.
27 | For this we need companies to not just be consumers of OSS, but also contributors of such projects. The more companies giving employees "company time" on OSS projects, the more secure, diverse, and healthy those communities will be.
28 |
29 | There is this Internet adage: "What if I train my employees and then they leave? --- What if you don’t, and they stay?". This is also true for OS. It's part of our infrastructure, products, and tooling, for this reason we need to care about them like if they were our own projects. No company will leave crucial parts of their in-house developed tech-stack unmaintained, why are we willing to do so for the ones that are Open Source?
30 |
31 | ## Reasons For Outbound OSPOs
32 |
33 | If you have some projects that could be Open Sourced (or already are), and/or like many others depend heavily on OSS, you might want to consider these arguments:
34 |
35 | We need a dedicated team to look after non-code aspects of our own OSS projects. Things like:
36 |
37 | * governance
38 | * project management
39 | * licensing
40 | * security
41 | * community engagement
42 | * developer education
43 |
44 | All these, and many others are crucial for the success of OSS projects.
45 |
46 | And with regards to contributing to external OSS projects, we need, as a company, to devote some of our employee’s work time to work on the critical OSS projects in our pipeline in order to:
47 |
48 | * guarantee a fast response in case of incidents
49 | * keep improving these projects
50 | * diversify the companies (if any) backing them up
51 | * remove maintenance burden
52 | * keep a healthy community
53 |
--------------------------------------------------------------------------------
/content/en/blog/sample-job-req.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: A Template Job Posting for Open Source Office Lead
3 | author: bvanevery
4 | date: 2016-05-25
5 | ---
6 |
7 | I ran into several folks this past week at OSCON who expressed a keen interest in creating a dedicated role for Open Source at their respective companies. So what was stopping them? One simple thing: every single one of them was struggling to define exactly what that role means. Instinctively we all have a feeling of what an employee dedicated to Open Source might do, but when it comes time to write it down or try to convince payroll, it can be challenging. Below I have included a starting point for a job description of what a dedicated Open Source manager might do. If you are in this boat, I'd highly recommend that you also check out the slides from our [talk at OSCON](http://todogroup.org/blog/oscon-talk/) this year. In addition, the many blog posts we've [published](http://todogroup.org/blog) about why our respective companies run Open Source.
8 |
9 | Also, on top of reusing what is below, we are collecting [open source office job descriptions](https://github.com/todogroup/job-descriptions) on GitHub from the industry that you can learn from.
10 |
11 | # The Job Posting
12 |
13 | *Side note: if you use this template, try running it through analysis on https://textio.com/talent/ first.*
14 |
15 | ## The Mission
16 |
17 | Our open source effort is currently lead by a multi-functional group of engineers and we are looking for a motivated, visionary individual to lead this effort and take Company Open Source to the next level.
18 |
19 | In this role, you'll work with our Engineering (Dev & Ops), Legal, Security, Business Ops, and Public Relations teams to help define what Open Source at Company means and build our open source community. Your day to day responsibilities will alternate between programming and several forms of program management. This is an exciting opportunity to work with all levels of the organization and leave a lasting impact here and on the engineering community at large.
20 |
21 | ## A good match might have (a)...
22 |
23 | * 8 years experience coding in or leading software engineering environments
24 | * Experience working on at least one successful and widely recognized open source project
25 | * Excellent communication and organizational skills
26 | * Familiarity with GitHub and open source CI tooling (Travis CI, Coveralls, etc)
27 | * Understanding of open source licenses
28 | * Experience and familiarity with multiple programming languages
29 | * Real passion for quality and continuous improvement
30 |
31 | ## Some things you might find yourself doing
32 |
33 | * You will lead and streamline all aspects of the outgoing open source process. This encompasses people processes to tooling automation.
34 | * You will own and handle our open source presence and reputation on GitHub and beyond
35 | * You will steer involvement and recognition of the open source program internally
36 | * You will work alongside product and business leadership to integrate Open Source goals with company goals. Overall, working to build Open Source mentality into our DNA.
37 | * You will build awareness of Company Open Source externally and increase overall involvement in the open source community.
38 | * You will establish Company as an actively contributing member of industry-leading Open Source initiatives. This involves taking active parts in TODO Group initiatives.
39 | * You will run our process for evaluating incoming open source code for use in our product.
40 |
--------------------------------------------------------------------------------
/content/en/blog/welcome.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Welcome!
3 | author: nzakas
4 | date: 2014-11-07
5 | ---
6 |
7 | A little over a month ago we announced the formation of the [TODO Group](http://todogroup.org), a group of companies coming together to collaborate on practices, tools, and other ways to run successful and effective open source projects and programs. The response we received was overwhelmingly positive, and we've been working hard since that time to clarify our goals and objectives as well as determine a path forward that includes as many companies as possible.
8 |
9 | ## Membership
10 |
11 | When we made our announcement, the initial members listed were:
12 |
13 | * [Box](http://opensource.box.com/)
14 | * [Dropbox](https://opensource.dropbox.com/)
15 | * [Facebook](https://code.facebook.com/projects/)
16 | * [GitHub](https://github.com/github)
17 | * [Google](https://developers.google.com/open-source/)
18 | * [Khan Academy](https://github.com/Khan)
19 | * [Square](http://corner.squareup.com)
20 | * [Stripe](https://github.com/stripe)
21 | * [Twitter](https://engineering.twitter.com/opensource)
22 | * [Walmart Labs](https://github.com/walmartlabs)
23 |
24 | In addition to these founding members, we've also added representatives from four companies that we've been engaged with since we started talking about forming TODO:
25 |
26 | * [IBM](https://ibm.github.io/)
27 | * [Intel](https://01.org)
28 | * [Microsoft](https://microsoft.github.io)
29 | * [Yahoo!](https://yahoo.github.io/)
30 |
31 | With these additions, we have representation from a good cross section of industry leaders in corporate open source.
32 |
33 | ## Community
34 |
35 | In addition to these members, we invited any interested companies to [participate](http://todogroup.org/join/), and we heard from over 700 companies within the first week. Due to the overwhelming response, we want to be sure we're extremely clear on our charter and operating principles, and how we are organized. To that end, we created our [Twitter account](https://twitter.com/todogroup) and this blog to better communicate with everyone, and setup a [mailing list](https://groups.google.com/group/todogroup) that companies can use to connect with each other to discuss open source.
36 |
37 | We are still working to more clearly define how membership works, and we'll be sharing those details as soon as we can.
38 |
39 | ## What's next?
40 |
41 | In the coming weeks, we'll be sharing more information on this blog. You can look forward to discussions of the legal areas of open source, how to build an open source community, what it takes to manage successful projects, and more. Some of the topics we have in mind include:
42 |
43 | * Why run an open source program?
44 | * Policies for launching new projects
45 | * Using external open source projects
46 | * Employee projects on their own time
47 | * Licenses, CLAs & other boilerplates
48 | * Interacting with your communities
49 | * Managing large open source portfolios
50 | * Metrics for success
51 | * The open source project lifecycle
52 | * Open source & corporate identities
53 | * What is the source of truth of truth?
54 |
55 | Longer-term, we'll be spending time curating best practices from our member companies to share with you as well as working directly with GitHub to create better tooling around corporate open source projects.
56 |
57 | We're very excited to get TODO Group up and running, and we look forward to further discussions about open source with the community.
58 |
59 |
60 | Nicholas C. Zakas, Principal Architect, Box
61 |
--------------------------------------------------------------------------------
/content/en/guides/todo-contribution-guidelines.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Open Source Program Office Case Study Guidelines
3 | ---
4 |
5 | The TODO OSPO Case Study initiative features real-world use cases and the impact OSPO Programs and open source are having on an organization.
6 | OSPO Use Cases build narratives around open source organization’s journey that includes Open Source Program Office highlighted activities, organizational structure,
7 | best practices, goals, and success stories, showcasing rganizations as leaders in the OSPO and open source management ecosystem.
8 |
9 | ## Requirements
10 |
11 | **Who can be featured in an OSPO Case Study?**
12 |
13 | As a rule, OSPO case studies feature:
14 |
15 | * Private and public organizations running an OSPO or an open source initiative
16 | * TODO Members
17 |
18 | All case studies must demonstrate at least one tangible business impact of OSPOs or open source management within the
19 | organization and/or the open source ecosystem. Examples from published case studies include:
20 |
21 | * Compliance, legal, and developer education
22 | * Evangelizing Open Source Culture and Usage
23 | * Hosting Open Source Projects
24 | * Growing Open Source Communities
25 | * Improving leadership and becoming a decision-making partner
26 | * OSPO or Open Source management Best practices (e.g tooling, documentation, etc)
27 |
28 | ## OSPO Case Study Process
29 | OSPO case studies follow a self-service model with editorial support and guidance provided by TODO Group and the Linux Foundation.
30 |
31 | The self-service follows a five-step process:
32 |
33 | **1. Proposal**
34 |
35 | Organizations submit a case study proposal via a Github Issue form
36 |
37 | IMPORTANT: This form is still in work in progress. Meanwhile, interested participants, please open an [issue](https://github.com/todogroup/todogroup.org/issues?q=is%3Aissue+is%3Aopen+label%3A%22use+case%22) using the 'use case' tag providing a description.
38 |
39 | **2. Review**
40 | * TODO steering committee team reviews proposal within 30 working days
41 | * If the proposal meets the criteria, the TODO PM sends a case study pack to the contact info provided
42 | * If the proposal doesn’t meet the criteria, TODO Program Manager will provide feedback and the organization is invited to resubmit.
43 |
44 | **3. Creation**
45 |
46 | Primary contact writes a case study following the required style documented in the case study pack
47 |
48 | **4. Editing**
49 | * TODO Group reviews the case study and makes any necessary edits as suggestions
50 | * Edits are based on the style guide.
51 | * Primary contact is welcome to make further edits or additions to the case study
52 | * Primary contact confirms when the draft is final and manages any approval processes
53 |
54 | **5. Publishing**
55 | * TODO and LF prepare the case study for publication
56 | * Primary Contact will receive a preview link, to view the case study before it goes live.
57 | * Case Study is published to todogroup.org and OSPO guide
58 | * Promotion cycle begins
59 |
60 | **6. Promotion**
61 | * Case studies are published on todogorup.org. TODO Group and LF market the case studies online, through social media, blog promotion, and the TODO OSPO newsletter.
62 |
63 | ## To get started
64 |
65 | Propose a case study and send it to the team directly by opening a [issue](https://github.com/todogroup/todogroup.org/issues?q=is%3Aissue+is%3Aopen+label%3A%22use+case%22) using the use case tag
66 |
67 | If you have any questions or feedback about the OSPO Case Study initiative, please send an email to info@todogroup.io.
68 |
--------------------------------------------------------------------------------
/content/en/blog/ospo-mind-map-2-release.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "OSPO Mind Map 2.0 release is out!"
3 | author: todogroup
4 | date: 2022-06-13
5 | ---
6 |
7 | TODO Group is proud to [announce a new OSPO Mind Map version](https://ospomindmap.todogroup.org/) release. The mind map shows a Open Source Program Office's (OSPO) responsibilities, roles, behavior, and team size within an organization. This post highlights the major improvements done by the community in this new version of the OSPO Mind Map.
8 |
9 | ## Updates on `Responsibilities` section
10 |
11 | OSPO Mind Map `Responsibilities` section has new OSPO-specific topics and different sub-sections defined, including:
12 |
13 | * 📘 Develop and Execute Open Source Strategy
14 |
15 | * 🧭 Eliminate Friction from Using and Contributing to Open Source
16 |
17 | * 🖥️ Manage Open Source IT Infrastructure
18 |
19 | * 📚 Give Advice on Open Source
20 |
21 | * 🫶 Grow and Retain Open Source Talent Inside the Organization
22 |
23 | * 🤝 Implement InnerSource Practices
24 |
25 | * ⏱️ Track Performance Metrics
26 |
27 | * 🤝 Collaborate with Open Source Organizations
28 |
29 | * 📈 Prioritize and Drive Open Source Upstream Development
30 |
31 | * 📝 Establish and Improve Open Source Policies and Processes
32 |
33 | * 🔍 Oversee Open Source Compliance
34 |
35 | * 📒 Support Corporate Development Activities
36 |
37 | Initial pull request with these changes can be found [here](https://github.com/todogroup/ospology/pull/111).
38 |
39 | **Welcoming Contributors 👋**
40 |
41 | The TODO Community welcomes more contributors to the OSPO mind Map to bring together the various communities involved in OSPO-specific topics. This will help to improve open source professionals' guidance across the OSPO ecosystem (e.g topics like "InnerSource", "Open Source metrics", "Open Source Compliance" and more).
42 |
43 | ## Updates on display
44 |
45 | Initially, the OSPO Mind Map displayed all sections by default, showing a huge mind map image. Now, when people access [https://ospomindmap.todogroup.org/](https://ospomindmap.todogroup.org/) the display view will only show the first 2 levels, so people can expand specific sections, avoiding unnecessary information and focusing on what matters to them at that time.
46 |
47 | 
48 |
49 |
50 | **Welcoming Contributors 👋**
51 |
52 | We are looking for tech contributors to work on a process to [automatically deploy new versions of OSPO mind map to the website](https://github.com/todogroup/ospology/issues/130). If you'd be interested to contribute, please open a [PR](https://github.com/todogroup/ospology/pulls)!
53 |
54 | ## About OSPO Mind Map and OSPOlogy
55 |
56 | This Mind Map is part of the TODO Group's [OSPOlogy repository](https://github.com/todogroup/ospology) which encapsulates a set of open initiatives (including the OSPO Mind Map, virtual global & regional meetings, an OSPO discussion forum, monthly OSPO News, and now, in-person workshops) to work in collaboration and study the status of OSPOs.
57 |
58 | ## Acknowledgments
59 |
60 | Thanks to OSPO Mind Map's v2.0 contributors and reviewers!
61 |
62 | - Thomas Steenbergen (EPAM)
63 | - Ana Jiménez (Linux Foundation)
64 | - Jari Koivisto
65 | - Josep Prat (Aiven)
66 | - Gergely Csatari (Nokia)
67 |
68 | Special thanks to Ibrahim Haddad (Linux Foundation), we were inspired by the _OSPO responsibilities_ section in [A Close Look at Open Source Program Offices: Structure, Roles and Responsibilities](https://github.com/ibrahimhaddad/publications/blob/master/Open%20Source%20Program%20Offices.pdf).
69 |
--------------------------------------------------------------------------------
/content/en/blog/ospo-expert-led-webinar-learnings.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Learnings from the OSPO expert-led panel on open source strategy & innovation"
3 | author: anajsana
4 | date: 2022-06-10
5 | ---
6 |
7 | On June, Thursday 9th I had the honor to be one of the panelists in the expert-led discussion *OSPOs in action*. The audience was able to learn from VMware, Comcast, Porsche, and Bloomberg's open source leaders to better understand the value of the OSPO, and where to get started. The aim of this article is to encapsulate my key learnings taken from the webinar, to help the open source community on their OSPO journey.
8 |
9 | ## Open Source Strategy & OSPO Key Learnings
10 |
11 | 🚀 **Starting an Open Source Program office means moving from open source ad-hoc to adopting a strategic posture around open source:**
12 |
13 | It is when the organization becomes conscious of the risks and innovation-related disadvantages that come with just using open source with no care nor strategic vission.
14 |
15 | 🧩 **Not every part of your organization is going to be ready for certain aspects of an open source strategy:**
16 |
17 | Thats where the OSPO can provide mentorship and act as the strategic partner to advise on how to make informed decision choices rather than accidental ones, adapted to specific profiles (from immature to more seasoned)
18 |
19 | 🤝 **Injecting open source into an organization's existing processes is a big challenge for any OSPO:**
20 |
21 | The panelists highlighted the importance of having a matrix of experts (e.g Porsche calls them *coordinators*, VMWare calls them *ambassadors*, Bloomberg calls them *guild leaders*, etc) to infuse the whole organization with a clear understanding of open source. This matrix of experts should be placed into the different teams or departments, so they act as the linchpin of the OSPO, translate its message, and answer questions on procedural aspects.
22 |
23 | 🧭 **Consider *Lead by Example* a key goal for OSPOs to build trust and thus better adopt open source within the entire organization:**
24 |
25 | To build trust within the organization across its different teams, groups or departments, OSPO members should be actively participating in open source projects and communities and have representation in the ecosystem.
26 |
27 | For folks willing to listen to the full discussion, the recording session is available on the [LF Youtube channel](https://youtu.be/Z10mYttHWfA) and [landing page](https://linuxfoundation.org/webinars/ospos-in-action/).
28 |
29 | ## What's next?
30 |
31 | The OSPOs in action webinar has been a space where open source leaders where able to share theirn learnings in an open and transparent way with the community, helping each other, and advancing together. Hoever, there was indeed a lot of questions from the audience that we couldn't cover in just one hour. [The TODO Group](https://todogroup.org/#) offers an open space and necessary tooling to preserve OSPO discussions and build new initiatives over the time. It is composed of an open community of practitioners, who aims create and share knowledge, and collaborate on practices, tools, and other ways to run successful and effective Open Source Program Offices or similar Open Source initiatives.
32 |
33 | With its 1,600+ community participants and [80+ general members](https://todogroup.org/members/) operating worldwide, TODO Group offers global and regional networking spaces, as well as a set of resources created by the community and seasoned OSPOers, to help more organizations advance in their OSPO journey.
34 |
35 | Our doors are open to everyone willing to learn more about OSPOs and Open Source Management. Please [join our community](https://todogroup.org/community/) and say hi!
36 |
--------------------------------------------------------------------------------
/content/en/blog/todo-track-at-collab-summit.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "TODO Track at the LF Collaboration Summit"
3 | author: todogroup
4 | date: 2016-04-05
5 | ---
6 |
7 | Last week, the TODO Group led a track at the [Collaboration Summit](http://events.linuxfoundation.org/events/collaboration-summit) which featured a variety of talks dedicated to open source program management.
8 |
9 | {{< tweet user="todogroup" id="715214451830460416" >}}
10 |
11 | Listed below are some of slides from TODO members given at the Collaboration Summit:
12 |
13 | Gil Yehuda ([@gyehuda](https://twitter.com/gyehuda)) runs the Open Source Programs Office (OSPO) at Yahoo and presented a talk highlighting some of the governance issues facing corporate based open source program offices. Gil made the case that medium to large tech companies need an OSPO. The tech industry acknowledges the ubiquity of open source in the corporate tech stack as well as in products, yet companies face governance issues that need to be addressed properly, consistently, and with goals in mind. He noted that Jim Zemlin ([@jzemlin](https://twitter.com/jzemlin)) lamented at the CollabSummit keynote that only about 30% of the tech companies surveyed had basic open source governance policies in place, let alone a mature process to manage their involvement in open source. The industry needs to improve this, since corporate contributions to open source are an increasingly important part of the ecosystem.
14 |
15 | Gil also focused on six of the most common aspects of governance. He detailed how an OSPO addresses inbound use of Open Source code, M&A deals, publication of code to existing projects as well as new open source projects, product review to ensure compliance of distributed code, and the abundance of employee generated questions that often come up related to copyright, work for hire, and code with unclear provenance. Gil's thesis was that an OSPO is essential to helping your company meet its open source goals and helps improve the overall quality of engineering too. He concluded with an invitation to reach out to us, the TODO Group, to help get started.
16 |
17 | {{< iframe src="https://www.slideshare.net/slideshow/embed_code/key/vTNvkwIXN4pmr8" >}}
18 |
19 | Brandon Keepers ([@bkeepers](https://twitter.com/bkeepers)) leads up open source efforts at GitHub and presented a talk about developing a maturity model for helping organizations embrace open source. The maturity model aims to provide a framework for helping everyone in an organization understand the benfits and challenges of consuming, contributing to, and releasing open source software.
20 |
21 | Christine Abernathy ([@abernathyca](https://twitter.com/abernathyca)) from the Facebook Open Source Office shared lessons from the community building strategies used at Facebook to manage some of the most successful Open Source projects. She also shared how Facebook uses their metrics dashboard and many tools (that are open sourced) to manage and report on activity in their open source communities.
22 |
23 | Guy Martin from the Autodesk OSPO discussed his experiences in addressing cultural and process issues before choosing a collaboration tool solution:
24 |
25 | {{< iframe src="https://www.slideshare.net/slideshow/embed_code/key/p3tfnyJCiv07RO" >}}
26 |
27 | Jeff McAffer ([@jeffmcaffer](https://twitter.com/jeffmcaffer)) from the Microsoft OSPO presented a talk about how Microsoft uses GHTorrent along with Microsoft's DataLake infrastructure to get important data analytics from Github. Jeff walked through real-world examples (using live data) to show how researchers and community managers can use Github's wealth of data to help make better decisions about managing projects and addressing issues. He then showed how you can leverage the same for your projects too.
28 |
29 | We hope you find these talks useful and you can find more presentations from the Collaboration Summit [online](http://events.linuxfoundation.org/events/collaboration-summit/program/slides).
30 |
--------------------------------------------------------------------------------
/content/en/blog/2023-ospo-survey-call-for-partners.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Announcing the 2023 OSPO Survey Call For Partners"
3 | author: todogroup
4 | date: 2023-03-15
5 | ---
6 |
7 | The TODO Group, together with Linux Foundation Research, is conducting a survey as part of a research project on the prevalence and outcomes of open source
8 | programs among different organizations across the globe. Open source program offices ([OSPOs](https://github.com/todogroup/ospodefinition.org)) help set open source strategies, policies and processes to
9 | streamline open source operations within organizations. Since 2018, the TODO Group has conducted surveys to assess the state of open source programs worldwide
10 | (all raw data, questionnaire, results and insights are available to everyone in the [OSPO Survey Repo](https://github.com/todogroup/osposurvey)).
11 | Today, we are pleased to announce the launch of the 2023 edition.
12 |
13 |
14 | The 2023 survey will generate insights into the following areas:
15 | * **Adoption and impact of OSPOs across sectors and industries,**
16 | including perceived benefits and challenges of open source offices and trends in hiring for open source development.
17 | * **Balancing openness and control in OSPOs,** including strategies for encouraging contribution and participation, providing education on open source best practices, and scaling open source operations within organizations.
18 | * **Security and sustainability of open source ecosystems,**
19 | including how OSPOs contribute to building more secure software and software supply chains, and how they
20 | enable long-term sustainable ecosystems by aligning organizational goals with open source goals and engaging stakeholders, teams, and executives.
21 | * **Industry or geographical segmentation,** including additional survey questions to gain insight into
22 | specific regions or industries (e.g., OSPOs in finance, OSPOs in Japan).
23 |
24 | The topic areas listed above are based on feedback that community members provided throughout the year, whether on GitHub, at conferences, or in meetings. The target sample for this survey is OSPO leaders.
25 |
26 | The results of this survey can help open source professionals gain a better understanding of the status and role of OSPOs within organizations.
27 | The target readership is likely to be involved in open source at some level and has a direct relationship with OSPO roles, either as a member
28 | of an OSPO or as someone who works closely with an OSPO. The survey is also relevant for those who are likely to have a close relationship
29 | with an OSPO in the future, such as managers, executives, policy makers and other decision-makers involved in open source initiatives.
30 |
31 | ## 🙋♀️ Become a partner in this research!
32 | We are seeking help from organizations to facilitate survey outreach, generate sample, and maximize impact of this research through partnership.
33 | There is NO monetary commitment.
34 |
35 | Partners support the project through:
36 |
37 | * Sharing the survey to their networks via main communication channels
38 | * Promoting the survey and final deliverables on social media channels
39 | * Partners also have the opportunity to engage with the third core topic listed above and suggest a segmentation that they are interested in,
40 | and work with the survey development team to design survey questions. This would involve a monetary commitment.
41 |
42 | As a partner, you will be included as an active collaborator in the survey. Both organizations
43 | and open source projects are welcome to become partners for the next OSPO survey. This includes, but is not limited to, corporations,
44 | foundations, non-profits, government agencies, universities, and representatives from open source projects.
45 |
46 | To participate, please contact *hcarter@linuxfoundation.org*.
47 |
48 | ### 📆 Timeline:
49 |
50 | * April 2023: kick-off and survey development
51 | * May 2023: survey in field
52 | * May-June 2023: data analysis and presentation of results
53 | * June-July 2023: report drafting
54 | * August 2023: report production
55 | * September 2023: publication
56 |
57 |
58 |
59 |
--------------------------------------------------------------------------------
/content/en/blog/Announcing-the-evolution-of-OSPO.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Announcing The evolution of OSPO featuring case studies from Bloomberg, Comcast, and Porsche"
3 | author: todogroup
4 | date: 2022-02-25
5 | ---
6 |
7 |
8 | More than a couple of decades into the OSPO movement, the role of the OSPO and similar open source initiatives have grown to become a
9 | central source of expertise and a strong voice in developing and implementing technology strategy at the world’s forward-thinking companies. The TODO Group, in collaboration with Linux Foundation Research, is pleased to release a new whitepaper, The Evolution of the Open Source Program Office. We hope this work provides guidance and a way to better frame and visualize the OSPO ecosystem complexity and provide a roadmap to ease OSPO planning and adoption
10 |
11 | The Evolution of OSPOs provides a set of patterns and directions, as well as a checklist, to help implement an OSPO or an open source initiative within
12 | corporate environments. This includes an OSPO maturity model, practical implementation from noted OSPO programs across regions and sectors, and a handful
13 | of broad OSPO archetypes, which drive differentiation in OSPO behavior.
14 |
15 | To gain more qualitative insights into [how OSPOs were evolving](https://github.com/todogroup/osposurvey#open-source-programs-survey), we interviewed leaders of noted OSPO programs, including some of the most influential technology firms, such as Red Hat, Microsoft, and VMware, as well as some of the most iconic transportation brands and one of the largest media and entertainment companies. Also, people will be able to learn from different OSPO case studies in three different sectors (media, financial services, and transportation) each case is structured as a journey through the stages of the OSPO.
16 |
17 |
18 | We welcome the open source community to contribute and collaborate to these resources, expanding the initial archetype scope or improving the
19 | documentation for each of the stages. Everyone is welcome to join our [TODO work day calls](https://github.com/todogroup/work-day-activities#work-day-activity-tracker) or present new ideas and discussions for upcomming [OSPOlogy community meetings](https://github.com/todogroup/ospology/tree/main/meetings#ospology-monthly-meetings). People can also open a new discussion in the [OSPO forum](https://github.com/todogroup/ospology/discussions).We are open!
20 |
21 | Last but not least, big thanks to the sponsors and to all the participants in this study who generously spent time speaking with us and reviewing sections
22 | of the report:
23 |
24 | * [Nithya Ruff](https://www.linkedin.com/in/nithyaruff/) (Comcast)
25 | * [Deborah Bryant](https://www.linkedin.com/in/opengovernment/) (RedHat)
26 | * [Chris Xie](https://www.linkedin.com/in/chrisxie-us/) (Futurewei Technologies, Inc.)
27 | * [Dirk Riehle](https://www.linkedin.com/in/dirkriehle/) (University of Erlangen)
28 | * [Kevin Fleming](https://www.linkedin.com/in/kpfleming/) (former at Bloomberg)
29 | * [Alyssa Wright](https://www.linkedin.com/in/alyssapwright/) (Bloomberg)
30 | * [Stormy Peters](https://www.linkedin.com/in/stormy/) (former at Microsoft)
31 | * [Suzanne Ambiel](https://www.linkedin.com/in/suzanne-ambiel-a77807/) (VMWare)
32 | * [Nik Peters](https://www.linkedin.com/in/nik-peters-95a30a131/) (Porsche)
33 | * [Michael Picht](https://www.linkedin.com/in/michael-picht-249b7a149/) (SAP)
34 | * [Peter Giese](https://www.linkedin.com/in/peter-giese/) (SAP)
35 |
36 | This report would not have been possible without [Alex Salkever](https://www.linkedin.com/in/alexsalkever/), who skillfully led the research and writing effort, and TODO Group’s [Ana Jiménez Santamaría](https://www.linkedin.com/in/ana-jim%C3%A9nez-santamar%C3%ADa/), for helping with project design and outreach.
37 |
38 | Last but not least, we would also like to thank Comcast, Bloomberg, and Porsche for their help and advice in the whitepaper's case studies, as well as VMware for its sponsorship of this research.
39 |
40 |
41 | * **Read the LF article [here](https://www.linuxfoundation.org/blog/leveraging-the-open-source-program-office-new-research-unpacks-the-evolution-of-the-ospo-and-a-whole-lot-more/)**
42 | * **Download the full study [here](https://linuxfoundation.org/tools/the-evolution-of-the-open-source-program-office-ospo/).**
43 |
--------------------------------------------------------------------------------
71 |
89 |
72 |
73 |
77 | 
86 |
87 |
88 |
86 |
87 |