docs: reframe eventkit as a kit #31
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Reframes EventKit as a kit for building event pipelines, not a PyPI library.
Closes #9
Philosophy Change
Before: Library you
pip installand consume as a black boxNow: Kit you clone and customize for your needs
What Changed
README Updates
git cloneworkflow, notpip installWhy This Makes Sense
EventKit is infrastructure code that teams will want to customize:
Rather than fight this with configuration options and backwards compatibility, we lean into it: this is your starting point, make it yours.
Future: Extract Libraries
As patterns stabilize, we can extract focused libraries:
eventkit-ring-buffer- SQLite WAL durabilityeventkit-queues- Queue abstractionseventkit-validators- Composable validationThese would be pip-installable while the kit remains customizable.
Related
gcp-python-api-kitphilosophyChecklist