## Problem/Motivation The **Drupal AI Summit Paris (December 2026)** was the only major event in the programme without its own lane. DrupalCon Rotterdam 2026 and DrupalCon Orlando 2027 both got scoped labels and dedicated boards in #275+s, which makes each workstream visible in one view across every sprint. Paris had **neither a label nor a board** — its tickets were findable only by searching the title. This mattered now rather than later: the case-studies and social tracks shift their primary promotion focus from Rotterdam to Paris at **Sprint 13** (see #320+s). The lane needed to exist before that handover, not be built during it. ## Resolution Paris got its lane, and the same treatment was extended to both DrupalCon summits at the same time. There are now **three summit boards**, each scoped to one `summit::` label: | Board | Label | Description | |---|---|---| | [996 — AI Enterprise Summit](https://git.drupalcode.org/project/ai_initiative_marketing/-/boards/996) | `summit::Enterprise AI Summit` | Tickets related to the AI Enterprise Summit, which usually happens at a DrupalCon. You can filter by a specific event, e.g. [`DrupalCon::Rotterdam-2026`](https://git.drupalcode.org/project/ai_initiative_marketing/-/boards/996?label_name[]=summit%3A%3AEnterprise%20AI%20Summit&label_name[]=DrupalCon%3A%3ARotterdam-2026). | | [997 — Dev AI Summit](https://git.drupalcode.org/project/ai_initiative_marketing/-/boards/997) | `summit::Dev AI Summit` | Tickets related to the Dev AI Summit, the developer-facing day that usually happens at a DrupalCon. You can filter by a specific event, e.g. [`DrupalCon::Rotterdam-2026`](https://git.drupalcode.org/project/ai_initiative_marketing/-/boards/997?label_name[]=summit%3A%3ADev%20AI%20Summit&label_name[]=DrupalCon%3A%3ARotterdam-2026). | | [998 — AI Summit Paris](https://git.drupalcode.org/project/ai_initiative_marketing/-/boards/998) | `summit::AI Summit Paris` | Tickets related to the Drupal AI Summit in Paris, a standalone event rather than a DrupalCon summit. There is no per-edition label yet, so the board currently shows the December 2026 edition only. Add a second label when a later edition is scheduled, then filter the same way. | All three use the same 8 `state::` column layout as the sprint board ([118](https://git.drupalcode.org/project/ai_initiative_marketing/-/boards/118)) and the two DrupalCon boards ([634](https://git.drupalcode.org/project/ai_initiative_marketing/-/boards/634), [635](https://git.drupalcode.org/project/ai_initiative_marketing/-/boards/635)). ### Naming decision The ticket originally proposed `AISummit::Paris-2026`, pinning the label to a single year. **We went the other way.** The `summit::` labels name the *event series*, not the instance — `summit::AI Summit Paris`, not `summit::AI Summit Paris 2026`. **Why:** a summit recurs. Pinning the label to a year would mean a new label and a new board every time the event runs, and the board would stop being a place you can look to see how this summit is usually promoted. Naming the series keeps one durable lane per event, and the year is expressed by filtering — see below. This also means the `summit::` scope now covers all three summits consistently, rather than Paris using one convention and the two DrupalCon summits using the older unscoped `Enterprise AI Summit` label. ## How to use the boards **Every summit board spans all years.** To narrow one to a single event instance, add the event's label as a second filter in the search bar. The two labels combine, so you get only the tickets carrying both. Enterprise AI Summit, limited to DrupalCon Rotterdam 2026: ``` https://git.drupalcode.org/project/ai_initiative_marketing/-/boards/996?label_name[]=summit%3A%3AEnterprise%20AI%20Summit&label_name[]=DrupalCon%3A%3ARotterdam-2026 ``` The same pattern works on any of the three boards — swap the board id and the first label, then add whichever `DrupalCon::` label you want. Two further filters, as documented in #275+s: - **Only tickets assigned to you** — add `&assignee_username=<your-username>` - **Only the current sprint** — add `&milestone_title=Started`, or a specific sprint such as `&milestone_title=Sprint%2012` ### One summit label per ticket `summit::` is a scoped label, so a ticket can carry only one. That is deliberate — it keeps per-event credit clean — but it means a ticket genuinely spanning two summits has to pick a side or go unlabelled. #195+s, which compares the Dev and Enterprise summits, was left unlabelled for that reason. ## Still open The **exact Paris dates are not recorded in any ticket** — only "December 2026". The [landing page](https://new.drupal.org/ai/events/drupal-ai-summit-paris-26) is live, so the dates should be pinned and carried into the promotion tickets. **This is not tracked anywhere else — it needs its own ticket or an owner.** ## Acceptance Criteria - [x] A scoped Paris label exists and the naming decision is recorded in this ticket. - [x] Existing Paris tickets carry the label. - [x] A Drupal AI Summit Paris board exists, scoped to that label, with the standard `state::` columns. - [x] Filter URLs are documented here. - [x] The board is linked from the current sprint meta — #312+s. ## Work Track AI Marketing — Project Management --- Predecessor: #275+s (DrupalCon Rotterdam and Orlando boards). _Drafted with the assistance of AI (Claude Code / Opus 5), reviewed by @jjchinquist._