keybase / keybase/client

Changing the team retention policy should require a majority of admin/owners

Open
#25,355 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

The title says it all, it should not be possible for a single admin within a team that has 10 owner/admins to set the retention policy to clear all the data.

I wonder if this should not apply for DMs as well. Why one can clear it all for both?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the team retention-policy permission handling and determine how team admins, owners, and direct messages are represented; define the majority rule and whether it applies to DMs before identifying the relevant tests and implementation changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authorization, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.