WapplerSystems/t3bootstrap-upgrade-skills
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Redmine-Skill: Sven als Senior-Entwickler eigenstaendig auffuehren

Browse Source 
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) <noreply@anthropic.com>
This commit is contained in:
melnicenko
2026-08-07 15:52:19 +02:00
co-authored by Claude Opus 5
parent d433782b5d
commit 2f0dbcdfb9
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
redmine-issue-workflow/SKILL.md
+3 -3
View File
@@ -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