I found several instances of this user uploading screenshots from earlier comments with changed filenames. In each case the md5sum of the screenshots are identical:
In
#3200644: Olivero's autocomplete input does not have disabled styling →
, comment 9 uploads renamed screenshots from comment 7
In
✨
Improve email address field description at /user/register
Closed: outdated
, comment 81 uploads renamed screenshots from comment 78
In
📌
Primary Drop Button style update
Needs work
comment 54 uploads renamed screenshots from comment 39
In
🐛
Paragraphs fields cause overflow of content forms in Claro
Needs work
comment 18 uploads renamed screenshots from comment 14
Another odd comment was before/after gifs that reported a patch didn't work, but are clearly the same image with different filenames (the system clock changes from 11:38 to 11:39 in both
📌
Let users disable animation in Olivero
Needs work
)
The user has received multiple reminders that screenshots of a patch applying/not applying is not helpful nor does it earn credit. This behavior continues. The following are examples of where the user has been informed about "patch applied" screenshots.
#2927318: Status report shouldn't apologize for phpinfo() being disabled nor encourage people to enable it →
#3191847: Enable _theme key in *.routing.yml options →
#3219959: Update standard profile so Olivero is the default theme →
#3220566: Olivero: wide image can overlap sidebar when toolbar open and in vertical mode →
#778346: system_sort_modules_by_info_name() is misnamed →
#3217924: Olivero: Convert all colors (blues and grays) to HSL and normalize hues and saturations. →
Proposed solution
- Send the user a PM (using the "Contact" tab on the user profile) alerting them about this issue, ask the user to stop, and ask for a public comment confirming this. Also post a notice about the issue on Drupal slack, mentioning the user by name. If other means of contact exist, they should also be used.
- Unpublish the trash post, and put a comment in the issue where it has been posted about it being unpublished, and why. Do not delete the post – the site moderators need to be able to see the user's posting history.
- If the user replies within 14 days and confirms that they will stop doing it, close the issue as "Fixed" without any further action.
- If the user persists after being warned, block the account when the user has posted ten trash posts.
Draft generic PM (to be sent via the "Contact" tab on the user's profile):
Dear Drupalicon,
Hi, I am [FULL NAME] and I am a site moderator at Drupal.org.
The site moderators have been notified about some of your posts in issues on Drupal.org, please see this report [URL].
To be precise, it is a report about posts with images already uploaded by others and posts with screenshots that show that a patch apply/don't apply.
Since your post provided no new information about the issue, I've unpublished it.
I'm sending you this PM to inform you that such posts are unwanted in issue queues on Drupal.org, as they are in no way helpful, and you should stop posting them.
Please comment on the report in the issue containing the report. Please also make it it clear that you understand that such posts are not helpful, and that you will stop doing this from now on.
Please also read the community post on Issue Etiquette [URL], to learn more about what to do and what not to do when posting in issues at Drupal.org.
I hope for your full cooperation in resolving this matter.
I am sorry to tell you that if you, for some reason, do not want to cooperate, your account at Drupal.org will eventually be blocked.