Просмотр новости
Найдите то, что Вас интересует
Спутники
РН
SpaceX
Роскосмос
NASA
СпутникиРНSpaceXРоскосмосNASAWe've changed how contribution credit is weighted on Drupal.org, and the changes are now live. If you watch the Drupal Marketplace you may have noticed some organizations shift position as a result; this post explains what changed and why, and what's still coming.
Two weights went up. Everything else stayed the same.
Core issues are now worth a baseline of 15 credits each (previously 10). We're delighted at how strongly organizations have rallied behind strategic initiatives like Drupal CMS, Drupal Canvas, and Drupal AI. That's exactly what the credit system is meant to encourage. Those initiatives all stand on Drupal core, though, and we want to make sure the core team gets the fundamental care and feeding it deserves alongside them.
Core security advisories now carry a 10x multiplier on top of that baseline, so a single core security issue is worth 150 credits (previously 50). The Security Team and core release managers are handling a growing volume of AI-generated reports, and we want organizations to have a strong reason to support, or join, that work.
Unchanged: the minimum credit value is 1; credit scales with project usage (a project used on 300,000 sites earns 3 credits per issue); strategic initiative issues are worth 10 credits; and contrib security advisories remain at 5x the project's normal weight.
We've also expanded the core sponsorship table, which gives sponsors a guaranteed monthly base credit for supporting key roles whose most important work doesn't always happen in an issue. It now covers active Security Team Members, Subsystem Maintainers, and Topic Maintainers in addition to the core leadership roles already listed.
Next, we'll publish a companion table naming core contributors who are currently seeking sponsorship, so an organization that wants to fund core work can see exactly who to talk to. We'll post again when it's ready.
A note for Drupal Certified Partners: We check quarterly for partners who have qualified for the next tier and will upgrade you then, or upon request if you've seen yourself reach the next level in between our updates. We also don't downgrade partners until the end of their current term, so there's always time to shore up credit if needed. If you have questions about how these changes affect your organization's standing, get in touch with the Drupal Association.
A required part of this site couldn’t load. This may be due to a browser extension, network issues, or browser settings. Please check your connection, disable any ad blockers, or try using a different browser.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Drupal.org blog: Migrating issues from security.drupal.org to git.drupalcode.org | 5 | 7 | 17-07-2026 |
| 2 | Drupal Association blog: The work that just happens: the DA Insider for September 2026 | 0 | 13.04 | 20-10-2026 |
| 3 | Drupal blog: The AWS Migration: Building the Next Chapter of Drupal’s Infrastructure | 0 | 10.28 | 21-09-2026 |
| 4 | Drupal Association blog: After the PHP security release: auditing your Drupal sites | 0 | 13.6 | 22-10-2026 |
| 5 | PreviousNext: How we secured our clients’ Drupal sites with critical PHP security updates | 0 | 13.12 | 22-10-2026 |
| 6 | Webpro Company blog: Drupal core July security updates: what site owners should check now | 0 | 7 | 16-07-2026 |
| 7 | Talking Drupal: Talking Drupal #575 - The Drupal Advocacy Program | 0 | 8.92 | 22-10-2026 |
| 8 | Dynamosys Insights: PHP2Shell: Updating Drupal Won’t Fix These Critical PHP Flaws | 0 | 7.88 | 22-10-2026 |
| 9 | Darren Oh: Bring hands-on demos to your content with Drupal Forge | 0 | 10.76 | 21-10-2026 |
| 10 | X-post: WordPress Credits Updates | 0 | 18.13 | 29-06-2026 |