Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When #2454283: Remove block user fasttoggle from community role is deployed, as part of #2386793: Modify user role progression on Drupal.org, users with a relatively high level of participation on Drupal.org, and a certain length of time as members, should get the Community role. This should come with an email letting them know about UI changes and policies.
Deployment
- Merge
2454285-community-autogrant
of bothdrupalorg
anddrupalorg_crosssite
. - Set
drupalorg_crosssite_community_threshold_*
variables insettings.local.php
.
Issue fork drupalorg_crosssite-2454285
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 2454285-users-should-get changes, plain diff MR !4
Comments
Comment #1
drummComment #3
drummComment #4
jhodgdonThe first sentence of the issue summary has no verb, making it a bit difficult to tell what this issue is proposing to do. Also lacks details -- what level of participation, and what type?
Comment #5
drummTotally forgot the last part of the sentence, added "… should get the Community role"
Comment #6
drummAlthough this is less exploitable than the spam protection measures, I'm not sure I want to post the specific thresholds publicly. I'll send over a copy to you.
Comment #7
jhodgdonAdding one clarification that I got from our IRC conversation to the issue summary (not adding specifics, agreed we don't want to provide details on how to exploit the process).
Comment #8
drumm#2386793: Modify user role progression on Drupal.org has more details on the criteria, including one I missed
Comment #10
drummComment #11
drummI'm deploying the welcome email part of this today, and the auto-granting will follow tomorrow.
Comment #13
drummThis has been deployed.
Comment #15
gregglesI see this got reverted.
https://twitter.com/drupalorgcommit/status/613116616801415169
What's up?
Comment #16
drummIt didn't actually, that's getting the
7.x-integration
branch synced back to7.x-prod
.https://bitbucket.org/drupalorg-infrastructure/drupal.org/commits/all is a better view of the whole picture.