Add FUNDING.yml and concrete sponsorship goals

Aberta
#90 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 3 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Pouca atividade
Stack de tecnologia
github, python

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
Python
Estrelas
0
Forks
2
Merge médio
2d 13h
PRs com merge (30d)
2

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de TMHSDigital/autoclicker

Todas as issues de TMHSDigital/autoclicker

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.