Submissions triage

When someone submits through /submit, the Pages Function opens a GitHub issue in this repo with the submission label. Triage those issues here.

Where submissions live

Every form submission becomes an open issue in goosegroup/balsam-coe with the submission label. Find them:

Initial triage (within a week)

  1. Read the submission. Body has mode, name, contact, workflow, idea, why.
  2. Apply a theme label if the submitter’s selection was vague or missing. One of: theme:content, theme:product-data, theme:marketing, theme:order-to-delivery.
  3. Correct the mode label only if the intent is clearly mis-tagged (e.g. submitter picked “join” but is actually proposing someone else’s work).
  4. Reply. Pick one of the three templates below. Paste into a comment on the issue. Personalize.

The three replies

Accepted to backlog

Thanks for putting this forward. We’re adding it to the backlog — the Operating Council reviews the backlog monthly and picks the next cohort. The fit is good for [workflow] because [one-line reason]. You’re credited, and if this becomes a cohort we’ll invite you to contribute. We’ll be back in touch when the next review happens.

Routed

This is a solid ask, but it’s a better fit for [team] than for a cohort. I’ve looped in [name] — they’ll follow up directly. Keeping this issue open as a reference so you have a thread to track.

Parked with reasoning

Thanks for submitting. We’re parking this for now because [specific reason — too early / too narrow / duplicates existing work / no core owner yet]. That’s not a closed door — [what would change the call]. If you want to iterate, resubmit with updated context and we’ll look again.

Close the issue with whichever of these applies. routed and parked close immediately; accepted to backlog stays open.

Promoting to pipeline display

When a submission is strong enough to show publicly on /pipeline:

  1. Add the show-on-site label.
  2. Confirm the issue has a theme:* label (that’s how it gets grouped).
  3. Next time the site rebuilds, the Ideas section on /pipeline picks it up.

Note: deploys are not automatic on label changes. Trigger a rebuild with a no-op push to main, or run npm run build && npx wrangler pages deploy dist/ --project-name=balsam-coe --branch=main manually.

Promoting to cohort candidate

When a submission matches an active cohort formation:

  1. Comment on the submission linking to the cohort issue or repo.
  2. Credit the submitter in the cohort’s people list.
  3. Close the submission with a note: “Moving forward as part of [cohort name].”

What not to do

  • Don’t police intent in public. If a submission violates “submit ideas for other people to do,” reply privately (email/Slack), then either route or park. The form copy sets the norm; the triage reply enforces it kindly.
  • Don’t leave submissions unanswered. Every one gets a response inside a week. If you can’t give a full reply, at minimum acknowledge it.
  • Don’t add show-on-site without a theme label. It’ll land in “Uncategorized” on /pipeline, which reads as sloppy.