todogroup / ospology Goto Github PK

We can create a new document that covers OSPONews guidelines to let the community know what can be included in the newsletter

Session Title

How to automate your FOSS policy and processes

Session Description

If you look at the OSPO mind map you will see an OSPO may have a lots of responsibilities such as "establish and improve Open Source processes", "oversee Open Source compliance", "eliminate friction from using and contributing to Open Source". Yet a lot of OSPOs only have a few people working on these responsibilities especially those who just started their OSPO. How do scale your OSPO with a small team?

Automation is the answer, but that raises the question which tools to use for which use cases. In this session Thomas will show how several OSPOs have been working together to create open source tooling to automate their FOSS policies and processes. He will demonstrates a reference processes for how one can automate 'oversee Open Source Compliance' and 'Publishing a new open source project' from start to finish and some of lessons he learned on automation over the years.

Benefits to the Ecosystem

You will learn:

• How you can automate your FOSS policy and processes by re-using the tooling, data and policy rules created by collaboration between several OSPOs under the Linux Foundation.
• How you can make your policy and process simpler thereby making the life easier of your organization's developers whilst keeping your legal counsel happy and can contribute to improve licensing/security in the FOSS community.
• What should be in your FOSS policy document and what not

Help us narrow down the focus a bit more. Please choose the OSPO related topic that best describes your proposal.

Adoption and Discovery, Compliance, Legal Developer Education, and Inventory, Evangelizing OSS Use and Ecosystem Participation

What level of experience should the audience have to best understand your presentation?

OSPO 101 (Beginner)

Speaker Name

Thomas Steenbergen

Speaker Bio

Thomas Steenbergen is the Head of Open Source Program Office at EPAM Systems (www.epam.com). He is steering committee member and one of the co-founders/organizers of the European Chapter of the TODO group and co-founder of the OpenChain Reference Tooling Work Group - both industry working groups where companies collaborate to address shared open source challenges. He is also an active contributor to the SPDX ISO specification for over 5 years, helping to better match what developers find in code and incorporate security (lead Security Profile).

As a core contributor to the OSS Review Toolkit, he enables highly automated open source policy checks in CI/CD by providing easy, open-source & scalable tooling and to share results in open standard (SBoM) formats. He is a frequent speaker and panellist at various global open source conferences and is always happy to start a conversation around anything open source. Thomas has held a variety of technical lead roles over the past 15 years across the Netherlands, United Kingdom and Germany.

Speaker preferred pronouns

he/him

Hi Gang,

May I suggest rendering SVG/PNG/PDF with tooling instead of uploading a text file to a website and saving the results?

The developer that wrote that specific website's code is here:
https://gitlab.com/raibis/text2mm

A different option that may or may not be merged into mermaid is here:
https://markmap.js.org/docs#markmap-view

You can view the website, and that markmap-view code appears to generate SVGs.

Create a CFP g.form to submit OSPOlogy topics and make it easier to share on SM channels. The form should include:

• Session Topic
• Abstract
• Benefits for the OSPO Ecosystem
• Speaker(s)
• Short bio
• Speaker's Email info

Inspired by Kubernetes community doc: create a doc that outlines the various responsibilities of contributor roles in OSPOlogy, and clarifies how people can make their way up the OSPOlogy contributor ladder

Following is an example of how to be a good open source community citizen when transitioning from open source model to closed-source model:
In some cases, an open source company may decide to switch to a closed-source model, abandoning the open source community and making its software proprietary. This can be a difficult decision for a company to make, and it requires careful planning and preparation. So, how a company should prepare for an open source company turned non-open source.
Communicate Clearly with the Community
One of the most important things that an open source company should do when transitioning to a closed-source model is to communicate clearly with the open source community. The company should be transparent about its decision to switch to a closed-source model, and it should provide clear reasons for doing so. The company should also provide a timeline for the transition and should explain how the transition will affect the open source community.
Protect the Community
An open source company has a responsibility to the community that has supported its software. When transitioning to a closed-source model, the company should take steps to protect the community. This may involve releasing the software under a permissive license, allowing the community to fork the project and continue development independently, or providing access to the source code for a limited time.
Ensure Continuity of Support
When transitioning to a closed-source model, the company should ensure that existing customers and users of the software will continue to receive support. This may involve providing a transition plan, offering incentives for users to switch to a new product, or providing access to support for a limited time.
Maintain Quality
When transitioning to a closed-source model, the company should ensure that the quality of the software remains high. This may involve hiring additional developers, investing in new technology, or providing training to employees. The company should also ensure that its closed-source product is fully tested and stable before releasing it to customers.
Develop a New Business Model
Transitioning to a closed-source model may require a new business model. The company should carefully consider its revenue streams and develop a strategy for generating revenue from its closed-source software. This may involve offering support and services, licensing the software to other businesses, or developing a subscription model.

Session Title

A Legal Guide To Open Works

Session Description

Films, music, buildings, sketches, speeches, documents, books, comics, software, all these works have in common the law that protects them.

