feat: add funding.json#1632
Conversation
Added funding manifest for Svelte, including details about the organization, projects, and funding channels.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| "role": "owner", | ||
| "name": "Svelte", | ||
| "description": "Web development for the rest of us", | ||
| "email": "", |
There was a problem hiding this comment.
We need an official email here so we can be contacted. It's also required by the JSON schema.
Co-authored-by: Ben McCann <322311+benmccann@users.noreply.github.com>
Co-authored-by: Ben McCann <322311+benmccann@users.noreply.github.com>
Co-authored-by: Ben McCann <322311+benmccann@users.noreply.github.com>
| }, | ||
| "repositoryUrl": { | ||
| "url": "https://github.com/sveltejs/svelte", | ||
| "wellKnown": "https://github.com/sveltejs/svelte/blob/main/.well-known/funding-manifest-urls" |
There was a problem hiding this comment.
Note that a file similar to https://github.com/sveltejs/svelte.dev/pull/1632/files#diff-dc6aa312408365efda3e35f463314bc3c7a2f37df864885c94ab21be318e8f6c needs to be added to the Svelte repository to provide provenance to the manifest.
| }, | ||
| "repositoryUrl": { | ||
| "url": "https://github.com/sveltejs/kit", | ||
| "wellKnown": "https://github.com/sveltejs/kit/blob/main/.well-known/funding-manifest-urls" |
There was a problem hiding this comment.
Note that a file similar to https://github.com/sveltejs/svelte.dev/pull/1632/files#diff-dc6aa312408365efda3e35f463314bc3c7a2f37df864885c94ab21be318e8f6c needs to be added to the SvelteKit repository to provide provenance to the manifest.
Related to sveltejs/svelte.dev#1632 This will allow us to apply for a grant from floss.fund ### Before submitting the PR, please make sure you do the following - [ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs - [ ] Prefix your PR title with `feat:`, `fix:`, `chore:`, or `docs:`. - [ ] This message body should clearly illustrate what problems it solves. - [ ] Ideally, include a test that fails without this PR but passes with it. - [ ] If this PR changes code within `packages/svelte/src`, add a changeset (`npx changeset`). ### Tests and linting - [ ] Run the tests with `pnpm test` and lint the project with `pnpm lint`
Related to sveltejs/svelte.dev#1632 This will allow us to apply for a grant from floss.fund --- ### Please don't delete this checklist! Before submitting the PR, please make sure you do the following: - [ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs - [ ] This message body should clearly illustrate what problems it solves. - [ ] Ideally, include a test that fails without this PR but passes with it. ### Tests - [ ] Run the tests with `pnpm test` and lint the project with `pnpm lint` and `pnpm check` ### Changesets - [ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running `pnpm changeset` and following the prompts. Changesets that add features should be `minor` and those that fix bugs should be `patch`. Please prefix changeset messages with `feat:`, `fix:`, or `chore:`. ### Edits - [ ] Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.
Related to sveltejs/svelte.dev#1632 This will allow us to apply for a grant from floss.fund --- ### Please don't delete this checklist! Before submitting the PR, please make sure you do the following: - [ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs - [ ] This message body should clearly illustrate what problems it solves. - [ ] Ideally, include a test that fails without this PR but passes with it. ### Tests - [ ] Run the tests with `pnpm test` and lint the project with `pnpm lint` and `pnpm check` ### Changesets - [ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running `pnpm changeset` and following the prompts. Changesets that add features should be `minor` and those that fix bugs should be `patch`. Please prefix changeset messages with `feat:`, `fix:`, or `chore:`. ### Edits - [ ] Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.
This PR adds a
funding.jsonfile based on https://fundingjson.org which will allow Svelte to apply for funding from https://floss.fund .The selected projects were based on the search results of
FUNDING.ymlin our GitHub organisation https://github.com/search?q=org%3Asveltejs%20FUNDING.yml&type=code . But I think there are more projects we could add, just off the top of my head: devalue, svelte-mcp, acorn-ts .The financial plans are based off the plans in https://opencollective.com/svelte
I chose to omit https://github.com/sponsors/sveltejs as a financial payment method since we don't advertise it anywhere and it looks mostly abandoned. OpenCollective is more transparent anyway.
The annoying bit is that we need to add a
.well-known/funding-manifest-urlsfile to each project's repository if we decide to go ahead with this if we want provenance for those project URLs listed. Once that's done, we can submit the URL to the funding.json file to https://dir.floss.fund/submit to applyEDIT: removed all projects except svelte and sveltekit so that it's easier for us to get started
Before submitting the PR, please make sure you do the following
feat:,fix:,chore:, ordocs:.