[OSPO Book] add preface and chapter one draft for review #282
Conversation
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
✅ Deploy Preview for ospomindmap canceled.
|
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
|
|
||
| An *Open Source Program Office (OSPO)* is a center of expertise, either virtual or physical, that supports, nurtures, shares, explains, and grows open source within an organization. An OSPO *role* can be conceived as an umbrella term, covering the responsibilities for defining and implementing strategies and policies that guide open source efforts and provide tools, processes, and knowledge to organization teams and experts in navigating open source without harming the open source ecosystem. Instead, they help to sustain it while achieving organizational goals. | ||
|
|
||
| OSPOs (as center of expertise) may comprise a framework built around some or all of the following aspects: |
There was a problem hiding this comment.
I am not entire sure if the terminology of "OSPO (as center of expertise)" and "OSPO (as a role)" is not overly complicated and not really needed. It creates the impression as if the abbreviation "OSPO" can apply to multiple different things. Wouldn't it be more straightforward to just use the terms as follows (on a high level):
- an OSPO is a center of expertise, either virtual or physical... [the org]
- An OSPO can act in multiple roles... [the what]
- an OSPO creates and maintains a framework covering the following aspects... [the how]
Just a proposal
There was a problem hiding this comment.
This section reads a little confusing to me as well. It also doesn't read as a definition, but it rather talks about what the org does, in some extent, and what responsibilities it has.
I would focus on really just defining here what the term actually means. I would establish that it is a group of people with the goals of X, Y and Z.
Then we can have subsections that talk about the OSPO's responsibilities, structure, job roles within that org and even suggest where it might sit within a bigger organization to be able to make impact.
There was a problem hiding this comment.
During yesterday's call, we agreed to come up with a different word to define the "different hats" that people within an OSPO play. The "persona" term was discussed but is also highly related to marketing definition and might create confusion.
There was a problem hiding this comment.
[From Contirbutor's call discussion] two differentiations might unblock this: OSPO as the entity and the people behind an OSPO (that includes roles, skillsets, etc)
|
|
||
| As an example, the following [diagram](https://lists.todogroup.org/g/ospo-book-project/message/5) illustrates the various players in a business-oriented OSPO and the different methods of interaction, communication, and knowledge transmission. | ||
|
|
||
| <img width="908" alt="img2" src="https://user-images.githubusercontent.com/43671777/224132683-6a2abdff-c846-4db3-b642-c2e32b5734fb.png"> |
There was a problem hiding this comment.
I think we should store the images in tree and also the editable versions of the images.
There was a problem hiding this comment.
+1! I can prepare an /img folder with the images and fix the links accordingly 👍
|
|
||
| > RE ML disussion: https://lists.todogroup.org/g/ospo-book-project/message/5 | ||
|
|
||
| If the organization decide to establish an OSPO (as entity) or integrate OSPO roles, it is crucial to assess the transmission of knowledge to different internal and external *open source players* that have a direct or indirect impact on the OSPO. This section examines the OSPO from four different perspectives: |
There was a problem hiding this comment.
I still have a hard time with using the OSPO term for both an entity as well as a group of roles. I think it is very easy to associate to job roles and functions, rather than the responsibilities that we listed above.
Co-authored-by: Ildiko Vancsa <[email protected]> Signed-off-by: Justin Dorfman <[email protected]>
Co-authored-by: Gergely Csatari <[email protected]> Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Co-authored-by: Ildiko Vancsa <[email protected]> Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Co-authored-by: Gergely Csatari <[email protected]> Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Co-authored-by: Georg Kunz <[email protected]> Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Co-authored-by: Ildiko Vancsa <[email protected]> Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Co-authored-by: Gergely Csatari <[email protected]> Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Co-authored-by: Georg Kunz <[email protected]> Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Co-authored-by: Georg Kunz <[email protected]> Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Co-authored-by: Ildiko Vancsa <[email protected]> Signed-off-by: Ana Jimenez Santamaria <[email protected]>
|
Update on the requested changes: I've committed those changes that didn't need further discussion (e.g typos, proofreading, removing unnecessary sentences) and kept those who need further discussion to let more people jump in during the week 🙂 Thanks @ildikov @CsatariGergely and @gkunz for your input and contributions 🙏 |
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Co-authored-by: Ildiko Vancsa <[email protected]> Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Co-authored-by: Ildiko Vancsa <[email protected]> Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Co-authored-by: Ildiko Vancsa <[email protected]> Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Co-authored-by: Ildiko Vancsa <[email protected]> Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
ospo-book/chapters/01-chapter.md
Outdated
| Open source has become an integral part of modern organizations, offering a range of benefits, including lower costs, increased collaboration, and access to a vast pool of talent and resources. However, with the growing importance of open source, organizations need to be equipped to manage their open source operations effectively, in order to realize these benefits. | ||
|
|
||
| Creating an Open Source Program Office (OSPO) can accelerate a company's or organization's open source journey from mindset change to efficient policies and workflows. An OSPO is a dedicated team or department within an organization that is responsible for managing the organization's open source operations, including the development, distribution, and use of open source software, and harmonizing and integrating these with product development. | ||
| In this book, we will guide organizations through the process of creating and implementing an OSPO. We will provide practical advice and best practices on how to streamline open source operations, and ensuring that organizations are able to maximize the benefits of open source technology, while being good open source citizens. |
There was a problem hiding this comment.
In those three paragraphs, there are too many , and and. I could understand well because I know what each section means. But other people like beginners may struggle with understanding each description.
What about making the list with bullet points, or providing a picture such as a mindmap?
ospo-book/chapters/01-chapter.md
Outdated
| Open source has become an integral part of modern organizations, offering a range of benefits, including lower costs, increased collaboration, and access to a vast pool of talent and resources. However, with the growing importance of open source, organizations need to be equipped to manage their open source operations effectively, in order to realize these benefits. | ||
|
|
||
| Creating an Open Source Program Office (OSPO) can accelerate a company's or organization's open source journey from mindset change to efficient policies and workflows. An OSPO is a dedicated team or department within an organization that is responsible for managing the organization's open source operations, including the development, distribution, and use of open source software, and harmonizing and integrating these with product development. | ||
| In this book, we will guide organizations through the process of creating and implementing an OSPO. We will provide practical advice and best practices on how to streamline open source operations, and ensuring that organizations are able to maximize the benefits of open source technology, while being good open source citizens. |
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
There was a problem hiding this comment.
@gkunz @ildikov @Jonasvdbo @caabernathy can you please review this new definition?
Signed-off-by: Ana Jimenez Santamaria <[email protected]>
No description provided.