All intellectual creations are proprietary by default, however, authors can grant the public permission to use their creative work under copyright law, and the authors can use open licenses to make their content available to everyone.

To make this task easier, Amtega (The Agency for Technological Modernization of Galicia) has created a guide to release both content and software legally.

Benefits to the Ecosystem

Learn how to deal with open licenses, how to choose them or how to apply them

Help us narrow down the focus a bit more. Please choose the OSPO related topic that best describes your proposal.

Compliance, Legal Developer Education, and Inventory

What level of experience should the audience have to best understand your presentation?

OSPO 101 (Beginner)

Speaker Name

• Marelisa Blanco
• Bárbara Román

Speaker Bio

• Marelisa Blanco: comic artist; lawyer; copyright professor at the Universidad Europea, U-Tad, and LCI Barcelona.

• Bárbara Román: Lawyer; CEO Nolegaltech.

Speaker preferred pronouns

She / They

Session Title

Growing Open Source Culture Inside Sony

Session Description

This session shares challenges and efforts as an Open Source Program Office (OSPO) to grow open source culture within Sony.
The challenges have been building the open-source program, growing the open-source culture within Sony, and learning how to collaborate with OSS communities.​

After Sony started using Linux in products in the early 2000s, Sony built its open-source program from the point of view of technology and OSS licenses and Sony’s relationship with OSS communities.​
OSS license committee consists of business unit representatives, including R&D, the legal department, and the IP department.
This committee promotes open-source culture by sharing policy and guidelines, hosting internal events, and training.​
Sony contributes to growing communities in the embedded systems area.
Since its early days, through our community liaison staff (who are members of the Linux development community), we communicated with the community, made contributions to the kernel and other projects, and helped establish the Embedded Linux Conference, and worked with others to enhance this community.​ ​

This session will explain these three challenges and how Sony has worked to foster a culture of acceptance, involvement, and education of Open Source within Sony through our OSPO.​

Benefits to the Ecosystem

This session shares challenges and efforts as an Open Source Program Office (OSPO) to grow open source culture within the embedded product industry. The challenges have been building the open-source program, growing the open-source culture within a company, and learning how to collaborate with OSS communities.​

This session shows the open-source program is built from the point of view of technology and OSS licenses and relationship with OSS communities. Listener can understand the importance of relation between business and OSPO.

This session gives listeners hints for growing culture inside a company.

Help us narrow down the focus a bit more. Please choose the OSPO related topic that best describes your proposal.

Evangelizing OSS Use and Ecosystem Participation

What level of experience should the audience have to best understand your presentation?

OSPO 101 (Beginner)

Speaker Name

Kazumi Sato and Hiroyuki Fukuchi (Sony Group Corporation)

Speaker Bio

Kazumi Sato
Sony Group Corporation
Distinguished Engineer
Kazumi SATO is a Distinguished Engineer in Sony. He is working on Linux-based system software for various Sony products. He is also working on OSS compliance and relationship with communities in Sony. Since 2002, when Sony started to use Linux, he leads system software development using Linux and introduces it to the products, complying with the OSS licenses. He is a member of the Software

Hiroyuki Fukuchi
Sony Group Corporation
Senior Alliance Manager
Hiroyuki FUKUCHI is Senior Alliance Manager in Sony. He is working on OSS compliance and relationship with OSS communities. He is the leader of the planning subgroup of the OpenChain Japan workgroup. He is a speaker at Open Source Summit Europe 2019, regarding building a reginal community. He is an English-Japanese translation volunteer regarding OSS community related document, such as OpenChain and SPDX specification.

Speaker preferred pronouns

Please add your preferred pronouns, if any (e.g She/ Her, They/ Them)

@koozz just noticed that when merged your PR: #306 GitHub actions drops the following error when trying to generate the pdf 🤔:

