d9a1260c91
* Update typography rule to disallow curly quotes with auto-fix - Reverse typography rule to detect and flag curly quotes instead of straight quotes - Add auto-fixer that converts curly quotes to straight quotes - Fix auto-fixer to properly escape quotes when they match string delimiters * Fix quotation marks in error messages and formatting strings across multiple files - Standardize quotation marks from curly to straight in error messages and string formatting for consistency. - Update various components and utility files to ensure proper string handling and improve readability. * Standardize quotation marks across multiple files - Replace curly quotes with straight quotes in various documentation and code files for consistency and improved readability. - Update error messages, comments, and documentation to ensure uniformity in string formatting. * Standardize month formatting across multiple components - Update month formatting strings from "MMMM 'yy" to "MMMM ''yy" in various components and utility files for consistency. - Ensure uniformity in how months are displayed throughout the application. * Refactor typography rule to enhance curly quote handling - Simplify the error reporting mechanism for curly quotes by creating a shared fix function. - Update test cases to include various curly quote scenarios for improved coverage. - Ensure consistent handling of curly quotes in formatting functions across multiple files. * Refactor typography handling and update tests for curly quotes - Replace curly quotes with their Unicode equivalents in typography rule and related test cases for consistency. - Remove unnecessary eslint-disable comments to improve code clarity. - Ensure proper handling of quotes in arithmetic and utility tests to align with updated typography standards. * Update VRT screenshots Auto-generated by VRT workflow PR: #6454 * Fix: Correct typo in budget cell notification message Co-authored-by: matiss <matiss@mja.lv> * Update VRT screenshots Auto-generated by VRT workflow PR: #6454 * Temporarily disable i18n string extraction workflow --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Cursor Agent <cursoragent@cursor.com>
3.7 KiB
title, description, date, slug, tags, hide_table_of_contents, authors
| title | description | date | slug | tags | hide_table_of_contents | authors | |
|---|---|---|---|---|---|---|---|
| Proposal for spending community funds | We're proposing a system to pay core maintainers for essential admin work funded by community donations. This 3-month trial won't move forward without your input. If the community is against it, we won't do it. | 2025-06-08T16:00 | spending-community-funds |
|
false | MatissJanis |
Our open source community has reached an exciting point: thanks to the incredible generosity of our donors, we now have a steady flow of funds coming in. First of all — thank you.
This support allows us to make the project more sustainable for everyone involved. We want to start by addressing something that is often overlooked in open source: the invisible labor that keeps everything running.
We're proposing a 3-month trial program to pay our core maintainers for the essential (but often unglamorous) work of:
- Reviewing pull requests
- Triage and categorize GitHub issues
- Preparing releases
We believe it's time to recognize the financial value of labor — but before we move forward, we want to hear your feedback. Join the conversation on Discord or leave anonymous feedback in this form.
Update: This proposal has been approved. More details about the payment system can be found in the paying contributors page.
What We're Proposing
Starting July 1st, we'd like to set aside $1,000 per month from the project's funds for a review stipend pool. This pool would be divided between core maintainers based on the work they do each month, measured via a transparent points system.
- Points are assigned based on the size of PRs reviewed (using lines of code as a proxy for effort).
- Additional points are awarded for labelling and grooming issues, closing duplicates, and managing releases.
- The system has a cap, and in months with less activity, the payout is reduced to $500.
- Payments are handled via OpenCollective and are only available to core maintainers.
This system is designed to be lightweight, fair, and easy to administer — and it keeps our monthly costs well within our donation income.
Why Start With Admin Work?
Before we consider feature bounties or bug bounties, we need to acknowledge the day-to-day labor that enables these contributions to be merged and released. Paying for features while leaving critical administrative work unpaid would be unsustainable — and unfair.
This trial serves as the foundation for broader funding efforts in the future. However, it begins with respecting the work that is already being done.
What We Need From You
We believe this is the right direction — but we won't go ahead without the community's support.
- If you're for it, against it, or have suggestions — let us know.
- If there's strong opposition, we won't implement it.
- If the community supports it, we'll begin the trial in July.
Join the conversation on Discord or leave anonymous feedback in this form. We're listening — and we'll publish a summary of the feedback before moving forward.
What's Next?
- We'll collect community feedback until late June.
- If there's consensus, the 3-month trial begins July 1st.
- After the trial, we'll evaluate how it went and where to go next.
Thank you again for being part of this journey. This community runs on trust, time, and care. With your feedback, we can keep building something that works — for all of us.