Workflow Workshop at FrOSCon 2026 -- working Agenda
===================================================
:Date: 2026-07-27
:Author: Hermann Voßeler
:toc:

//MENU: label FrOSCon-26 Agenda

************************************************************************
Working agenda for the planned in-person meeting at FrOSCon 2026
(St.Augustin), continuing the workflow design discussion between
Wouter Verwijlen and the Lumiera team. The items below are derived
from the link:Discussion25Digest.html[Discussion Digest 2025]: every
“open” point recorded there is a candidate; this page arranges them
into workable blocks and marks the intended outcome for each.
************************************************************************

// NOTE: draft compiled from the digest -- ordering, timeboxes and
//       priorities to be adjusted by the participants.

Preparation
-----------

- Read (or skim) the link:Discussion25Digest.html[Discussion Digest 2025];
  flag any point where the digest misrepresents your position.
- _Wouter:_ current state of the editing *scenario catalogue* -- even a partial
  collection helps as test material for blocks 1--3.
- _Hermann:_ check which parts of the timeline UI can serve for hands-on
  demonstration (even in mock-up form), especially for the attachment
  gesture question (block 1).
- Collect any mockups / sketches produced since December (connection
  visualisation, placement adjustment popups).


Block 1 -- The attachment gesture  (decision)
---------------------------------------------

_The point where the discussion paused in December 2025_
(-> link:Discussion25Digest.html#adding[Adding clips and automatic placement setup]).

Three candidate designs for how a clip acquires its placement connections:

1. context rule at drop location (proximity: magnetic yes / content-anchor?)
2. the “hooking gesture” (change of drag direction over a target; seam-drop
   for magnetic insertion)
3. arrow-connect (two-step: drop onto clip, then position via arrow)

Wouter explicitly wanted to _try_ the hooking gesture. If any form of
interactive mock-up is possible at the meeting, this is the block to use it;
otherwise paper walkthrough against scenarios from the catalogue.

Intended outcome::
  Pick one primary design (or a concrete combination), well-defined enough
  to be prototyped; note the fallback and the criteria for revisiting.

Related decisions to take along the way:

- how far the automatic mode reaches (magnetic only, or content-anchor with
  explicit target selection)
- the exact drop-location rules and their tuning parameters (“how close is
  close”)


Block 2 -- Moving semantics  (decision)
---------------------------------------

-> link:Discussion25Digest.html#moving[Moving, rearranging and ripple behaviour]

Open points, each small but consequential:

- *Collision default*: block (with push-through resistance) vs. never-block /
  make-way (Resolve model). Homework reference: Kdenlive's default mode as a
  specimen of blocking.
- *Make-way side effects*: when clips move out of the way, may magnetic
  connections break? Which reactions are shown during the gesture?
- *Reordering*: the mechanism for FCP-style drag reordering under magnetic
  placement -- “dragging while respecting all placements” vs. “dragging while
  ignoring the selected clip's children”; which is default?
- *Modifier budget*: confirm the table -- Shift = add to selection,
  Alt = duplicate, Ctrl = the common “alternative behaviour” modifier
  (Gimp pattern); snapping as toggle.

Intended outcome::
  Defaults fixed for collision behaviour and reordering; modifier table
  confirmed; open corner cases delegated to the scenario catalogue.


Block 3 -- Visual language  (exploration / mockups)
---------------------------------------------------

-> link:Discussion25Digest.html#grouping-devices[Grouping devices] /
link:Discussion25Digest.html#prototypes[Placement prototypes]

No existing NLE offers a model for displaying clip connections; colour is
largely reserved for the editor's own clip colourisation. To work on:

- indicating placement type per clip (lines/borders rather than colours)
- marking the *group leader* of an implicit group
- collision and diagnostic indicators (“why is this clip here?” --
  the derivation display)
- gesture feedback overlays: locked-clip indication, direction arrows
  (the Priority-2 cues from
  link:Discussion25Digest.html#gesture-concept[the gesture concept])

Intended outcome::
  A shortlist of visual candidates worth drawing up properly after the
  meeting; agreement on what the minimum indicator set must convey.


Block 4 -- Nested clips, sections, vertical space  (deep dive)
--------------------------------------------------------------

_The least-resolved cluster of the Grouping area_
(-> link:Discussion25Digest.html#sections[Sections and the narrative structure] /
link:Discussion25Digest.html#layering[Tracks, layering and vertical space]).

- Can nested sequences deliver the lightweight, always-visible quality of
  Wouter's *sections* proposal (named headers, drag-to-reorder scenes,
  per-section versioning)? What exactly is missing?
- Vertical screen real estate: inline rendering of nested content sharing
  track space (Hermann's sketches from April 2025 as starting point);
  stepwise expand/collapse; condensed previews; the popup-portal idea
  and its misclick problem.
- The layering-order override (content fixed above a reference clip):
  define the practical test that FrOSCon-25 called for.

Intended outcome::
  A shared picture of how a nested clip appears in each state
  (collapsed / condensed / expanded / opened), concrete enough to mock up;
  decision whether sections need any dedicated support beyond nested
  sequences + placements.


Block 5 -- Trimming deep dive  (exploration)
--------------------------------------------

_Never had its dedicated round in the mail discussion_
(-> link:Discussion25Digest.html#trimming[Trimming]).

- walk through Wouter's document proposal (clip-based trim-side selection,
  three commands, contextual trim mode, no sync locks) as a whole
- interplay with placement connections: what exactly ripples when trimming
  magnetic / content-anchored neighbours (behaviour matrix as reference)
- clip selection vs. trim-side selection: mutually exclusive?
  toggling? how does this respect sticky selections?
- keyboard bindings for trim operations; dynamic trimming via playback

Intended outcome::
  Confirm or amend the document proposal as the working trimming design;
  produce the list of trim scenarios for the catalogue.


Block 6 -- Routing groundwork  (open the quadrant)
--------------------------------------------------

_The one area of the 2025-08-24 topic plan that was never discussed_
(-> link:Discussion25Digest.html#tagging[Organising footage] /
link:Discussion25Digest.html#layering[Layering]).

- default routing rules: what happens without any user intervention
- tag-based routing in detail: tag taxonomy, tagging effort, auto-detection,
  relation to bins/project view
- explicit wiring (“plugs”): which user-visible form, if any, in the first
  iteration
- mixing groups, sub-mixes, and what replaces track mute/solo

Intended outcome::
  Not decisions -- a structured map of the routing questions, so this area
  can be worked through by mail like Grouping was.


Block 7 -- Smaller items  (round-up)
------------------------------------

- *Gear switch activation*: sub-mode of tools vs. always active for keyboard
  users; dedicated per-gear bindings in parallel?
  (-> link:Discussion25Digest.html#gear[The gear switch])
- *Navigation tool scope*: reaching effect parameters and mixer strips under
  the overarching navigation tool -- unresolved since FrOSCon-25
  (-> link:Discussion25Digest.html#tools-modes[Tools, modes, views]).
- *Placement edge cases* from Wouter's catalogue: swapping clips of different
  placement types, offset inheritance, anchor deletion
  (-> link:Discussion25Digest.html#prototypes[Placement prototypes]).


Block 8 -- Process
------------------

- publication path for the *scenario catalogue* (PDF -> Asciidoc, as with the
  Proposals document)
- Wouter's offer to work directly in Asciidoc / git for future document
  updates
- roadmap towards the actual *design document*: which digest topics are ripe
  to be rewritten as specification
- applying the *personas* to prioritise: a first pass ordering the agreed
  features (-> link:Discussion25Digest.html#personas[Target audience])
- rhythm and channel for the continued discussion after the meeting

