Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

docs: define free and paid product model

未关闭
#7 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
领域
payments

调研方向

The issue names no files, tests, or entry points. Start by identifying where product limits and entitlement decisions belong, then define the free and paid rules, offline and account-lifecycle behavior, and the boundary with ChatGPT access; done means the model is documented and the acceptance criteria are unambiguous.

由索引模型根据 Issue 内容生成。

描述

Objective

Define a simple monetization model without weakening the core product or creating confusing limits.

Proposed initial model

Free:

  • Queue up to 2 prompts total, meaning one automated follow-up after the initial prompt.
  • Local-only operation.
  • Core queue controls.
  • No ads.

Paid:

  • Larger or unlimited queue sizes subject to practical safety limits.
  • Advanced queue features added over time.
  • Optional workflow features.
  • Optional cross-device sync only if a backend is introduced later.

Important product rule

QueueIt sells the QueueIt software and workflow features. It does NOT sell ChatGPT access, model tokens, or a way around ChatGPT usage limits.

The extension must never imply that paying QueueIt increases a user's ChatGPT quota.

Entitlements

Document:

  • anonymous/free state
  • paid state
  • how entitlement is checked
  • what happens offline
  • grace period behavior
  • account deletion
  • refunds/cancellation handling
  • server-side verification if a backend is introduced

Recommendation for MVP

Do not build payments before the core queue loop is stable. First validate the product with a local free version.

Acceptance criteria

A user can understand the free limit in one sentence, and paid functionality is clearly separate from ChatGPT subscription access.

主要语言
CSS
星标
0
派生
0
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ChinmayOnGithub/queueit 的其他 Issue

查看 ChinmayOnGithub/queueit 的全部 Issue

相似的 Issue

更多 Fintech & Quant Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。