Improving quality of Drupal Planet content

Thanks @ultimike, I support any initiatives which can weed out bland, machine generated articles on Planet Drupal.

I at point thought about suggesting adding a feature, where registered users can flag a blogger ("Hide blogger" ?), and as an individual user, no longer see posts from this blogger on the Planet Drupal page.

If a blogger hits a certain limit of "Hide blogger" flaggings by us users, the blogger could receive a "your content is low quality" message, or maybe get relegated to a less prominent display, like only showing the header, and in a smaller font?

@ressa - I agree wholeheartedly, but I think that your idea should be spun off into a different issue.

I chose the two items in the issue description because I think they are easily achievable in the short term.

Thinking about the "AI disclosure" a bit more - we (the Drupal community) could even provide suggested text or badging to make it easier for authors to comply.

-mike

That's a good suggestion, and I have created another issue. And great idea about a creating a "AI disclosure" / "No AI" badge.

I also created a Meta issue 📌 [Meta] Improving quality of Drupal Planet content Active , to have a central point for Planet Drupal improvements as well. It does share the same title as this issue ...

Maybe this issue could be split up into two issues (or even three?), and retitled, perhaps like this (or some other titles)?

• Send guidelines about Drupal Planet reminder regularly
• Disclose AI content
• Offer Planet Drupal "No AI generated content" Badges

I have already listed them like that in the Meta issue, what do you think about this approach?

Is this a proposal for automatically sending an email to feed owners?

@avpaderno - I'm not sure if it should be automatic, or more like a quarterly newsletter with different content each time reminding feed owners of the quality standards for posting on Drupal Planet.

As a first step, sure, an automatic reminder each quarter is fine, but I think we should aim higher.

Also - I wouldn't be against temporarily removing publishers whose current emails bounce. Being on Drupal Planet is a privilege, and should be treated as such.

-mike

Feeds do not have owners, as they are not nodes. There is only the person who created an issue asking to add a feed to Planet Drupal, but the account used to create that issue is not associated to the feed.
Furthermore, the person who asked to add the feed is not necessarily the person who is responsabile for the feed content or who adds new content. It could also be that person no longer works for the organization that handles that feed.

This means that, even in the case it would be possible to retrieve the emails associated to the feeds active on Planet Drupal, that email address could be not read from a person to which that message should be addressed. Supposing that person would reply saying which person should be contacted for that matter, there is no way to associate the given email to a feed.

That is all very disappointing, but I understand. ☹️

This is now a much bigger task than I imagined....

-mike

Thanks for clarifying @avpaderno, in that case perhaps this issue could become a feature wish for the new drupal.org, and moved to https://www.drupal.org/project/drupalorg → , something like this?:

• Add new "Contact" field to Planet Drupal feeds, which references a user on drupal.org
• Add a function in a custom module which regularly emails the contacts a reminder, triggered via cron -- maybe also to the user's organization? The Organization recipient can then act, and update the Contact field, if the original person who added the feed is no longer present

For new feeds, the Contact field could become mandatory, and existing feeds could over time get updated with a Contact?

An initial task would be to go through all the current feeds and send some emails to figure out who the listed owner of each should be...

Seems like maybe a good no-code task for a contribution day at a future Drupal event...

-mike

Great suggestion @ultimike, I have updated the issue summary, and added it under "Remaining tasks".