From 2f0dbcdfb9ccbea2042e76fadf2acf85fc95f80f Mon Sep 17 00:00:00 2001 From: Ilja Melnicenko Date: Fri, 7 Aug 2026 15:52:19 +0200 Subject: [PATCH] Redmine-Skill: Sven als Senior-Entwickler eigenstaendig auffuehren Sven stand bisher nur als Anhaengsel in Iljas Punkt. Er bekommt einen eigenen Eintrag mit seiner Rolle als Senior-Entwickler und Maintainer der gemeinsam genutzten Extensions. Co-Authored-By: Claude Opus 5 (1M context) --- redmine-issue-workflow/SKILL.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/redmine-issue-workflow/SKILL.md b/redmine-issue-workflow/SKILL.md index a98be40..9ad3af9 100644 --- a/redmine-issue-workflow/SKILL.md +++ b/redmine-issue-workflow/SKILL.md @@ -72,9 +72,9 @@ Redmine renders **Textile** by default. Consequences: The assignee tells you what KIND of work a ticket is. These roles hold across projects, so read them before deciding whether a ticket is yours to act on. -- **Ilja** (the user) and **Sven** — the **developers**. Code, templates, SCSS, TypoScript, - deployments. Sven maintains the shared WapplerSystems extensions, so coordinate with him before - cutting a tag on one of those. +- **Ilja** (the user) — **developer**. Code, templates, SCSS, TypoScript, deployments. +- **Sven** — **senior developer** and maintainer of the shared WapplerSystems extensions + (`address`, `ws_slider`, `hero-item`, …). Coordinate with him before cutting a tag on one of those. - **Ranju** — **junior developer**. Also on the development side, so a ticket assigned to her is technical, not editorial. - **Corinna** — **design and the bulk of editorial work**. Content tickets (texts, images, page