Skip to content

chore: add a pull request template for user stories #117

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.

Sign up for GitHub

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

Merged
kparisa merged 2 commits into from
Oct 6, 2026
Merged

chore: add a pull request template for user stories #117

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ffc5e4d
chore: add a pull request template for user stories
Sep 23, 2026
b360200
Merge branch 'main' into github/user-story-template
kparisa Oct 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
56 changes: 56 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE/user-story.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
# User story: how we use Apache Iggy

<!--
This is for sharing a story of how you or your team use Apache Iggy in a
real project or production. A merged story is published on the Apache Iggy
website (https://iggy.apache.org/blogs/).

You control what is shared: delete any section you do not want to answer,
sign with your name, a pseudonym, or "anonymous", and keep any detail you
prefer to stay private. Your company name and logo are optional, and a logo
is only shown on the Powered By page when your organisation's entry there
confirms permission for it.

Prefer not to use GitHub? Send the same answers to [email protected] and
a committer will open the pull request for you.
-->

## Who are you?

<!-- One or two sentences: you and/or your team or company, and what you
build. Delete this section entirely if you prefer not to be identified. -->

## What problem were you solving?

<!-- What were you using before Apache Iggy (or alongside it), and what was
not working: latency, cost, ops burden, language fit? -->

## Why Apache Iggy?

<!-- What did the evaluation look like, and what made Iggy the fit? If you
built or extended a connector or SDK as part of this, link the PR or issue
in https://github.com/apache/iggy if there is one. -->

## What does the deployment look like today?

<!-- Concrete, but only what you are comfortable sharing: scale
(messages/sec, retention, cluster size), transport (TCP/QUIC/HTTP), and
where it runs. Rough or unverified numbers are fine, just say so. -->

## What broke or surprised you first?

<!-- Rough edges are genuinely useful to the project. Link the issue or PR
in https://github.com/apache/iggy if you filed one. -->

## What are you willing to share?

- [ ] My name as published (or a pseudonym, or "anonymous")
- [ ] My company name (text only, on the story and on the Powered By page)
- [ ] My company logo on the Powered By page (only shown if the
organisation's `content/organizations/` entry has
`permissionConfirmed: true`)
- [ ] A short quote from this story for the Powered By page

## Anything else?

<!-- Optional. -->
Loading