Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the OSPO Definition to Reflect Current Trends and Practices #9

Merged
merged 25 commits into from
Jun 14, 2023

Conversation

anajsana
Copy link
Member

@anajsana anajsana commented Mar 6, 2023

Open source program offices (OSPOs) can be established in a variety of sectors, regions, and organizational sizes, including private and public organizations. Therefore, it's important that we review and update the traditional OSPO definition to be more inclusive and up-to-date.

This PR aims to enhance the OSPO definition by incorporating a new section that focuses on OSPO segmentation based on the organization's goals and motivators.

Open source program offices (OSPOs) can be established in a variety of sectors, regions, and organizational sizes, including private and public organizations. Therefore, it's important that we review and update the traditional OSPO definition to be more inclusive and up-to-date.

This PR aims to enhance the OSPO definition by incorporating a new section that focuses on OSPO segmentation based on the organization's goals and motivators. 

Signed-off-by: Ana Jimenez Santamaria <anitajs95@gmail.com>
@anajsana anajsana requested a review from caniszczyk March 6, 2023 11:40
@caniszczyk
Copy link
Member

LGTM @anajsana - would be great if we can point to case studies of each category

I prefer "center of competency" of "central hub" but am open to other wording suggestions :)

Signed-off-by: Ana Jimenez Santamaria <anitajs95@gmail.com>
@caniszczyk
Copy link
Member

LGTM

README.md Outdated Show resolved Hide resolved
The community put together a more detailed definition for OSPOs via teh OSPO book project, which answers common questions (what, why, who, and how). This commit includes this definition: https://github.com/todogroup/ospology/blob/main/ospo-book/chapters/01-chapter.md#ospo-definition

Signed-off-by: Ana Jimenez Santamaria <anitajs95@gmail.com>
Include suggested responsibilities shared as a comment in this PR: #9 (comment) 

Signed-off-by: Ana Jimenez Santamaria <anitajs95@gmail.com>
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
anajsana and others added 2 commits May 30, 2023 10:57
Signed-off-by: Ana Jimenez Santamaria <anitajs95@gmail.com>
Co-authored-by: Georg Kunz <georg.kunz@ericsson.com>
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
@anajsana anajsana self-assigned this May 30, 2023
@anajsana anajsana added the documentation Improvements or additions to documentation label May 30, 2023
Copy link
Member

@UlisesGascon UlisesGascon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
Co-authored-by: Ulises Gascón <UlisesGascon@users.noreply.github.com>
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
@souravcipher
Copy link
Member

Fantastic work Ana!

LGTM 🎉

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
anajsana and others added 5 commits May 31, 2023 09:12
Co-authored-by: Cornelius Schumacher <schumacher@kde.org>
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
Co-authored-by: Cornelius Schumacher <schumacher@kde.org>
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
Co-authored-by: Cornelius Schumacher <schumacher@kde.org>
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
Co-authored-by: Cornelius Schumacher <schumacher@kde.org>
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
Co-authored-by: Cornelius Schumacher <schumacher@kde.org>
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
README.md Outdated Show resolved Hide resolved
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
@anajsana anajsana mentioned this pull request May 31, 2023
README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
… repo

Co-authored-by: Shanmugapriya M <97021994+spriya-m@users.noreply.github.com>
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
Copy link
Member Author

@anajsana anajsana left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

include OSPO pronunciation guidance in the definition.

README.md Show resolved Hide resolved
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
README.md Show resolved Hide resolved
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
@katnovakovic
Copy link

Is it worth stating that the OSPO covers the whole organisation, representing all lines of business / groups? Ideally you want to avoid duplicated effort across an organisation.

@anajsana
Copy link
Member Author

anajsana commented Jun 5, 2023

Is it worth stating that the OSPO covers the whole organisation, representing all lines of business / groups? Ideally you want to avoid duplicated effort across an organisation.

That's a great point to include @katnovakovic ! I think it should be added both in the [HOW](The OSPO represents and works with all lines of business units/groups) and [WHY] (ideally, with the aim to avoid duplicated effort across the organization) section 🤔

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Show resolved Hide resolved
… the OSPO

Co-authored-by: rrrutledge <rrrutledge@users.noreply.github.com>
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
README.md Outdated Show resolved Hide resolved
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
anajsana and others added 4 commits June 8, 2023 13:27
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
Co-authored-by: Cornelius Schumacher <schumacher@kde.org>
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
README.md Outdated Show resolved Hide resolved
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
@anajsana
Copy link
Member Author

anajsana commented Jun 8, 2023

Is it worth stating that the OSPO covers the whole organisation, representing all lines of business / groups? Ideally you want to avoid duplicated effort across an organisation.

That's a great point to include @katnovakovic ! I think it should be added both in the [HOW](The OSPO represents and works with all lines of business units/groups) and [WHY] (ideally, with the aim to avoid duplicated effort across the organization) section 🤔

I've added this line and committed the changes 👍

README.md Outdated Show resolved Hide resolved
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
@anajsana anajsana merged commit e91550f into master Jun 14, 2023
1 check passed
@anajsana
Copy link
Member Author

Great work everyone! Thanks for contributing to the new OSPO Definition release! 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet