make a seperate repo for OSS in Business WG

[Delta456]

OSS in Business work currently resides on https://github.com/todogroup/ospology/tree/business_guide_dev branch which is becoming hard to track with the new additions and changes from upstream.

Moving to a separate repo would help to track changes, suggestions tracked and would also help people from non tech background to contribute to the business side of the content.

[eriksven]

We discussed this topic in multiple of the OSS in Business WG meetings and came to the conclusion to request the separate repository.

This might conflict with the mono-repo approach of this ospology repository but at the same time we already had multiple cases where people had a hard time finding the content of the business guide over all the other other directories and Pull Request.

[anajsana]

Hello! This would need review from the SC.

For context: In the past we had the opposite issue that TODO had many hosted repos (+30) that were difficult to find, a single repository to host community resources was the solution. Those who are outside OSPOlogy, are still difficult to find, such as the awesome oss management tooling repo or the OSPO policies one.

[anajsana]

started a gitvote for SC members to review: todogroup/governance#395

[anajsana]

OSS in Business work currently resides on https://github.com/todogroup/ospology/tree/business_guide_dev branch which is becoming hard to track with the new additions and changes from upstream.

Moving to a separate repo would help to track changes, suggestions tracked and would also help people from non tech background to contribute to the business side of the content.

A few thoughts from my side:

• I’m not fully sold on creating a new repo. We’ve had complaints in the past about having too many repositories, and adding another one could increase confusion and maintenance overhead.
• Also, if someone isn’t familiar with Git/GitHub workflows, moving content into a single dedicated repo doesn’t really solve the core problem
• A workflow that has worked well in OSPO Book WG to draft and iterate in a collaborative document first like Google Doc (we could create a dedicated folder in the TODO Group Drive instance for “OSS in Business” drafts and reviews) + once sections are mature, we assign someone with Git experience to transfer the reviewed content into Markdown and open PRs against the OSPOlogy repo.
  - This is essentially the same process the OSPO Book working group uses: collaborative drafting first, then a someone with Git experience handles the Markdown + PR workflow
  - To make contributions visible and credited, we can keep a lightweight contributors file (e.g., CONTRIBUTORS.md) where we add names for doc contributors as sections get merged