-
Notifications
You must be signed in to change notification settings - Fork 48
Consider a separate repo for optional Patina components #1417
Copy link
Copy link
Open
Labels
state:backlogIn the backlogIn the backlogstate:needs-maintainer-feedbackNeeds more information from a maintainer to determine next stepsNeeds more information from a maintainer to determine next stepsstate:needs-ownerNeeds an issue owner to be assignedNeeds an issue owner to be assignedstate:needs-triageNeeds to triaged to determine next stepsNeeds to triaged to determine next stepsurgency:lowLittle to no impactLittle to no impact
Milestone
Description
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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
state:backlogIn the backlogIn the backlogstate:needs-maintainer-feedbackNeeds more information from a maintainer to determine next stepsNeeds more information from a maintainer to determine next stepsstate:needs-ownerNeeds an issue owner to be assignedNeeds an issue owner to be assignedstate:needs-triageNeeds to triaged to determine next stepsNeeds to triaged to determine next stepsurgency:lowLittle to no impactLittle to no impact
Type
Projects
Status
Backlog