Add FUNDING.yml and concrete sponsorship goals

未關閉
#90 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 3 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
48/100
Issue 類型
功能
描述清晰度
描述清楚
活躍度
冷清
技術堆疊
github, python

研究方向

Start by checking the existing sponsor links in the README and landing page, then locate the landing page and the app's Info dialog. Add .github/FUNDING.yml for the repository sponsor account and a single support link in both places; mention commercial licensing for business users. The issue is done when GitHub shows the Sponsor button, the profile has a concrete goal, and the website and Info dialog each link to it once.

由索引模型根據 Issue 內容生成。

描述

marketing priority: low

Why it matters

The README and landing page link to GitHub Sponsors, but the repository has no .github/FUNDING.yml, so GitHub doesn't show the Sponsor button on the repo page, the place most visitors look. There's also no stated reason to sponsor. Concrete, visible goals convert far better than a generic heart badge, and this project has real recurring costs coming (code signing, see the signing issue).

Evidence

  • .github/ contains dependabot.yml, ISSUE_TEMPLATE/, PULL_REQUEST_TEMPLATE.md and workflows/, but no FUNDING.yml.
  • README badge and footer, plus the landing page footer, link to https://github.com/sponsors/TMHSDigital.

Suggested approach

  1. Add .github/FUNDING.yml with github: [TMHSDigital] (plus any other platforms used).
  2. On the Sponsors profile, add one or two concrete goals, e.g. "Sign releases so Windows stops warning (monthly signing cost)".
  3. Add a short "Support the project" line to the landing page and the app's Info dialog. It stays non-intrusive: no nag screens.
  4. Mention commercial licensing (CC BY-NC) next to sponsorship for business users, since that's the other revenue path the license already sets up.

Done when

  • The repo page shows the Sponsor button, the Sponsors profile has a concrete goal, and the website and Info dialog link to it once.
主要語言
Python
星號
0
分支
2
平均合併
2 天 13 小時
30 天內合併 PR
2

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

TMHSDigital/autoclicker 的其他 Issue

查看 TMHSDigital/autoclicker 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。