* 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>
2.4 KiB
title, description, date, slug, tags, hide_table_of_contents, authors
| title | description | date | slug | tags | hide_table_of_contents | authors | |
|---|---|---|---|---|---|---|---|
| Continuing to reward contributors | Our 3-month trial of paying core maintainers has been a success. We're making it permanent — and will be expanding the system to cover bug bounties, feature work, and more. | 2025-10-06T10:00 | continuing-to-reward-contributors |
|
false | MatissJanis |
Three months ago, we launched an experiment: using community donations to directly support the people who keep this project running. The idea was simple — compensate core contributors for the invisible but essential work of reviewing pull requests, triaging issues, and preparing releases.
Today, we're excited to share that the trial has been a success. 🎉
Thanks to your feedback, patience, and ongoing support, we've ironed out the kinks in the system, resolved bugs in the points tracking process, and proven that this model is both fair and sustainable.
As a result: we're making contributor payments permanent.
What This Means
- Core contributors will continue to receive stipends based on their monthly contributions.
- The transparent points system (for PR reviews, issue triage, and releases) remains in place.
- Funding continues to come from our community donations on OpenCollective.
This ensures that the essential maintenance work — the work that enables everything else to happen — is recognized and supported long-term.
What's Next: Expanding the System
The initial trial was focused on core maintenance. Now that the foundation is solid, we're preparing to expand. Over the coming months, we plan to introduce:
- Bug bounties → Rewards for fixing long-standing or high-impact issues.
- Feature bounties → Incentives for implementing important improvements requested by the community.
- Other initiatives → Ways to make contributing more rewarding and sustainable for everyone, not just core maintainers.
We'll share details about these expansions soon — so stay tuned!
Thank You ❤️
This project is powered by generosity, trust, and shared care. By supporting contributors financially, we're not just sustaining the software — we're sustaining the community behind it.
To everyone who has donated, given feedback, or contributed time and energy: thank you. This is your success as much as ours.