pandoc: ospo-book/chapters/*.md: openBinaryFile: does not exist (No such file or directory)

Chapter 2 currently has separate sections about the reasons to start and OSPO and to sustain it.

I perceive that as confusing. An OSPO as an organizational structure is inherently meant to be a permanent thing. Its responsibilities such as managing compliance, mitigating security risks, or connecting to the open source community are all long-term activities without a defined end. So I can't really think of a scenario where it makes sense to start an OSPO without sustaining it.

It would be clearer to combine the sections into one, maybe under the title "Reasons for having an OSPO" or something like that.

Part of the confusion might actually come from the misnomer of Open Source Program Office. A program mostly has a natural end and the term is often used in organizations to name time-limited initiatives. So having this as part of the name might create wrong assumptions. This part of the confusion I would rather address in a clarification of the naming of an OSPO-like organizational structure than letting it structure the reasoning for having an OSPO.

As per the TOC

Markdown file

Title

"Measuring the success and impact of your OSPO"

Outline

• Discuss the value and process of aligning open source strategy goals with metrics.
• Explore different aspects of measuring open source impact within the organization and organization’s help and support across open source projects and their communities.
• Introduce the Goal-Question-Metric (GQM) approach for assessing OSPO success and the work done in CHAOSS.
• Identify common scenarios and recommendations.
• Present a use case showcasing the successful measurement of OSPO impact in the organization and open source projects & communities.

Sections

• #473
• #474
• #475
• #476

Discussing the mind map with @dwjobling, he raised that there isn't a top-level activity to "measure value."
Because of this, performance metrics assume that the activity is valuable and valued but doesn't directly measure whether an activity an OSPO is running is worthwhile doing. (David's observation, I can't take credit!)

I think this is a valuable observation because it differs from community engagement and upstream impact; I'd propose that we have a top-level activity of measure value, which could include the impact on employees, return on investment, community engagement, reuse and productivity, reducing cost, reducing business risk (thinking back to Taylor English's OSPOCon 2021 talk), community goodwill, marketing, and compliance.

If people agreed, happy to support with a PR.

Deploy the mind map Japanese version: https://github.com/todogroup/ospology/blob/main/ospo-mindmap/Content/ospomindmap_jp.md under https://ospomindmap.todogroup.org/jp

Session Title

The strategy and ideas behind the Spotify FOSS Fund

Session Description

In Q1 of 2022 we decided to establish a FOSS fund. In this presentation I will cover what the practical challenges was and what underlying assumptions, ideas and strategy brought us to this decision.

Benefits to the Ecosystem

The session presents our strategic thinking behind establishing a FOSS fund and attempts to go beyond the premise of "because its the right thing to do" but rather focuses on why it from a business objective makes sense to do what we did.

Help us narrow down the focus a bit more. Please choose the OSPO related topic that best describes your proposal.

Evangelizing OSS Use and Ecosystem Participation

What level of experience should the audience have to best understand your presentation?

No response

Speaker Name

Per Ploug

Speaker Bio

After 10 years in building an open source tech company, I switched to working in big tech companies. First at Zalando
establishing their open source team, later as head of their product security, and now at Spotify where I lead the OSPO.

Speaker preferred pronouns

he/him

Once a pull request updating the OSPO mind map is merged it should be automatically deployed to https://ospomindmap.todogroup.org/

Chapter 2 currently has two appendices in the middle of its text (Appendix A and Appendix B). This hurts the reading flow a bit. I would suggest to move these appendices to an own chapter about OSPOs in public administrations.

Discussion from the APAC / EMEA contributors call. Anti-patterns might be a very strong word

• https://en.wikipedia.org/wiki/Crossing_the_Chasm
• https://en.wikipedia.org/wiki/Crossing_the_Chasm#/media/File:Technology-Adoption-Lifecycle.png

Embajador ospo mexico

Originally posted by @Blackheart2 in #305 (comment)

The Good Governance Handbook of the OSPO Alliance has a very good list of activities of an OSPO. This includes progress assessments and recommendations. It feels like this would be pretty much the content of the chapter 4 of the OSPO book. Could we find a way to reference that instead of creating another independent list of activities which overlaps a lot with the already existing list?

As per the TOC

Title

"Measuring the success and impact of your OSPO"

Outline

• Discuss the value and process of aligning open source strategy goals with metrics.
• Explore different aspects of measuring open source impact within the organization and organization’s help and support across open source projects and their communities.
• Introduce the Goal-Question-Metric (GQM) approach for assessing OSPO success and the work done in CHAOSS.
• Identify common scenarios and recommendations.
• Present a use case showcasing the successful measurement of OSPO impact in the organization and open source projects & communities.

Sections

• #469
• #470
• #471
• #472

Session Title

Disclaimer: This is not a session yet. It's a topic suggestion. I don't have to be the person to tell it. I'm currently involved in the exact topic and would love to share, but also learn from others.
https://dev.to/postman/how-postmans-building-their-open-source-program-office-ospo-hgf

"Building an OSPO around existing Open Source involvements"

Session Description

Your company is already in the Open Source game? There's contributors and maintainers that get paid to do their job on an Open Source project? But there's a disconnect and unclarity why your company does this and on what terms contributing to Open Source is welcomed or permitted?
Having an Open Source Program Office can be a solution. But there's challenges when you can't start from scratch, and there is already some sort of structure in place. Hear them in this real life story of creating the OSPO at Postman.

Benefits to the Ecosystem

Learn about others' challenges along the road of creating an OSPO at your company.
Handle existing relationships and structures, manage change.

Help us narrow down the focus a bit more. Please choose the OSPO related topic that best describes your proposal.

Adoption and Discovery, Becoming Strategic Decision-Making Partner

What level of experience should the audience have to best understand your presentation?

OSPO 101 (Beginner)

Speaker Name

Jan Schenk

Speaker Bio

Program manager; tech community lover; Open Source advocate; Diversity, Equity, Inclusion and Belonging activist. I spent the majority of my life in the Tech Industry.

Speaker preferred pronouns

He/They

Hi,

in the OSPO Book, there are many links to Linux Foundation (lf) content. But these are inconsistent, I found 3 patterns:

1. a link is to the lf website, example in {1},
2. a direct link to a pdf on the lf website, example in {2},
3. an external link to a pdf, example in {3}.

And about {2}, there is another way to link to that content in {4}.

I would suggest to always use the #1 pattern above, and I will submit a PR to fix #2 and #3.

Thanks, Jean-François Gagné

{1}:

[the OSPO maturity model](https://linuxfoundation.org/tools/the-evolution-of-the-open-source-program-office-ospo/)

{2}:

[business value of the OSPO report](https://project.linuxfoundation.org/hubfs/LF%20Research/TODO%20Group%20-%20The%20Business%20Value%20of%20the%20OSPO%20-%20Report.pdf?hsLang=en)

{3}:

[This report by Dr. Ibrahim H](https://8112310.fs1.hubspotusercontent-na1.net/hubfs/8112310/LF%20Research/LF%20Research%20Guide%20to%20Enterprise%20Open%20Source.pdf)

{4}:

[The Business Value of the OSPO](https://www.linuxfoundation.org/research/business-value-of-ospo)

The book contains a copy of the OSPO definition. From https://github.com/todogroup/ospodefinition.org. Instead of copying the text I would suggest to add just one sentence as a summary of the definition and link to the detailed definition at https://ospodefinition.org instead of duplicating the full text.

I propose adding a markdown linter as a GitHub action to the repository, for instance the GitHub SuperLinter [1]. Initially, the linter would only check the book, but depending on our experiences with it, we can extend it to the entire repository.

[1] https://github.com/super-linter/super-linter

At the moment in the mind map we have developer education in two places:

• Responsibilities - Oversee Open Source Compliance - Educate Developers - Training & Certification
• Responsibilities - Establish and Improve Open Source Policies and Processes - Processes - Educating people

These have a bit different flavors but are still close to each other and in order to make the mind map a tiny bit less complex, these two could be merged.

The top level readme is a little difficult to read.

Specifically

• switch communication to active voice
• improve the organization of sections.
• remove conjunctions.
• add emojis to look hip!

In the "Upcoming Conferences and Call for Papers" section of OSPOlogy, it's not clear which are simply upcoming events and which have an active CfP (or maybe there are no active CfPs in the latest issue). It would help the reader to list these separately so that it's more obvious at a glance what has an open CfP and what doesn't.

Hi @anajsana

Today in the CHAOSS Metrics WG meeting, we were talking about a book chapter that we could possibly work on. While we have a few ideas, we were wondering if there is an overarching framework for the book -- a set of chapters that you are hoping to have. The reason that this was asked is because as we were framing a chapter, we were wondering "is this being covered in another chapter?" and "are there frameworks from other chapters that we could leverage?"

The chapter possibility that we were discussion was around Demonstrating OSPO Value and how metrics can play a part in that process. As part of this discussion, we were thinking that the chapter might start with a discussion of how it is important to address the following questions:

What is the overall strategy of your organization?
How is your OSPO aligned with this strategy?

However, if these questions are addressed in other chapters, we don't want to repeat or create confusion. From these questions, we can discuss metrics that can demonstrate this alignment and subsequently how to talk about that alignment throughout an organization.

To preview the final outcomes of each PR from the ospo book, we are using GitBook.

However, this is done manually at this moment and is needed to work on automation that allows visualize a preview when submitting PRs directly to the gitbook: https://www.gitbook.com

The table of content contains the list of chapters and some notes about their content. It would be good to link the entries in the table of content to the actual chapters.

I'm not sure how to do this with hugo in a way that it shows up on the generated site correctly. If you have a hint for me how to do it, I can also come up with a pull request.

For the chapters which aren't completed yet there is no content on the generated site yet. So it would be good to add a note that it is work in progress instead of the link.

Session Title

3rd Party Outbound OSPO: An extrospective approach to OSS

Session Description

An entire department, working in the open, focusing on other companies’ Open Source repositories… sounds like something unthinkable, right? Well… except is not, and I’m here to tell you the story of the OSPO team at Aiven, whose main mission is to contribute and guarantee the sustainability of external OSS projects.

The most common and widespread way to support OSS communities takes the form of donations. Money donations are a good way to secure projects financially, however, you can rarely foresee their impact on the community. On top of that, in some cases, money is just a palliative, and will not prevent contributors with a day to day job from burning out. We think an alternative exists, where, instead of money, companies donate employees' time to directly work on existing critical OSS projects.

Learn from Aiven’s experience building their OSPO, and how it impacts mission, scope, hiring, team composition, and metrics definitions.

We will share the benefits that the company is experiencing as well as direct examples of how our OSPO is improving the sustainability of various OSS communities. But the roads of our project were seldom perfect, and we'll discuss pitfalls and areas to watch out for, so you know them in advance when building your own Outbound OSPO focusing on 3rd party OSS.

Benefits to the Ecosystem

You will learn:

• an Innovative way of doing OSPOs
• when it’s good and when it’s not
• how it can improve the global OSS ecosystem
• how to measure success
• how recruiting changes
• how fragile OSS communities and projects can benefit from more companies adopting the new approach

Help us narrow down the focus a bit more. Please choose the OSPO related topic that best describes your proposal.

Adoption and Discovery, Evangelizing OSS Use and Ecosystem Participation

What level of experience should the audience have to best understand your presentation?

OSPO 101 (Beginner)

Speaker Name

Josep Prat

Speaker Bio

Josep Prat is a Open Source Software Manager at Aiven and is passionate about Open Source Technologies. With a strong background in Scala and distributed systems, he contributes to several Open Source Projects like Kafka and Akka, and is a committer for Akka HTTP. In his spare time, Josep enjoys late and long brunches on Sundays, kids permitting.

Speaker preferred pronouns

He/Him

Session Title

How Academic OSPOs Are Amplifying Research Impact … and How Industry OSPOs Can Benefit
Please provide more details about your proposal

Session Description

OSPOs in academia need to be in alignment with the missions of universities, including teaching, research, and public service. These missions are very different from the missions of industrial corporations. But the strategic goals of both academic and industry OSPOs are complementary and enable acceleration of innovation that benefits all stakeholders. In this presentation we will provide an overview of the efforts being made at UC Santa Cruz to amplify the impact of academic research by leveraging open source ecosystems, and how these activities are opening opportunities that can benefit industry partners – both through the engagement with university researchers and the education of the next generation of technical professionals.

Benefits to the Ecosystem

The audience will learn about:

• Efforts to support academic research based in open source ecosystems that align with industry practices;
• Development of innovative curricula and mentoring programs that teach open source techniques to the next generation of technical professionals; and
• How industry OSPOs and the wider open source community can support these efforts and benefit from their outcomes.

Help us narrow down the focus a bit more. Please choose the OSPO related topic that best describes your proposal.

Evangelizing OSS Use and Ecosystem Participation, Hosting OSS Projects and Growing Communities

What level of experience should the audience have to best understand your presentation?

No response

Speaker Name

Carlos Maltzahn and Stephanie Lieggi

Speaker Bio

Carlos Maltzahn is the founding director for the Center for Research in Open Source Software (cross.ucsc.edu) and the new UC Santa Cruz OSPO. He is an Adjunct Professor of Computer Science & Engineering at UC Santa Cruz, a co-founder of the Ceph open source distributed storage system project, and co-founded the Systems Research Lab, known for its cutting-edge work on programmable storage systems, big data storage & processing, scalable data management, distributed system performance management, and practical reproducible evaluation of computer systems. Prior to joining UCSC, he was a Performance Engineer, Netapp. (see people.ucsc.edu/carlosm)

Stephanie Lieggi is assistant director for CROSS and the UC Santa Cruz OSPO. In her current roles she supports the work of academic-based open source projects and enables a sustainable contributor base through the establishment of hands-on mentorship programs. Stephanie promotes the use of open source in academic settings as well as increasing diversity and inclusion in open source ecosystems. Prior to joining UCSC, she was a Senior Research Associate and Adjunct Professor at the Center for Nonproliferation Studies (CNS) at the Middlebury Institute of International Studies at Monterey (MIIS).

Speaker preferred pronouns

Carlos Maltzahn (he, him)
Stephanie Lieggi (she, her)

Based on a previous discussion to render SVG/PNG/PDF with tooling instead of uploading a text file to the repo, we have considered migrating to markmap to continue to build the OSPO mindmap.

Action Items

• Create ospomindmap.md and change it for OSPO_Mind_Map.txt via PR
• Update documentation (https://markmap.js.org/docs#what-is-markmap) and submitt PR

The OSPO Book contains a glossary. Its content is mostly the same as the OSPO Glossary. I would suggest to remove the glossary from the book and point to the OSPO Glossary instead, so that there is no redundant content, which runs the risk of becoming inconsistent or outdated. The link in the header of the OSPO Book site could just link to https://ospoglossary.todogroup.org/.

Chapters cover a wide variety of topics which approach might change depending on the nature of the organization that has an OSPO (enterprises, NGO, government, university).

An idea could be to make an initial segmentation and use them as tags that can be included in each chapter and/or topic. This way is easier for the reader to understand that a specific resource or study serves better organizations with "X" goals. For instance:

This book is intended for Open Source Program Office managers, policymakers, executives, and stakeholders within organizations. Throughout the book, you can find up to three colored tags, that represent the different entities that could establish an open source program office (OSPO) based on the wide organization’s goals:

• Business Oriented OSPOs are established within for-profit organizations, such as enterprises, that are primarily focused on creating business value through the use of open source software. These OSPOs may prioritize topics such as driving innovation, talent retention, legal compliance, or risk management.

• Social Oriented These are OSPOs established within a government or public administrators that are focused on using open source software to achieve social or public policy objectives (e.g serving citizens). These OSPOs may prioritize topics such as interoperability, open data, accessibility, inclusion, privacy, security and transparency.

• Educational Oriented These are OSPOs established by educational institutions, such as universities or schools, that are focused on using open source software to support teaching, research and learning activities. These OSPOs may prioritize topics such as curriculum development, student engagement, open data, or knowledge sharing.

Maybe something to include in Chapter 0

Hi,

When visiting the OSPO Book Website, there is an "Edit this page" link in the right sidebar. This link leads to a non-existing page.

As an example, on the home page of the OSPO Book, the link points to {1a} while I think it should point to {1b} (missing ospo-book between main and content).

{1a}: https://github.com/todogroup/ospology/edit/main/content/en/_index.md
{1b}: https://github.com/todogroup/ospology/edit/main/ospo-book/content/en/_index.md

Same problem on the TOC page: {2a} while should be {2b}.

{2a}: https://github.com/todogroup/ospology/edit/main/content/en/toc.md
{2b}: https://github.com/todogroup/ospology/edit/main/ospo-book/content/en/toc.md

Thanks for looking into this,

Jean-François Gagné

Although we have made significant progress in formulating a better definition based on the input provided by past contributors, it is possible that this description may require further review in the future. Therefore, we have created an issue to ensure that we can revisit this definition if necessary at a later time. The PR that included the OSPO definition for the OSPO Book project was merged with the following content:

What - Place

An Open Source Program Office (OSPO) is a center of expertise, either virtual or physical, whose people support, nurture, share, explain, and promote the growth of open source within an organization.

Who - People

OSPOs are composed of people (open source specialists) wearing different hats:

• Open Source Enabler: OSPOs can help organizations navigate the cultural, process, and tool changes required to engage with the open source community effectively. This can involve educating teams/ units, establishing new processes and workflows, and adopting new tools and technologies.
• Open Source Counselor: OSPOs can provide guidance and advice on the latest open source trends, licensing issues, and how to engage with open source projects, foundations, and communities. This can help organizations stay up-to-date with the rapidly changing open source landscape and ensure they are making informed decisions.
• Open Source Advocate: OSPOs can promote the use and/or contribution of open source and best practices across different organizational units. This can help organizations realize the benefits of open source as well as engaging people to contribute to open source projects or start new ones.
• Open Source Environmentalist: OSPOs can help organizations support and sustain open source projects in the long term by addressing issues such as security, maintenance, and project health. This can involve establishing policies and procedures for code review, security vulnerability management, and ongoing maintenance and support through funding and/or contributions. By doing so, OSPOs can help ensure that open source projects remain healthy and continue to benefit the wider community.

How - Approach

The way the people behind an OSPO achieve this is by creating and maintaining a framework covering the following aspects: strategy, governance, compliance, and community engagement. The OSPO's strategy focuses on aligning the organization's open source goals with its overall organization objectives.

WHY - Value

An OSPO serves as a vital bridge between an organization and the open source community, helping to ensure that the organization is a good steward of open source software and can reap the benefits of open source adoption while minimizing risks.

Useful documentation to have this sync: https://dev.to/brunorobert/github-and-gitlab-sync-44mn

TODO Group is conformed by experienced OSPO leaders from different fields. These OSPO ambassadors can act as mentors to help new OSPO leaders in their OSPO journey by connecting them with TODO members to discuss industry-related OSPO issues.

In order to nurture the #mentoring slack channel, maybe we can build a more structured mentoring program, creating an initial document to establish the main issue, goals, and procedures to create these mentorship programs.

Calling all InnerSource practitioners!

'The State of InnerSource Survey 2022' is live and InnerSource Commons needs your input!

Why is this so important?

1. The data we collect provides an international snapshot on InnerSource adoption, scale-up and sustainability over the past year.
2. It gives you a chance to identify and share common trends and issues affecting your InnerSource project and organization.
3. All the feedback provided will inform our activities and supports in 2023.

Your input is vital so please complete the survey: https://www.surveymonkey.com/r/8X7Q5RW

We're aiming to keep the survey to one person per organization but please share the survey with any other relevant people.

Thank you so much!

Request to translate ospo-mindmap into Chinese-Simplified ,this will be well known by more developer and open source guys.

Session Title

Ways to define a metrics strategy in your OSPO

Session Description

Organizations with an OSPO understand the value of investing in open source development and set goals related to open source use and participation. But every open source program defines success a little differently. The goals they set, and metrics they track, will vary according to the reasons the organization is investing in open source – whether it’s to recruit developers, bring in new ideas and technologies through open innovation, achieve faster time to market, lower development costs, or myriad other reasons.

In this panel discussion, a group of OSPO leaders will gather to discuss how they have participated in metrics strategy discussions with the help of CHAOSS tools, and open source metrics standards.

Benefits to the Ecosystem

As stated from CHAOSS: The importance of open source software is no longer in question and its importance raises important questions about how we understand the health of the open source projects we rely on. Unhealthy projects can have negative impacts on the community involved in the project as well as organizations that rely on such projects. In response, people and organizations want to know more about the open source projects they are engaged with.

The panel will explore how a better understanding of open source community health can have positive impacts for OSPO-related operations.

Help us narrow down the focus a bit more. Please choose the OSPO related topic that best describes your proposal.

Hosting OSS Projects and Growing Communities

What level of experience should the audience have to best understand your presentation?

OSPO 101 (Beginner)

Speaker Name

Matt Germonprez (Moderator)
Ana Jiménez Santamaría (Moderator)

Dawn Foster (Panelist)
Sean Goggins (Panelist)
Daniel Izquierdo (Panelist)
Mike Nolan (Panelist)

Speaker Bio

Matt Germonprez is the Mutual of Omaha Distinguished Chair of Information Science & Technology and Professor of Information Systems and Quantitative Analysis in the College of Information Science & Technology at the University of Nebraska Omaha. His lines of research have been funded by numerous organizations including the Alfred P. Sloan Foundation, the Ford Foundation, the National Science Foundation, the Chan Zuckerberg Initiative, and Mozilla. Matt is the co-founder of the Linux Foundation Community Health Analytics OSS Project (CHAOSS). Matt is an active open source community member, having presented design and development work at LinuxCon, the Open Source Summit NA, the Linux Foundation Open Compliance Summit, the Linux Foundation Collaboration Summit, and the Open Source Leadership Summit.

Speaker preferred pronouns

He/Him

I'd like to propose two additional topic areas which may be good to cover in the OSPO book - either in a separate chapter or as one of the already proposed chapters:

• Current developments and their impact on Open Source Software:
  Ana mentioned in out 1:1 that the book is supposed to be updated regularly, e.g., on yearly basis. Based on this, I think it would be interesting to include a section on the latest / recent / current developments in the open source and OSPO space. This could be a short section / chapter in the beginning of the book. A list of current examples include (feel free to extend):

  • the recent push towards more regulation of software and its impact on open source
  • widely used and single-company-backed projects changing their licenses (bait-and-switch)
  • open source gaining tracking and attending in the public sector

• Outlook:
  This could be related to the proposal above, but instead of looking at recent development, this section could take a look at potential future developments in the open source domain. This could be a section / chapter in the end of the book. A list of potential examples (again, feel free to extend)

  • upcoming AI and its impact on open source
  • How will open source software evolve going forward?
  • How will OSPO need to evolve going forward?

  Please not that I don't necessarily have answers to those questions yet. But maybe you have opinios, so please chime in.

Session Title

Building an OSPO in the Energy Sector: The Alliander experiences

Session Description

Business sponsorship, enthusiasm and going for it. Those three ingredients define Alliander’s OSPO. After joining LF Energy and releasing our first open source project under the LF Energy umbrella, we started to recognize the need within Alliander for a group of people with the know-how and mandate to help bring structure and organization to the open source plans. And so some enthusiasts came together and discussed the various open source needs within the company. The OSPO turned out to be an excellent means for this because it created an overview of all open source activities. From there, we started consolidating knowledge, worked on building better open source development practices, familiarized the organization with innersource, improved license compliance, and looked for external opportunities for collaborating via open source. The OSPO as a strategic pillar for change was born. Two years later, here we are. We have released and contributed to many more open source projects, have a functioning Open Source Program Office and are starting to embed the open source mindset in the organization.

In this session, we will tell you more about our OSPO journey, our OSPO ambitions and will be introducing LF Energy.

Benefits to the Ecosystem

Learn about Alliander's experiences in building an OSPO in the Energy Sector.

Help us narrow down the focus a bit more. Please choose the OSPO related topic that best describes your proposal.

Adoption and Discovery

What level of experience should the audience have to best understand your presentation?

OSPO 101 (Beginner)

Speaker Name

Jonas van den Bogaard & Nico Rikken

Speaker Bio

Jonas van den Bogaard is solution architect & open source evangelist at Alliander. Alliander is the largest DSO in the Netherlands. As a DSO, Alliander is responsible for the distribution of energy such as electricity, gas and heat.

Nico Rikken is Senoir DevOps Consultant & open source evangelist at Alliander. Alliander is the largest DSO in the Netherlands. As a DSO, Alliander is responsible for the distribution of energy such as electricity, gas and heat.

Speaker preferred pronouns

Please add your preferred pronouns, if any (e.g She/ Her, They/ Them)

Session Title

Measuring the Business Impact of Open Source

Session Description

As much of the open source story focuses on community and public commons, organizations are not always financially aligned towards these goals alone. Successfully pitching the value of open source to an organization requires a focus beyond the bottom line, as well as identifying the appropriate analogues for your organizational stakeholder. In this talk, we share what we have learned about demonstrating the value of open source, working with stakeholders to identify their needs, and how to define success metrics for open source within an organization.

Benefits to the Ecosystem

Outcomes

• Audience will learn about the evolving needs of businesses in relation to their open source organizational life cycle
• Audience will walk away with a framework to identify stakeholders to open source in an organization
• Audience will get a high level overview of how to define success metrics for open source, along with a few specific use cases which walk through applying the method to demonstrate sample metrics

Help us narrow down the focus a bit more. Please choose the OSPO related topic that best describes your proposal.

Becoming Strategic Decision-Making Partner

What level of experience should the audience have to best understand your presentation?

Advanced OSPO (Advanced)

Speaker Name

amanda casari

Speaker Bio

Amanda Casari is an open source scientist in the Open Source Programs Office at Google, where she is co-leading research and engineering to better understand risk and resilience in open source ecosystems. She was named an External Faculty member of the Vermont Complex Systems Center in 2021. Amanda is persistently fascinated by the difference between the systems we aim to create and the ones that emerge, and pie.

Speaker preferred pronouns

she/her

Would it be possible to share this event in the newsletter please:

ORT Community Days
6-7 March, 2024
Berlin, Germany
https://cd.oss-review-toolkit.org

Thanks!

If a new definition appears in any of the book's chapters (or an existing one needs further explanation), please open a new pull request (PR) to add that definition to the glossary 👍 You can also leave a comment in this issue to propose adding a new definition before creating a Pull Request

• Link to the book glossary: https://github.com/todogroup/ospology/blob/main/ospo-book/chapters/glossary.md
• Link to book chapters: https://github.com/todogroup/ospology/tree/main/ospo-book/chapters

Hi, there are many broken links to the TODO Group Website in the OSPO Book. Some examples in {1}, {2} and {3}.

{1}:

{2}:

{3}: https://github.com/todogroup/ospology/blob/b53f3dd405b2be91458d029411bca2012c53b4c7/ospo-book/content/en/references.md?plain=1#L30C50-L30C94

I suspect most of the urls to not be working, I tested a few in below.

$ grep -r todogroup.*guides ospo-book/ | sed -e 's/.*http/http/;s/[ \)|].*//' | sort | uniq -c
   2 https://todogroup.org/guides/building-leadership/         <<<===--- this does not work.
   2 https://todogroup.org/guides/casestudies/autodesk/        <<<===--- this works.
   2 https://todogroup.org/guides/casestudies/capitalone/      <<<===--- this does not work.
   2 https://todogroup.org/guides/casestudies/comcast/         <<<===--- this works.
   2 https://todogroup.org/guides/casestudies/dropbox/
   2 https://todogroup.org/guides/casestudies/facebook/
   2 https://todogroup.org/guides/casestudies/microsoft/
   2 https://todogroup.org/guides/casestudies/ni/
   4 https://todogroup.org/guides/casestudies/porsche/
   2 https://todogroup.org/guides/casestudies/redhat/
   2 https://todogroup.org/guides/casestudies/salesforce/
   2 https://todogroup.org/guides/casestudies/sap/
   2 https://todogroup.org/guides/casestudies/uber/
   2 https://todogroup.org/guides/create-program/           <<<===--- this does not work.
   2 https://todogroup.org/guides/diversity-inclusion/      <<<===--- this does not work.
   2 https://todogroup.org/guides/improve-your-open-source-development-impact/     <<<===--- this works.
   2 https://todogroup.org/guides/management-tools/         <<<===--- this does not work.
   2 https://todogroup.org/guides/managing-career-development-within-ospo/
   2 https://todogroup.org/guides/marketing-open-source-projects/
   2 https://todogroup.org/guides/measuring/
   2 https://todogroup.org/guides/organizing-and-managing-open-source-events/
   2 https://todogroup.org/guides/os-commercial-ecosystem/
   6 https://todogroup.org/guides/outbound-oss/
   4 https://todogroup.org/guides/participating/
   2 https://todogroup.org/guides/recruiting-open-source-developers/
   2 https://todogroup.org/guides/shutting-down-an-open-source-project/
   2 https://todogroup.org/guides/starting-an-open-source-project/
   6 https://todogroup.org/guides/strategy/
   2 https://todogroup.org/guides/using-open-source/

With a little work, it is possible to find the right page by editing the URL and looking in {4} or {5}.

{4}: https://todogroup.org/resources/guides/

{5}: https://todogroup.org/resources/case-studies/

Sorry, I do not have time to provide a PR, and maybe this should be addressed by a redirect on the TODO Group Website, not by an edit of the OSPO Book (or by both).

Thanks for looking into this,

Jean-François Gagné

Session Title

OSPO Case Study Chapters

Session Description

Through work with over 100 different organizations on building metrics dashboards as part of the CHAOSS project over the last 7 years, we've built case studies for corporate, government, university, and acadmic OSPOs through active work with them.

Would case study chapters be helpful? I could propose a standard format.

Benefits to the Ecosystem

People learn by seeing modeled behavior, and Case studies are a useful written format for doing that.

Help us narrow down the focus a bit more. Please choose the OSPO related topic that best describes your proposal.

Becoming Strategic Decision-Making Partner

What level of experience should the audience have to best understand your presentation?

None

Speaker Name

Sean Goggins

Speaker Bio

https://www.seangoggins.net/bio/

Speaker preferred pronouns

He/Him

This ticket is to track existing open source models and or related studies that have been published over the past years