Channels v1.1: Implement Pricing + Request Tracking
Closed
Nobody has claimed this yet.
channels
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
In future we should decide: Do channel events count towards your run limit, or do we want another limit entirely?
- Taylor's inuition: include 10x more of them than workflow runs.
- Brandon's intuition is to make them free/unlimited to attract people to OpenFn, and focus on monetising other higher-value-add features.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides no files, tests, or entry points to inspect. Start by reviewing the channel-event limit and pricing questions in this issue, then establish the intended policy and implementation scope before identifying the affected code and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100