- πΊπΈUnited States brianbrarian
I think "Spam Prevention" is really the only category that Honeypot needs.
- Status changed to Needs work
almost 2 years ago 7:39pm 28 April 2023 - πΊπΈUnited States adrian_s_m
I believe #4 makes sense to me as well. The maintainer states on his blog that it's for spam protection Introducing the Honeypot form spam protection module for Drupal
- Status changed to Needs review
almost 2 years ago 7:57pm 28 April 2023 - πΊπΈUnited States kurttrowbridge
No disagreement from me! Updating the issue summary and flipping back to Needs Review.
- Status changed to RTBC
almost 2 years ago 8:17pm 28 April 2023 - Status changed to Postponed
over 1 year ago 5:48pm 19 May 2023 - πΊπΈUnited States chrisfromredfin Portland, Maine
Postponed until a new smaller list of Categories is finalized.
- Status changed to Needs work
9 months ago 3:56am 8 May 2024 - πΊπΈUnited States leslieg
Updated the issue summary to reflect the recent change to reduce the number of Categories from 55 down to 19.
- Status changed to Needs review
9 months ago 4:44pm 8 May 2024 - πΊπΈUnited States kurttrowbridge
Updating to a single category: Security.
- Status changed to RTBC
7 months ago 12:43pm 25 June 2024 - Status changed to Active
4 months ago 8:51pm 22 September 2024 - πΊπΈUnited States tr Cascadia
To me, it is very important that groups of similar modules get categorized the same way so that users looking for a module can find ALL similar modules listed in the same set of categories. Wasn't that the point of reducing the number of categories?
But this issue seems to have looked at Honeypot only in isolation. Likewise for other similar modules. Has anyone looked at the group of spam-prevention modules as a whole to ensure they are all together in the same set of categories? For example, CAPTCHA has a different list of categories and no issue/recommendation that I can find to change those categories for Project Browser. I would argue that following the recommendation in this thread will make is LESS easy for users to locate all modules performing this similar functional of spam prevention.
It seems to me that Spam prevention, which was the original category, was far more descriptive of the functionality of modules like Honeypot. Earlier this year drupal.org forced a category change and put Honeypot into Security, lumping it in with other modules that actually address security concerns like Password Policy and Security Kit. And now Project Browser is saying the categories should be further restricted to make it *only* in Security.
So my ask here is that you compile a list of modules that are similar (there is a partial list on the Honeypot project page, for example) and make the same recommendation to ALL these similar modules so that they will ALL show up in the same categories.
Additionally, if Spam prevention is supposed to be in the Security category, shouldn't the description of that category mention Spam prevention? It seems to be like this whole process of making category recommendations for the Project Browser should also be making recommendations/changes to the category descriptions to better enable users to find modules. As the people in this issue queue review the various modules and categories of modules, they should be double-checking whether the category description adequately describes what's in the category.
- πΊπΈUnited States leslieg
hi @ty. Thanks for your thoughtful questions and apologies for delay in responding.
This issue was created when there were 55 categories that could be added to a module on the drupal.org project page. After listening to community concerns and evaluating the best way forwrd to endure that categories would be a beneficial filter for Project Browser's target audience (sitebuilders and those new to Drupal), the decision was made to take a step back and take a good look at the categories that existed, the number of categories that could be selected, etc. We spent quite a bit of time working with the Drupal community on this and made the decision to reduce the number of categories from 55 down to 19 and to limit the number of categories that could be selected for a mudule to three.
We understood that this was a major change. Before we reopened all the category issues for rework, we worked with the Drupal Association the implementation of a migration plan to map and automatically update the existing categories. https://www.drupal.org/project/drupalorg/issues/3383004 π± Migrating "Categories" on Drupal.org Project pages Fixed
We also creating a document outlining the suggested use of the various categories. A document with category descriptions was created and added to the Maintainers page on Drupal.org https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... β .
The "Security" category was defined as: Help protect the website from attackers or bad actors, by identifying, preventing, or mitigating security vulnerabilities.
All modules previously using the Spam category were migrated to the new Security category.
As the module maintainer you can select two additional categories if you feel that Honeypot falls under categories in addition to Security. Please review the definitions while making your decisions.
Please reach out if you have additional questions or concerns.
- πΊπΈUnited States leslieg
Marking this issue as fixed. Current categories on the Project page are "Content editing experience and Security". The recommendation was only "Security". Maintainers know the module best and can select the categories they feel are most appropriate.
Note - the older updates on this issue occured before the Categories options were updated.
- Status changed to Fixed
1 day ago 6:50pm 27 January 2025