Automate manifesto signing: form → mailing list + auto-published signatory list
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- backend-api-design
Research direction
Start by reading BRIEF.md and PLAN.md in the life-itself/devspaces-consolidation planning repository, then review the listed form, mailing-list, webhook, and build-time options. Done means documenting an agreed architecture, canonical signatory store, consent and affiliation-disclaimer language, moderation step, and implementation plan for automatic updates.
Written by the indexing model from the issue text.
Description
Currently manifesto signing is a Google Form processed manually (signatories hand-added to manifesto.md).
Desired:
- On signup, signatory is added to the mailing list (Substack or ESP — pending email-infra decision, see devspaces-consolidation/BRIEF.md).
- Signatory list on /manifesto updates automatically (with consent + affiliation-disclaimer handling).
Needs its own mini research/plan:
- Options: Google Form + Apps Script → commit to repo / Brevo form + API → build-time fetch / Tally+webhook / custom endpoint.
- Consent language for public listing; moderation step to prevent spam signatures.
- Where the canonical signatory store lives (sheet vs repo data file).
Part of the Developmental Spaces consolidation (see life-itself/devspaces-consolidation planning repo: BRIEF.md, PLAN.md).
- Dominant language
- CSS
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from life-itself/developmentalspaces.org
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
life-itself/developmentalspaces.org#36 · 2 comments ·
All issues in life-itself/developmentalspaces.org
Similar issues
-
[Bug]: LangGraph Store sync put bypasses namespace validationPossibly taken @ktz03 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
volcengine/OpenViking#6050 ·
Maintainers usually reply within 1 day
-
[Bug]: Streamed /v1/chat/completions sends unredacted agent error text (keys) in the final chunkPossibly taken @rodricksz4h5 claimed this today. Openarea/streaming comp/gateway P2 type/security
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#138245 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
🐞 bug pending triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CircuitVerse/CircuitVerse#8025 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day