Perhaps next to Status for each test.
Even better would be a kind of Gantt chart log thing where you can see visually the relative times it takes! But that might be a bit advanced.
Something like: https://claude.ai/public/artifacts/58a06f78-2552-40fc-add8-0eb17f483a02
OR: https://claude.ai/public/artifacts/dd00223a-017f-47c6-9ceb-6c29e741d879
But I think this is a follow-up issue. For now, I think having the time it took for each test specifically next to status would be good.
- Things are busy before Vienna but owuld be good to have some onboarding meetings with them and details in the Sponsors tracker.
We have one with the CCC, we can improve things but one exists.
It works, we can improve things but the fundamentals work
Follow up issue here: ✨ Add a planning tool for plan-and-execute vs react Active
--- AI TRACKER METADATA ---
Update Summary: Allows us to pull a wider variety of images than is in the media library which is great for demos and likely good in production for one-off pages. Code is in a module and github, haven't figured out "proper" integration with Canvas AI
Check-in Date: MM/DD/YYYY (US format) [When we should see progress/get an update]
Due Date: MM/DD/YYYY (US format) [When the issue should be fully completed]
Blocked by: [#XXXXXX] (New issues on new lines)
Additional Collaborators: @username1, @username2
AI Tracker found here: https://www.drupalstarforge.ai/
--- END METADATA ---
Implement New Tracker Metadata Template (Both should work)
[Tracker]
<strong>Short Description: </strong> [One-line issue summary for stakeholders]
<strong>Update Summary: </strong> [One-line status update for stakeholders]
<strong>Check-in Date: </strong>MM/DD/YYYY
<strong>Due Date:</strong> MM/DD/YYYY
<strong>Blocked by:</strong> [#XXXXXX] (New issues on new lines)
<strong>Additional Collaborators:</strong> @username1, @username2
AI Tracker found here: <a href="https://www.drupalstarforge.ai/" title="AI Tracker">https://www.drupalstarforge.ai/</a> and docs on how to use the metadata above can be found <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.
[/Tracker]
Happy with this but note everything else we've ended up with lower case.
strategic evolution
priority
beta blocker
So should we do all the above lower case?
workstream 1a
ai views
Given the comment here: https://www.drupal.org/project/ai/issues/3485449#comment-16267002 🌱 [Meta] Bring AI Search, Assistants and Chatbot out of Experimental Active - that suggests we will not be taking AI Search out of experimental until 2.0 due to a number of refactors I think this isn't a beta blocker for 1.2.
As per this issue, I do not think this issue is a blocker to taking AI Search out of experimental buti a nice to have. There are plenty of work arounds and this is a fairly niche, as long as we have good errors I do not think this should block taking it out of experimental and certainly not 1.2
yautja_cetanu → created an issue.
A couple of things:
- Translate using the AI Translation is different to CK Editor, Translate translates the whole page and uses the tabs along the top of the page when enabled. It's a blunt instrument and is aimed at just working.
- The CK Editor Translation plugin is different, it uses a taxonomy for the languages and you get to it by going to the CKEditor settings and enabling the translate with AI AI Assistant plugin for that specific CKEditor toolbar for that style (such as the WYSIWYG style).
- It's probably worth enabling the AI Logging module and going into the AI Logging settings and enabling it to see what happens and posting that here too.
- Its also worth checking the default AI settings to make sure something has been set for all of the different operations and the model that has been set has the ability to do the translation. Providers can set defaults, the amazee provider may need defaults.
(How we bring the Salsa digital stuff):
https://github.com/salsadigitalauorg/xb_metadata/
Things Marcus thinks:
- - There are things hardcoded into the design system for metadata, Can we bring it into our existing UI?
- - Something similar to how AI Agents and config works, we have something where the information comes from the yaml files and then you can override it.
- - We need to decide if the thing we already have, if there is some missing metadata
Things Akhil thinks:
- - There are two approaches: The CT version, they do one component at a time, (They it gets the features of each component) when asked.
- - The version in XB gets all the tool calls and componenet information at once. Akhil things moving to the other one would be better.
For Kristen:
Our plan for the Small medium large.
- We go for T-shirt sizes not fibinacci sequence.
- We use Drupal issue tags for S, M , L, XL
- Small is a couple hours. 0-3.5 hours. (<0.5 day)
- Medium is up to 2 days - 3.5 - 14 hours (0.5 - 2 days)
- Large is more than 3 days - 14 - 30 hours (|2-4 days)
- XL is - More than a week. (4days + a week or more)
(We might change this, as a lot of issues might be XL or Small at this point.
- I had timeouts (been having issues with things lasting more than 5 mins timing out and causing issues on drupalforge but not locally. So maybe do things in smaller batches?
- Marcus has a brief summary on his meta issue of each issue, can we use some kind of standard syntax for summary that we pull into Starforge? (One Line Summary: ) for example.
- We should have another calendar view for Management style tasks (Marketting, etc).
- Ideally going forward, we would update the assignments for the beginning of the week and then do all pulling in updates to the following week. (Would be good for the website to maintain some kind of history).
- Be good if we could facilitate Marcus' planning doc on Starforge.
- Need to have "Epics" or "Tracks" and show all the issues in a track, all the (not done issues) and start doing burndown charts.