Add a Module category called "Artificial Intelligence"

Is this about "modules entirely written by AI without much human interaction which might contain security issues" that need the label.
OR
"Modules that integrate with AI tool X/Y written by a human"?

For the first one, I think we don't need a module category but a label which can be seen as a disclaimer (similar to thingiverse/printables for AI STLmodels).
For the second one, a module category would work (e.g. for modules under the AI initiative)

@ bramdriesen

Ah great, I didn't think of that angle. Going with the theme of what Module Categories are defined as in https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →

It was thinking in the lines of "Modules that integrate with AI tool".

See https://www.drupal.org/drupalorg/docs/maintenance/guidelines-for-module-... →

Updating ID and IS based on guidelines.

According to the guidelines noted in #5, the next steps are to engage stakeholders and open comments for Guidelines for module categories updates, Step 2: Open Review → , which should be open for 30 days.

I've posted this in the #AI channel in Drupal Slack.

I agree with this +1

Since AI is such an overarching technology, this is a category that could easily be added to many projects in the future. Should we add to the description that it should be used only for modules whose primary function is to provide the tooling for AI, and not simply identify a project as AI-enabled?

+1 For #9, I think this should be made very clear.

The discussion for adding a label for "AI generated" modules is separate discussion happening elsewhere.

One thing about this, it's likely that more and more modules will have some AI functionality alongside the other categories.

I wonder if AI utilities Vs AI enabled or something should exist?

- the AI vector database provider is one tool.
- but a webform agent that uses AI to create forms should maybe be distinct ?

It's kind of fine if modules can have multiple categories though

I think that, with the given description, a single module category for AI projects should suffice.

For me it looks like we have an implicit consensus. Could somebody please confirm if we we can put this into RTBC?

The documentation is not clear about when the status can be changed. It just says:

After an appropriate period of open public comment, and once consensus has been reached, the issue can be marked Reviewed & Tested by the Community, and move on to implementation.

(Emphasis is mine.)

The text before that says the requested change should not implemented before 30 days are passed. [A]appropriate period could mean anything.

As a side note, site moderators cannot add new module categories. Even if the status would be changed, it would be probably pass some time before the module category is effectively added.

Registering my vote +1

Thanks @avpaderno. I will wait.

Meanwhile removing "Needs issue summary update" as it was addressed in #6.

This takes a +1 for me too. I will wait another week, and then change the status to Reviewed & tested by the community.

I don’t see why this needs to wait further. The issue summary is clear and this is a no-brainer IMO

I don’t see why this needs to wait further.

It will be probably still wait, since not even site moderators can add new module categories.

Criteria review:

✅ What impact will the proposed change have on existing users and the system?

✅ How many module projects would utilize this category change right away? (Could 100 modules be tagged with this category today? 1000?)
- even if it's not a ton right now (and it is a good amount), it's only going to grow

✅ How many community upvotes have there been for this change?
- no dissent inside this issue

✅ Does this change reflect a contrib ecosystem (for example, Drush, Webform, or Drupal Commerce)?
- only kind of, but only insofar as we've successfully consolidated our AI efforts

✅ Is this change represented by an existing category whose scope could be expanded or the description altered instead?
- I don't believe there's another category that would adequately represent this suite of modules

Additional considerations for terms

✅ Compound categories are not allowed (for example, using slashes or ampersands unless part of a very defined term in the technology sector, like Import/Export).

✅ Parentheticals should not be used to add context.
Acronyms should always be spelled out (but may use parentheses for the acronym, as in Search Engine Optimization (SEO)).
- I do recommend we do "Artificial Intelligence (AI)" just as an eye-catcher

✅ Terms and descriptions should use American English (en-US locale) for spelling and must be spelled correctly. Descriptions should be grammatically correct.
- reviewing the description, the only thing I don't like is "intelligent automation" because we have an "Automation" category for that. But I think what we're meaning here is "artificially-intelligent automation" or "agentic automation" or something like that. Would OP be amenable to a change in that vein?

I've updated the IS with those two changes to title and a suggested description, but I think if we get that, this can RTBC.

Nice analysis! Including "AI" makes sense :)

I’ve added the category with the description

Provides AI-powered functionality, integrate with machine learning services, or enable AI-based features such as content generation, natural language processing, recommendation engines, computer vision, or artificially-intelligent automation.

Since these are now project categories, which recipes may use too.

For those coming across this, here is the link → to all modules tagged with the new category to help see if there are AI modules you know that are still missing the categorisation at a glance.