golem15/summercms
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(19.4.1): mark research open questions resolved

Browse Source
This commit is contained in:
Jakub Zych
2026-10-20 03:32:45 +02:00
parent ae81df3f4e
commit 2b5f0b2c92
1 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
.planning/phases/19.4.1-early-public-demo-on-demo-summercms-io/19.4.1-RESEARCH.md
View File

@@ -634,18 +634,20 @@ func (p *Plugin) Schedule() []pact.ScheduledCommand {
| A8 | The Node binary path and the Centrifugo binary path on rome match the summercms.io/bm files | rome deployment | Supervisor start failure; *check on rome* |
| A9 | `compass.Config` has a `Bool` accessor | Code example | Use `String` == "true" |
## Open Questions
## Open Questions (RESOLVED)
1. **"By mail" for contact submissions (D-04).**
All four were answered by the user on 2026-10-20 and recorded in CONTEXT.md.
1. **"By mail" for contact submissions (D-04).** RESOLVED: a G15Office task is enough; no mail is sent (D-04 revised; plan 03 adds no mailer).
- Known: feedback stores the submission (admin list) and files a G15Office task; it never mails. The demo mail driver is `log`.
- Unclear: whether a g15office task satisfies "by mail", and SMTP credentials for rome.
- Recommendation: configure the G15Office sync for the demo, plus a small `golem15.demo` listener or job that mails the operator. Mail on submission in the shared plugin would need a v0.1.1 tag and SMTP config. Ask the user in plan 2.
2. **Repository visibility and creation.**
2. **Repository visibility and creation.** RESOLVED: both repositories are private (D-21).
- `tea repos create --owner golem15 --name <repo>` is the precedent (19.5-02-PLAN Task 5; `tea` 0.16.0 is logged in as `jakub`).
- Unclear: are sm-demo-app and vue-demo-app private (19.5 default) or public (showcase)?
- If public, README and DEPLOY.md must hold no credentials (DEPLOY.md documents the key names only, D-06).
3. **Admin-tab half of todo ltcvqext.** The demo admin is private. The boardwalk `X-Summer-Build`/manifest work is framework code with a framework tag and changelog post. Recommendation: do the site half here and leave the todo open with a progress note for the admin half, unless the user wants a framework release in this phase.
4. **Concurrency with Phase 19.5,** which also edits `sm-user-plugin` and plans to mount sociallogin in sm-demo-app (19.5 D-21). Recommendation: finish 19.4.1's user change and tag first, and let 19.5 read the next free tag at execution.
3. **Admin-tab half of todo ltcvqext.** RESOLVED: site half only; the admin half stays open with a progress note (D-22). The demo admin is private. The boardwalk `X-Summer-Build`/manifest work is framework code with a framework tag and changelog post. Recommendation: do the site half here and leave the todo open with a progress note for the admin half, unless the user wants a framework release in this phase.
4. **Concurrency with Phase 19.5,** RESOLVED: 19.4.1 finishes and tags its sm-user-plugin change first; 19.5 reads the next free tag at execution (plan 03), which also edits `sm-user-plugin` and plans to mount sociallogin in sm-demo-app (19.5 D-21). Recommendation: finish 19.4.1's user change and tag first, and let 19.5 read the next free tag at execution.
## Environment Availability