b_man β made their first commit to this issueβs fork.
avpaderno β credited b_man β .
Adding a line to organizations to indicate that organizations receive 1 credit per individual membership
b_man β made their first commit to this issueβs fork.
hestenet β credited b_man β .
b_man β made their first commit to this issueβs fork.
I've removed the duplicate event.
b_man β made their first commit to this issueβs fork.
Welcome to the community sharker92! I've confirmed your account, you should now be able to use https://www.drupal.org normally.
Kristen Pol β credited B_man β .
Kristen Pol β credited B_man β .
B_man β made their first commit to this issueβs fork.
Moving this to the drupal.org issue queue so I can create a proper issue fork / MR.
Thanks! Post DrupalCon things have settled down and I now have some space to review/ export this since it seems to have hit a good spot.
Content administrator has been granted to quietone. Please check when you have a chance that you can see what you need for doing release manager duties and report back if there's still a hangup.
I think the right role here is Content Administrator, since I don't see anything more specific I'm going to go ahead and grant it. If it turns out not to be the right role, we might swap it for the more correct one.
Moving this over to project issue tracking to create an MR for review
Swapping youtube embed for link so that non admins can edit this documentation
Thanks for the report! We have a potential fix in the review/deploy pipeline. Should see those fixes coming to production in the next days.
I've unblocked and confirmed. They should be able to use https://www.drupal.org and it's subsites normally
I've bandaid fixed this by changing the URL from the admin menu, but I'll defer to @drumm to merge/deploy the real fix.
hestenet β credited B_man β .
B_man β made their first commit to this issueβs fork.
Oh yeah, that was me, I forgot to hit save when I commented right after I did it. My apologies.
I'm thinking on ways we can make the protections less aggressive while still protecting us from spam account creation. Probably a mash up of the un-publish all posts idea with some other stuff mixed in.
Looks like they were automatically blocked for not submitting to the anti spam account creation measures. Their profile also looks a little spammy, but that wasn't the cause for the block as far as I can tell.
I just double checked to confirm, and any confirmed user can add a contributor roles using the links found in the "How to add roles" section of the description of this issue.
Working on this.
B_man β made their first commit to this issueβs fork.
Removed contents of 3376609-fix-typos.patch.
Adding a little more to the summary.
This was discussed a bit here: https://drupal.slack.com/archives/C0451JV7HRD/p1689090567790169. And for now completely removing auto crediting seems to be the direction we are looking to take.
Not quite as elegant as Neil's solution, but considering the pressure the credit system is under right now, removing all auto credit checking might be net neutral as far as extra work for maintainers, and also disincentivizes the behavior of doing empty things just for credit.
B_man β made their first commit to this issueβs fork.
I was thinking when it was created that the view was for spot checking upcoming date availability (hence the forward looking dates). The tiny csv button at the bottom of that page is an export for all event data. Does that fulfill the need or would you still prefer to have this view modified?
hestenet β credited B_man β .
Development has started on this so I'm going to move this over to Drupal.org customizations and going to assign it to myself since I'm going to be making commits.
Yeah, multi-select does seem to be the most straight forward path here. Events will need to be updated once this is deployed, but once updated will show up in the Contribution event pane instantly.
apaderno β credited B_man β .
Re-published, not spam.
Moving to bluecheese where the change will be made so we can have a proper issue fork/MR structure.
apaderno β credited B_man β .
After conferring with @drumm and @fjgarlin we're going to start with comment 3 and then potentially in the future audit other content types for meta descriptions / snippets for content types all make sense.
The most highly voted upon solution to this is here: https://stackoverflow.com/questions/15685205/noindex-tag-for-google/1571...
Thoughts? @drumm and whomever else:)
Patch contents removed at request of poster.
Fixed
I've unblocked kevin-ait. We have a new method for preventing spam accounts in place and it seems it might not message loud enough that the block is incoming.