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

docs: update 2025 roadmap #1860

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

docs: update 2025 roadmap #1860

wants to merge 1 commit into from

Conversation

samayer12
Copy link
Contributor

Description

We've had some discussions around the roadmap, this PR includes the updates.

End to End Test:
(See Pepr Excellent Examples)

Related Issue

hotfix

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Other (security config, docs update, etc)

Checklist before merging

Comment on lines +19 to +20
- **Determine if a Transactional PeprStore makes sense**:
- Sus out details involved with having a transactional Pepr Store. What are the implications of this? What are the benefits? What are the drawbacks? What are the use-cases? What are the technologies that can be used to implement this?
Copy link
Contributor

Choose a reason for hiding this comment

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

Based on a comment by @slaskawi this may now not be a priority from a UDS perspective as they will not rely on the store for Keycloak integration. Lets keep an eye on this

@cmwylie19
Copy link
Contributor

I think one place that Pepr has a lot of room to improve is our documentation. The project is created to anyone to be able to handle complex Kubernetes events from the new person to the expert, I hypothesize if we can improve our docs we will get more traction in the community.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

2 participants