Elaborar o relatório de impacto (RIPD) do piloto
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
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- documentation, security
Research direction
Read the cited sections in docs/design.md (lines 136–144 and 161) and locate the original design document’s “fases” diagram. Map data and risks for each treatment, including network metadata, then review the candidate with the data protection officer and lawyer after #38 and #28 are resolved. Done means the RIPD is approved and archived before the pilot, with each mitigation tracked in an issue or implemented.
Written by the indexing model from the issue text.
Description
Contexto
O RIPD (Art. 38) é obrigatório antes do lançamento: há dado biométrico (rosto), menores nas fases seguintes e grande escala. É critério do Portão 1 junto com o parecer e precisa dos métodos de idade escolhidos.
Escopo
- Mapear os dados por componente (celulares, semeadores, idade, push), inclusive metadados da rede
- Riscos, medidas e bases legais por tratamento
- Revisão pelo encarregado e pelo advogado contra a versão candidata
Critérios de aceite
- RIPD aprovado e arquivado antes do primeiro membro do piloto
- Cada medida do RIPD tem uma issue ou está implementada
Depende de
- #38 — Obter o parecer jurídico pré-piloto sobre as seis perguntas em aberto
- #28 — Homologar os métodos de idade: sinais das lojas e fornecedores
Fontes
docs/design.md:161docs/design.md:136-144- Diagrama "fases" do documento de design original (não exportado para
docs/design.md)
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
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
melodic-software/claude-code-plugins#9619 ·
Maintainers usually reply within 1 day
-
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
-
area: core
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
venn: a name that starts with set-, union-, text- or style- followed by a letter is a parse errorOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
obsidianmd/pele#65 ·
Maintainers usually reply within 3 days
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
11ty/buildawesome#4407 · 1 reaction ·
Maintainers usually reply within 1 day