Nomear o encarregado e abrir o canal de atendimento aos titulares
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- backend
Research direction
Start with the cited sections of docs/design.md to understand the required contact and data subject request process. The issue does not name implementation files or an existing entry point, so first locate how the app publishes contact information and receives support requests. Done means a test request completes the documented flow and the formal appointment and contact are published on varanda.app and in the app.
Written by the indexing model from the issue text.
Description
Contexto
Antes do lançamento é preciso nomear o encarregado (Art. 41), publicar o canal de contato e atender pedidos dos titulares (Art. 18) com verificação proporcional, registro mínimo e prazos. A nomeação não depende do parecer.
Escopo
- Nomear o encarregado por ato formal e publicar o contato em varanda.app e no app
- Fluxo de pedidos dos titulares: recebimento, verificação proporcional, decisão, resposta e prazos
- Registro mínimo das solicitações
Critérios de aceite
- Um pedido de teste chega ao canal e é respondido pelo fluxo
- Nomeação e contato publicados
Fontes
Fase: Fase 1 — Piloto 18+ · Dificuldade: média · depende de parecer ou serviço externo
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 32m
- Merged PRs (30d)
- 17
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 Varanda-org/varanda
-
área:app área:produto sem-fase tipo:decisão
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Varanda-org/varanda#91 ·
Maintainers usually reply within 1 day
-
área:jurídico área:operações portão:1 tipo:operação
Difficulty 5/5 Over a week Newbie friendliness 20/100
Varanda-org/varanda#96 ·
Maintainers usually reply within 1 day
-
área:identidade área:produto sem-fase tipo:verificação
Difficulty 5/5 Over a week Newbie friendliness 25/100
Varanda-org/varanda#93 ·
Maintainers usually reply within 1 day
-
área:identidade área:produto sem-fase tipo:decisão
Difficulty 5/5 Over a week Newbie friendliness 25/100
Varanda-org/varanda#92 ·
Maintainers usually reply within 1 day
-
área:moderação área:produto sem-fase tipo:decisão
Difficulty 5/5 Over a week Newbie friendliness 35/100
Varanda-org/varanda#90 ·
Maintainers usually reply within 1 day
All issues in Varanda-org/varanda
Similar issues
-
bug Frontend P2-medium UI UX
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Deepak3699/Ai_Mentor#427 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
11ty/buildawesome#4407 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
keyxmakerx/Chronicle#1711 ·
Maintainers usually reply within 1 day
-
frontend
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
uoftblueprint/canada-basketball#79 ·
Maintainers usually reply within 1 day
-
New App Request
Difficulty 1/5 Under an hour Newbie friendliness 76/100
ThatGuySam/doesitarm#1126 · 1 comment ·