Add FUNDING.yml and concrete sponsorship goals

Offen
#90 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 3 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Ruhig
Tech-Stack
github, python

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
Python
Sterne
0
Forks
2
Ø Merge
2 T. 13 Std.
Gemergte PRs (30 T.)
2

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus TMHSDigital/autoclicker

Alle Issues in TMHSDigital/autoclicker

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.