Consider a separate repo for optional Patina components

[makubacki]

Request Description

Today, the Patina project plans to maintain components provided by the Patina project in the patina repository.

An alternative approach would be hosting optional components in a separate repository. This has pros and cons. This issue tracks making a decision.

• It is recommended that when this issue is picked up that the owner creates an RFC to explain the pros and cons in detail and drive the actual decision-making process.

---

At this time, there is no plan to create a separate repository for optional components.

Are you going to make the change?

Someone else needs to make the change

Do you need maintainer feedback?

Maintainer feedback requested

Anything else?

No response

[makubacki]

Current Plan

Create a separate ODP repo called patina-components that will initially serve as an evaluation area for breaking out components to their own repo. Meaning, initially, only new components will be added to the repo with no change to existing components in the patina repo.

Rationale

Patina components are ultimately pieces of functionality largely authored by the ecosystem that extend the base set of functionalities provided by Patina core code while leveraging Patina SDK code. As today's firmware code is a mix of open and closed source, so will be Patina components.

The primary purpose for this repo split is to better reflect the reality of detached repo component development within the Patina project itself so shared challenges with downstream code are readily apparent to Patina maintainers.

Because Patina components are maintained as separate crates, the crate boundary makes repo placement less important from a code sharing perspective, but independent versioning to Patina SDK changes, the ability to individually version components, etc. better reflect how components will be maintained outside the patina repo.

Based on this evaluation, other components might move to the patina-components repository.

[makubacki]

I've assigned myself as owner of this issue with the task to create and populate the initial content of the patina-components repo.