Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

GitHub Sponsors for the krizaka organisation — enrol, profile and tiers

Open
  • Is something wrong?
#27 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #43 by @rohitkaswan — closed without merging

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
15/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github
Domain
tooling

Research direction

This is explicitly a manual action for Oussama, not a newcomer code task. Read the prerequisite issues #18, #19, and #16, then use the GitHub Sponsors dashboard and the listed repository Settings pages; the issue also points to .github/FUNDING.yml. Done when the public sponsor profile is live and the Sponsor button appears on krizaka/orazaka.

Written by the indexing model from the issue text.

Description

owner:oussama priority:P2 product:krizaka type:ops

Manual action — Oussama only (company bank account, identity, tax forms).

krizaka/.github now ships a default .github/FUNDING.yml
(github: [krizaka] + a link to the contact form, topic partnership, source sponsor). The GitHub Sponsors entry stays
inert until the organisation is accepted into GitHub Sponsors — that is this issue.

Prerequisites

  • Company registered (NEQ) and bank account in the company's name — .github#18 → .github#19. GitHub pays organisations through Stripe Connect; the payout account must belong to the legal entity.
  • Two-factor authentication on the owner account (already required by the org).
  • Tax information: the Stripe onboarding asks for the business number (NE) and a W-8BEN-E (non-US entity).

Steps

  1. github.com/sponsors → Get started → choose the krizaka organisation (or Org → Settings → Sponsors, left menu, when shown).

  2. Fill the waitlist / application form: country Canada, legal name of the company, contact e-mail [email protected] (.github#16 — never the gmail address).

  3. When accepted (GitHub reviews organisations, usually days to a few weeks): Stripe Connect onboarding → company identity, bank account, tax form.

  4. Sponsor profile (Sponsors dashboard → Profile details):

    • Short bio: Open-source building blocks and two products — sovereign AI on your own machines (Orazaka) and a creator video platform that pays every cent exactly once (Orochia).
    • Introduction (proposed):

      Krizaka builds in the open, under Apache-2.0: Java building blocks on Maven Central (com.krizaka), the @krizaka UI packages on npm, and two products built on them. Sponsorship pays for the CI, the hosting of the demos and the time to keep the blocks maintained (N and N-1 supported, deprecations with codemods). Thank you.

    • Featured work: orazaka, orochia, krizaka-ui, krizaka-platform-kit.

  5. Tiers (Sponsors dashboard → Sponsor tiers; monthly, in USD as GitHub requires). Proposed — only promise what we can keep:

    Tier Monthly What the sponsor gets
    Supporter $5 Our thanks, the sponsor badge on GitHub, and a mention in the release notes of the month.
    Backer $25 Everything above + name (or handle) in the "Sponsors" section of the organisation README, and an area: label of their choice prioritised in the monthly triage of good first issues.
    Partner (companies) $250 Everything above + logo in the README's Sponsors section, answers within 2 business days on GitHub Discussions of the products, and a 30-minute call per quarter on the roadmap. No SLA, no private fork — paid support stays a separate contract.

    One-time tiers: allow custom amounts (min $5).

  6. Goals (optional): leave empty until there is a figure we can honour (e.g. "cover CI and demo hosting").

  7. Publish the profile, then tick "Sponsorships" on the main repositories (each repo → Settings → General → Features → Sponsorships): orazaka, orochia, krizaka-ui, krizaka-platform-kit, krizaka-build, krizaka-com, orochia-mobile. That is what makes the Sponsor button appear (it reads this default FUNDING.yml).

  8. Tell a Claude session it is live: it adds a "Sponsors" section and the sponsor button/badge to the organisation README (today the README only says "write to us", nothing is promised).

Alternatives (not created — proposals)

  • Open Collective (via the Open Source Collective fiscal host, 10 % fee): transparent public ledger, invoices for companies; useful if sponsors want invoices before Stripe/GitHub works. Adds open_collective: krizaka to FUNDING.yml.
  • Polar.sh: funding per issue + subscriptions, good for "pay to prioritise a feature"; adds polar: krizaka.
  • Recommendation: GitHub Sponsors first (no GitHub fee on sponsorships from personal accounts, visible on every repo); revisit Open Collective only if a company asks for invoices.

Done when: github.com/sponsors/krizaka is public and the Sponsor button shows on krizaka/orazaka.

Dominant language
No language data
Stars
0
Forks
0
Avg merge
2h 18m
Merged PRs (30d)
21

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from krizaka/.github

All issues in krizaka/.github

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.