[Tracker]
Update Summary: [Discuss] Decide on use of word "pools" for CCC
Additional Collaborators: @username1, @username2
Metadata is used by the AI Tracker. Docs and additional fields here.
[/Tracker]
Problem/Motivation
Follow-up to:
#3563100: Minor cleanup on CCC pools page
I don't like the use of "pools" even if it might be a standard term in AI and other software spaces. I want to use something less techie.
For now, I've changed the menu item name and page title to "Agent Context", but left all other mentions of "pools" intact.
Proposed resolution
Review the existing code where "pool" and "pools" is used and update to not use that term.
Target date or deadline
February 2026
Remaining tasks
- Update code to be more generic and remove words "pool" and "pools"
- Create follow-up issue to update codebase if needed
Issue fork ai_context-3563107
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
kristen polComment #3
kristen polI've been working on this.
Comment #4
kristen polStarted the work here but ran out of steam:
#3564691: Create settings and sub-settings hierarchy for CCC
Unassigning for now.
Comment #5
kristen polComment #6
kristen polIt's changed in the UI so not major anymore
Comment #7
kristen polHigher priority items right now
Comment #8
kristen polComment #9
kristen polThis could be done along with refactor:
#3574359: Refactor context selection logic
Comment #10
kristen polComment #11
dstorozhukComment #12
dstorozhukI will take that one.
Comment #14
dstorozhukI don't see any changes in branch. Probably this was added already to 1.0.x
Comment #15
kristen polYes, noted in issue summary
Comment #16
kristen polComment #17
dstorozhukComment #18
dstorozhukComment #19
dstorozhukComment #20
dstorozhukAfter we merge that task - we need to notify all devs to reinstall the module, since we made a config name change, so this can throw the errors.
Assuming no real users use the module yet.
Comment #21
dstorozhukReady for review
Comment #22
kristen polThanks!
The module isn’t used for real, there’s a warning at the top of the project page that the dev branch isn’t stable, and I haven’t been adding update hooks since the code is changing rapidly.
Everyone just needs to reinstall from scratch at this point.
We aim to stabilize in a couple of weeks.
Comment #23
kristen polI did a quick scan of the changes and it seems pretty clear.
Just wondering if “assignment” should be “selection” but we can discuss tomorrow.
Comment #24
kristen polActually, I’ll keep this open for now for other people to chime in
Comment #25
kristen polI might try to get this in now
Comment #26
kristen polI've reviewed carefully, and this seems fine for now.
Any further refinement would happen here:
#3574359: Refactor context selection logic
I'll do a quick test and then merge if all is well.
Comment #27
kristen polWorks as expected, so I'll merge this.
Comment #29
kristen polMerged! Thanks :)
Comment #31
kristen pol