(iggy-website) branch main updated: chore: add a pull request template for user stories (#117)

[kr...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

kparisa pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iggy-website.git


The following commit(s) were added to refs/heads/main by this push:
     new bfbebbc13 chore: add a pull request template for user stories (#117)
bfbebbc13 is described below

commit bfbebbc13ba08e0fcfb89e4f3d7f426427432788
Author: Justin Mclean <jm...@apache.org>
AuthorDate: Tue Oct 6 17:27:15 2026 +1100

    chore: add a pull request template for user stories (#117)
    
    Lets people share how they use Iggy as a blog post PR. Opt-in via
    ?template=user-story.md, so other PRs are unaffected. Pairs with the
    Powered By page's caseStudyUrl.
    
    Co-authored-by: Justin Mclean <ju...@apache.org>
    Co-authored-by: Kranti Parisa <kr...@laserdata.com>
---
 .github/PULL_REQUEST_TEMPLATE/user-story.md | 56 +++++++++++++++++++++++++++++
 1 file changed, 56 insertions(+)

diff --git a/.github/PULL_REQUEST_TEMPLATE/user-story.md b/.github/PULL_REQUEST_TEMPLATE/user-story.md
new file mode 100644
index 000000000..89751c994
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE/user-story.md
@@ -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 dev@iggy.apache.org 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. -->